CN114339870B - Report processing method and device, terminal and network side equipment - Google Patents

Report processing method and device, terminal and network side equipment Download PDF

Info

Publication number
CN114339870B
CN114339870B CN202011066145.3A CN202011066145A CN114339870B CN 114339870 B CN114339870 B CN 114339870B CN 202011066145 A CN202011066145 A CN 202011066145A CN 114339870 B CN114339870 B CN 114339870B
Authority
CN
China
Prior art keywords
report
rrc message
cell group
terminal
message
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN202011066145.3A
Other languages
Chinese (zh)
Other versions
CN114339870A (en
Inventor
文鸣
金巴·迪·阿达姆·布巴卡
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication 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 Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to CN202011066145.3A priority Critical patent/CN114339870B/en
Priority to PCT/CN2021/121691 priority patent/WO2022068874A1/en
Publication of CN114339870A publication Critical patent/CN114339870A/en
Application granted granted Critical
Publication of CN114339870B publication Critical patent/CN114339870B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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
    • 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/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Landscapes

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

Abstract

The application discloses a report processing method and device, a terminal and network side equipment, and belongs to the technical field of communication. Wherein the method comprises the following steps: sending a first Radio Resource Control (RRC) message to the terminal, wherein the first RRC message carries a request identifier of a report corresponding to the auxiliary node (SN); and receiving a second RRC message sent by the terminal, wherein the second RRC message carries the report corresponding to the request identifier. The application solves the problem that only the interaction of the MN related report is allowed between the MN and the terminal in the prior art.

Description

Report processing method and device, terminal and network side equipment
Technical Field
The application belongs to the technical field of communication, and particularly relates to a report processing method and device, a terminal and network side equipment.
Background
In the current field of mobile communication, a usage scenario of SgNB (SN (Secondary Node) is gNB in MR-DC (Multi-Rat Dual Connectivity, multi-system dual connectivity)) to acquire RACH (Random ACCESS CHANNEL ) report is determined. However, the present mechanism only allows interaction between MN (Master Node) and terminal, sgNB cannot obtain related information in the RACH (Random ACCESS CHANNEL) procedure executed by any terminal on SgNB side from the terminal in MR-DC state.
Disclosure of Invention
The embodiment of the application provides a report processing method and device, a terminal and network side equipment, which can solve the problem that only interaction of MN-related reports is allowed between an MN and the terminal in the prior art.
In a first aspect, a method for processing a report is provided, which is executed by a network side device, and includes: a first RRC message is sent to a terminal, wherein the first RRC message carries a request identifier of a report corresponding to an auxiliary node SN; and receiving a second RRC message sent by the terminal, wherein the second RRC message carries the report corresponding to the request identifier.
In a second aspect, there is provided a report processing apparatus, comprising: a first sending module, configured to send a first RRC message to a terminal, where the first RRC message carries a request identifier of a report corresponding to an auxiliary node SN; the first receiving module is configured to receive a second RRC message sent by the terminal, where the second RRC message carries the report corresponding to the request identifier.
In a third aspect, a method for processing a report is provided, which is executed by a terminal, and includes: receiving a first RRC message sent by network side equipment, wherein the first RRC message carries a request identifier of a report corresponding to an auxiliary node SN; and sending a second RRC message to the network side equipment, wherein the second RRC message carries the report corresponding to the request identifier.
In a fourth aspect, there is provided a report processing apparatus, comprising: a second receiving module, configured to receive a first RRC message sent by a network side device, where the first RRC message carries a request identifier of a report corresponding to an auxiliary node SN; and the second sending module is used for sending a second RRC message to the network side equipment, wherein the second RRC message carries the report corresponding to the request identifier.
In a fifth aspect, a network side device is provided, the network side device comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions implementing the steps of the method according to the first aspect when executed by the processor.
In a sixth aspect, there is provided a terminal comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction when executed by the processor implementing the steps of the method according to the third aspect.
In a seventh aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor, performs the steps of the method according to the first aspect, or performs the steps of the method according to the third aspect.
In an eighth aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface and the processor being coupled, the processor being configured to run a network side device program or instruction, to implement the method according to the first aspect, or to implement the method according to the third aspect.
In the embodiment of the application, the network side equipment receives the second RRC message carrying the report corresponding to the request identifier and sent by the terminal by sending the first RRC message carrying the request identifier of the report corresponding to the auxiliary node SN to the terminal, so that the network side equipment can acquire the report corresponding to the auxiliary node SN, and optimize network side parameters through the report corresponding to the SN, thereby solving the problem that only interaction of MN related reports is allowed between the MN and the terminal in the prior art, and enriching the application scene of acquiring the report.
Drawings
Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable;
FIG. 2 is a flowchart of a method for processing a report according to an embodiment of the present application;
FIG. 3 is a flow chart diagram of a second method of processing a report in an embodiment of the application;
FIG. 4 is a schematic diagram of a report processing apparatus according to an embodiment of the present application;
FIG. 5 is a second schematic structural diagram of a report processing device according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a communication device according to an embodiment of the present application;
fig. 7 is a schematic diagram of a hardware structure of a terminal according to an embodiment of the present application;
Fig. 8 is a schematic structural diagram of a network side device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the application. All other embodiments, which are derived by a person skilled in the art based on the embodiments of the application, fall within the scope of protection of the application.
The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate, such that embodiments of the application may be practiced otherwise than as specifically illustrated and described herein, and that the "first" and "second" distinguishing between objects generally being of the same type, and not necessarily limited to the number of objects, such as the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.
It should be noted that the techniques described in the embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the application are often used interchangeably, and the described techniques may be used for both the above-mentioned systems and wireless techniques, as well as other systems and wireless techniques. The following description describes a New Radio (NR) system for exemplary purposes and NR terminology is used in much of the following description, but these techniques may also be applied to applications other than NR system applications, such as 6 th Generation (6G) communication systems.
Fig. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may also be referred to as a terminal device or a User Equipment (UE), and the terminal 11 may be a terminal-side device such as a Mobile phone, a tablet Computer (Tablet Personal Computer), a Laptop (Laptop Computer) or a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a palm Computer, a netbook, an ultra-Mobile Personal Computer (ultra-Mobile Personal Computer, UMPC), a Mobile internet device (Mobile INTERNET DEVICE, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE), and the wearable device includes: a bracelet, earphone, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may be a base station or a core network, where the base station may be called a node B, an evolved node B, an access Point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a Basic service set (Basic SERVICE SET, BSS), an Extended service set (Extended SERVICE SET, ESS), a node B, an evolved node B (eNB), a home node B, a home evolved node B, a WLAN access Point, a WiFi node, a transmission and reception Point (TRANSMITTING RECEIVING Point, TRP), or some other suitable terminology in the field, and the base station is not limited to a specific technical vocabulary so long as the same technical effect is achieved, and it should be noted that, in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.
First, related terms in the present application are explained;
1) UEInformationRequest (terminal information request)
This message is used for the network side UE to request to acquire corresponding information, such as requesting UE to send idle mode measurement, logged measurement report, connection establishment failure report, RACH report, etc. The message can only be sent to the UE by the MN (master node) node at present, for requesting the reporting information about MN recorded by the UE.
(2) UEInformationResponse (terminal information response)
This message is used for the UE to send to the network side the relevant information previously requested by the network side, e.g. when ra-ReportReq-r16 is set to 'wire' in UEInformationRequest, the UE will then include ra-ReportList-r16 in UEInformationResponse message and send to the network side.
The message can only be used to deliver MN-related reports. SRB1 and SRB2 may be used for transmission, SRB2 being used when logged measurement (record measurement) information is contained in the message.
The following describes in detail a report processing method provided by the embodiment of the present application through specific embodiments and application scenarios thereof with reference to the accompanying drawings.
The embodiment of the application provides a report processing method, which is executed by a network side device, fig. 2 is a flowchart of the report processing method of the embodiment of the application, as shown in fig. 2, and the steps of the method include:
step S202, a first RRC (Radio Resource Control ) message is sent to a terminal, wherein the first RRC message carries a request identifier of a report corresponding to an auxiliary node SN;
step S204, a second RRC message sent by the terminal is received, wherein the second RRC message carries a report corresponding to the request identifier.
Through step S202 and step S204 in the embodiment of the present application, the network side device sends the first RRC message carrying the request identifier of the report corresponding to the auxiliary node SN to the terminal, and receives the second RRC message carrying the report corresponding to the request identifier sent by the terminal, so that the network side device obtains the report corresponding to the auxiliary node SN, and the network side device can optimize the network side parameter through the report corresponding to the SN, thereby solving the problem in the prior art that only interaction of MN-related reports is allowed between the MN and the terminal, and enriching the application scenario of obtaining the report.
In an optional implementation manner of the embodiment of the present application, the first RRC message in the embodiment of the present application may include at least one of the following: terminal information request (UEInformationRequest) message, terminal information request UEInformationRequestSCG (Secondary Cell Group) message of the secondary cell group;
the terminal information request message carries a request identifier corresponding to the report; the terminal information request message of the secondary cell group is generated by the SN and carries the request identification corresponding to the report.
It should be noted that, because the terminal information request message carries the request identifier corresponding to the report, that is, UEInformationRequest is equivalent to the existing UEInformationRequest enhanced request. UEInformationRequestSCG is generated by the SN and carries the request identifier corresponding to the report, which is equivalent to a new RRC message.
In addition, for the enhanced UEInformationRequest, in a specific application scenario, interaction is performed between the MN and the SN through an Xn/X2 interface (through the Xn interface if both the MN and the SN are gnbs, and through the X2 interface if the MN is an eNB and the SN is a gNB), the MN knows the requirements of the report required to be acquired by the SN, and includes the request corresponding to the report required to be acquired in UEInformationRequest. For the new UEInformationRequestSCG, no interaction with the MN is required in the specific application scenario, the SN directly includes the request in this information.
Further, in the embodiment of the present application, in the case that the first RRC message is a terminal information request message of the secondary cell group, and the terminal is configured with the signaling radio bearer SRB (Signaling Radio Bearer), the sending, to the terminal, the first RRC message in step S202 includes:
step S202-11, a terminal information request message of the secondary cell group is sent to the terminal through SRB3 or SRB 1.
In the embodiment of the present application, in the case that the first RRC message is a terminal information request message of a secondary cell group, and the terminal is not configured with the signaling radio bearer SRB3, the sending, to the terminal, of the first RRC message in step S202 includes:
And step S202-12, a terminal information request message of the secondary cell group is sent to the terminal through SRB 1.
As is known from the above steps S202-11 and S202-12, if the terminal is configured with the signaling radio bearer SRB3, the terminal information request message of the secondary cell group may be sent to the terminal through SRB3 or SRB1, specifically through SRB3 or SRB1 depending on the network side device. If SRB3 is not configured, a terminal information request Message for the secondary cell group is sent to the terminal through SRB1, e.g., the request Message is included in the DL-DCCH-Message, and sent by the MN to the terminal.
Note that a Signaling Radio Bearer (SRB) is defined as a Radio Bearer (RB) used only for transmitting RRC and NAS messages. Further, the SRB includes:
SRB0 is used for RRC messages using CCCH logical channels;
SRB1 for RRC messages (possibly including accompanying NAS messages) and NAS messages before SRB2 establishment, all using DCCH logical channels;
SRB2 is used for NAS messages and RRC messages including recorded measurement information, all using DCCH logical channels. SRB2 has a lower priority than SRB1 and can be configured by the network after security activation by the AS.
SRB3 is used for specific RRC messages when the UE is in (NG) EN-DC or NR-DC and uses DCCH logical channels all.
In an alternative implementation manner of the embodiment of the present application, the request corresponding to the report in the present application is identified as at least one of the following:
1) Requesting an identity of a random access report (ra-ReportReqSCG) for accessing the secondary cell group; wherein the report requested by the identification of the requested access secondary cell group random access report includes at least one of: two-step random access report (2-step RACH report), four-step random access report (4-step RACH report).
It should be noted that, in an alternative implementation manner of the embodiment of the present application, the same request may be used, or 2 separate requests may be separated to request 2-step and 4-step RACH reports respectively.
2) Requesting an identification of a secondary cell group minimization of drive tests record measurement report (logMeasReportReqSCG);
3) Requesting an identification of a secondary cell group connection establishment failure report (connEstFailReportReqSCG);
4) Requesting identification of a secondary cell group radio link failure report (rlf-ReportReqSCG);
5) An identification of an SN cell movement history information report (mobilityHistoryReportReqSCG) is requested.
The method for processing the report in the present application is described above from the terminal side, and the method for processing the report in the present application will be described again from the network side, where the terminal side corresponds to the network side.
The embodiment of the application also provides a report processing method, which is executed by the terminal, fig. 3 is a flowchart of a report processing method in the embodiment of the application, and as shown in fig. 3, the steps of the method include:
Step S302, a first RRC message sent by a network side device is received, wherein the first RRC message carries a request identifier of a report corresponding to an auxiliary node SN;
step S304, a second RRC message is sent to the network side device, wherein the second RRC message carries a report corresponding to the request identifier.
Through the above steps S302 and S304, the terminal receives the first RRC message carrying the request identifier of the report corresponding to the auxiliary node SN sent by the network side device, and sends the second RRC message carrying the report corresponding to the request identifier to the network side device, so that the network side device obtains the report corresponding to the auxiliary node SN, and the network side device can optimize the network side parameters through the report corresponding to the SN, thereby solving the problem in the prior art that only interaction between the MN and the terminal for MN-related reporting is allowed, and enriching the application scenario for obtaining the report.
In an optional implementation manner of the embodiment of the present application, the second RRC message in the embodiment of the present application includes at least one of the following: a terminal information response (UEInformationResponse) message, a terminal information response (UEInformationResponseSCG) message for the secondary cell group;
the terminal information response message carries a report corresponding to the identifier; the terminal information response message of the secondary cell group carries a report corresponding to the identifier.
For UEInformationResponse, after the terminal sends to the network side device, if the network side device is the MN, further, the MN may forward to the SN through the Xn/X2 interface.
In an optional implementation manner in the embodiment of the present application, in a case where the second RRC message is a terminal information response message of the secondary cell group, a manner of sending the second RRC message to the network side device includes at least one of the following:
mode 1, in case that the terminal is under an evolved universal mobile telecommunications system terrestrial radio access network new radio-dual connection NG EN-DC (Next Generation E-UTRA-NR Dual Connectivity) or EN-DC and SRB3 is configured, transmitting a second RRC message to the network side device through SRB3 based on the base layer;
In mode 2, in the case that the terminal is NG EN-DC or EN-DC and is not configured with SRB3, the second RRC message is embedded in an Evolved universal terrestrial radio access E-UTRA (Evolved-UMTS Terrestrial Radio Access, evolved universal mobile telecommunications system terrestrial radio access network) RRC message, and is sent to the network side device through the E-UTRA RRC message.
For modes 1 and 2 above, if the terminal is under (NG) EN-DC and SRB3 is configured, the message is handed over to the lower layer for transmission by SRB 3; if SRB3 is not configured, the message is embedded in an E-UTRA RRC message ULInformationTransferMRDC and sent to the network side device over E-UTRA. That is, in the embodiment of the present application, the case of only SRB1 and SRB3 is prioritized because Logged measurement (record measurement) is not necessarily present. However, if logged measurement is available, if SRB3 is configured, it should be transmitted via SRB3, and if not configured, it should be transmitted via SRB 2; or SRB3 may be configured, but SRB2 transmission is used instead of SRB 3.
In an optional implementation manner of the embodiment of the present application, in the case that the second RRC message is a terminal information response message of a secondary cell group, the manner of sending the second RRC message to the network side device in step S304 of the present application may further include at least one of the following:
Mode 3, in the case that the terminal is under NR-DC and the SRB3 is configured, transmitting a second RRC message to the network side device through the SRB3 based on the bottom layer;
mode 4, in the case that the terminal is in NR-DC and is not configured with SRB3, embedding the second RRC message into the NR RRC message, and transmitting the second RRC message to the network side device through the NR RRC message;
for modes 3 and 4 above, if the UE is under NR-DC and SRB3 is configured, the message is delivered to the lower layer for transmission via SRB 3; if SRB3 is not configured, the message is embedded in NR RRC message ULInformationTransferMRDC and sent to the network side through SRB 1. Since it is a report of SN requirements, it is necessarily SCG related, and SRB3 is used for transmission once SRB3 is configured.
In an alternative implementation manner of the embodiment of the present application, the report corresponding to the request identifier in the present application is at least one of the following:
1) A random access report (ra-ReportReqSCG) to access the secondary cell group; wherein the request access secondary cell group random access report includes at least one of: two-step random access report (2-step RACH report), four-step random access report (4-step RACH report).
2) A secondary cell group minimization of drive tests record measurement report (logMeasReportReqSCG);
3) A secondary cell group connection establishment failure report (connEstFailReportReqSCG);
4) A secondary cell group radio link failure report (rlf-ReportReqSCG);
5) SN cell movement history information report (mobilityHistoryReportReqSCG).
In an optional implementation manner of the embodiment of the present application, when the second RRC message is a terminal information response message of the secondary cell group, and the terminal sends, in a dual connection case, the second RRC message to the network side device, where the second RRC message includes at least one of:
Mode 5, when the secondary cell group minimization of drive test record measurement report is not included in the second RRC message and SRB3 is not configured, sending the second RRC message to the network side device through SRB 1;
in mode 6, when the secondary cell group minimization of drive tests (mdr) record measurement report is not included in the second RRC message and SRB3 is configured, the second RRC message is sent to the network side device through SRB 3.
As can be seen from the above-described modes 5 and 6, if the report is not included, the second RRC message is preferentially transmitted with SRB3 in the case where SRB3 is configured, and the second RRC message can be transmitted through SRB1 in the case where SRB3 is not configured.
In mode 7, when the second RRC message includes the secondary cell group minimization of drive test record measurement report and SRB3 is configured, the second RRC message is sent to the network side device through SRB3 or SRB 2.
In the mode 8, if the second RRC message includes the secondary cell group minimization of drive test record measurement report and SRB3 is not configured, the second RRC message is sent to the network side device through SRB 2.
As can be seen from the foregoing manners 7 and 8, in the case where the secondary cell group minimization of drive test record measurement report is included in the second RRC message in the embodiment of the present application, there are the following cases:
1) If SRB3 is configured, SRB3 is used; SRB3 was not configured and SRB2 was used;
2) If SRB3 is configured, SRB2 is used; SRB3 was not configured and SRB2 was used;
3) If SRB3 is not configured, SRB2 is used.
The following describes the request and response of the present application in detail with reference to specific implementations of embodiments of the present application;
alternative embodiment 1:
In this alternative embodiment, the triggering and reporting of SgNB related reports is performed using the new request and response information.
Mode 1: the network side equipment acquires a report related to SgNB from the terminal through UEInformationRequestSCG messages; wherein the conditions using UEInformationRequestSCG include:
SIGNALLING RADIO BEARER (signaling radio bearer) SRB1 or SRB3;
RLC-SAP (Radio Link Control SERVICE ACCESS Point, radio link layer control protocol service access Point) AM;
Logical channel (DCCH) (DEDICATED CONTROL CHANNEL );
direction Network to UE (Network to terminal).
Further, UEInformationRequestSCG message specifically includes:
and the new Message is contained in the DL-DCCH-Message as follows:
Mode 2: the terminal uses UEInformationResponseSCG messages to transmit information related to the network request SgNB; wherein the conditions using UEInformationResponseSCG include:
SIGNALLING RADIO BEARER (signaling radio bearer) SRB1 or SRB2 or (in case of recording measurement information included) SRB3;
RLC-SAP (Radio Link Control SERVICE ACCESS Point, radio link layer control protocol service access Point) AM;
Logical channel (DCCH) (DEDICATED CONTROL CHANNEL );
direction Network to UE (Network to terminal).
Wherein UEInformationResponseSCG message comprises the following contents:
wherein specific entries for each report multiplex the definition of R16.
The method for reporting the report content in the network side according to logMeasReportSCG includes not only specific report content, but also a field with an available identifier for indicating whether the corresponding report is not submitted to the network side, where the field is used to indicate whether the UE side has a corresponding report not submitted to the network side:
alternative embodiment 2:
in this alternative embodiment, the existing request and response are multiplexed and enhanced; the network side equipment acquires a report from the terminal by using the enhanced UEInformationRequest message.
Mode 1) the conditions for using the enhanced UEInformationRequest message include:
Signalling radio bearer:SRB1；
RLC-SAP:AM；
Logical channel:DCCH；
Direction:Network to UE。
Wherein UEInformationRequest message includes the following:
mode 2, conditions for using the enhanced UEInformationRequest message include:
SIGNALLING RADIO BEARER SRB1 or SRB2 (in case of recording measurement information)
RLC-SAP:AM；
Logical channel:DCCH；
Direction:UE to network。
Wherein UEInformationRequest message includes the following:
It should be noted that, when multiplexing the existing RRC message, further enhancements may be made, for example, when SRB3 is configured and the UEInformationRequest message only contains a request related to SCG, the UEInformationRequest message may be directly sent from SN to UE through SRB 3; if SRB3 is configured and the UEInformationResponse message contains only reports related to SCG, UEInformationResponse message may be sent directly from UE to SN through SRB 3.
It should be noted that, in the above alternative embodiments, the present application is illustrated by combining the enhanced request with the enhanced response, and combining the new request with the new response, and in other embodiments of the present application, the acquisition of the report related to SgNB may be implemented by combining the enhanced request with the new response, or combining the new request with the enhanced response.
By the method for triggering and reporting SgNB the related report in the alternative implementation manner of the embodiment of the application, the SgNB can acquire SgNB related report from the UE for network side parameter optimization, so that the problem that only interaction of MN related report is allowed between the MN and the terminal in the prior art is avoided.
It should be noted that, in the report processing method provided in the embodiment of the present application, the execution body may be a report processing device, or a control module in the report processing device for executing the report processing method. In the embodiment of the present application, a method for processing a report by using a report processing device is taken as an example, and the report processing device provided in the embodiment of the present application is described.
An embodiment of the present application provides a report processing apparatus, and fig. 4 is a schematic structural diagram of the report processing apparatus according to the embodiment of the present application, as shown in fig. 4, where the apparatus includes:
A first sending module 42, configured to send a first RRC message to the terminal, where the first RRC message carries a request identifier of a report corresponding to the auxiliary node SN;
The first receiving module 44 is configured to receive a second RRC message sent by the terminal, where the second RRC message carries a report corresponding to the request identifier.
Optionally, the first RRC message in the embodiment of the present application includes at least one of the following: terminal information request message and terminal information request message of auxiliary cell group; the terminal information request message carries a request identifier corresponding to the report; the terminal information request message of the secondary cell group is generated by the SN and carries the request identification corresponding to the report.
Optionally, in the case that the first RRC message is a terminal information request message of a secondary cell group, and the terminal is configured with a signaling radio bearer SRB3, the first sending module 42 in the embodiment of the present application may further include: and the first sending unit is used for sending a terminal information request message of the secondary cell group to the terminal through SRB3 or SRB 1.
Optionally, in the case that the first RRC message is a terminal information request message of a secondary cell group, and the terminal is not configured with a signaling radio bearer SRB3, the first sending module 42 in the embodiment of the present application may further include: and the second sending unit is used for sending a terminal information request message of the secondary cell group to the terminal through SRB 1.
Optionally, reporting the corresponding request identification is at least one of: the method comprises the steps of requesting identification of a random access report of an access auxiliary cell group, requesting identification of a secondary cell group minimization of drive tests record measurement report, requesting identification of a secondary cell group connection establishment failure report, requesting identification of a secondary cell group radio link failure report, and requesting identification of an SN cell movement history information report.
Optionally, the report requested by the identification of the random access report requesting access to the secondary cell group includes at least one of: two-step random access report, four-step random access report.
By sending the first RRC message carrying the request identifier of the report corresponding to the auxiliary node SN to the terminal and receiving the second RRC message carrying the report corresponding to the request identifier sent by the terminal, the device in the embodiment of the application realizes the mode that the network side equipment acquires the report corresponding to the auxiliary node SN, and can optimize the network side parameters through the report corresponding to the SN, thereby solving the problem that only interaction of MN related reports is allowed between the MN and the terminal in the prior art, and enriching the application scene of acquiring the report.
The present application is explained from the perspective of the network side, and the present application will be explained from the perspective of the terminal side.
The embodiment of the application provides a report processing device; fig. 5 is a schematic diagram of a second structure of a report processing apparatus according to an embodiment of the present application, as shown in fig. 5, the apparatus includes:
The second receiving module 52 is configured to receive a first RRC message sent by the network side device, where the first RRC message carries a request identifier of a report corresponding to the auxiliary node SN;
And a second sending module 54, configured to send a second RRC message to the network side device, where the second RRC message carries a report corresponding to the request identifier.
Optionally, the second RRC message in an embodiment of the present application includes at least one of: terminal information response message, terminal information response message of auxiliary cell group; the terminal information response message carries a report corresponding to the identifier; the terminal information response message of the secondary cell group carries a report corresponding to the identifier.
Optionally, in the case that the second RRC message is a terminal information response message of the secondary cell group, the second sending module 54 in the embodiment of the present application may further include at least one of the following:
a third sending unit, configured to, in a case where the terminal is under new radio-dual connection NG EN-DC or EN-DC of the evolved universal mobile telecommunications system terrestrial radio access network and the SRB3 is configured, transmit, through the SRB3, a second RRC message to the network side device based on the bottom layer;
And the fourth sending unit is used for embedding the second RRC message into the evolved universal terrestrial radio access E-UTRA RRC message and sending the second RRC message to the network side equipment through the E-UTRA RRC message under the condition that the terminal is in EN-DC and is not configured with SRB 3.
Optionally, in the case that the second RRC message is a terminal information response message of the secondary cell group, the second sending module 54 in the embodiment of the present application may further include at least one of the following:
a fifth transmitting unit, configured to transmit, through SRB3, a second RRC message to the network side device based on the bottom layer, in a case where the terminal is under NR-DC and the SRB3 is configured;
And a sixth sending unit, configured to embed the second RRC message into the NR RRC message and send the second RRC message to the network side device through the NR RRC message when the terminal is under NR-DC and is not configured with SRB 3.
Optionally, the report corresponding to the request identification is at least one of: random access report of access auxiliary cell group, auxiliary cell group minimization of drive test record measurement report, auxiliary cell group connection establishment failure report, auxiliary cell group radio link failure report, SN cell movement history information report.
Optionally, in the case that the second RRC message is a terminal information response message of the secondary cell group, and the apparatus is in a dual connection case, the second sending module 54 in the embodiment of the present application may further include one of the following:
a seventh sending unit, configured to send, in a case where the second RRC message does not include the secondary cell group minimization of drive test record measurement report and is not configured with SRB3, the second RRC message to the network side device through SRB 1;
An eighth sending unit, configured to send, in a case where the second RRC message does not include the secondary cell group minimization of drive tests record measurement report and is configured with SRB3, the second RRC message to the network side device through SRB 3;
A ninth sending unit, configured to send a second RRC message to the network side device through SRB3 or SRB2 when the second RRC message includes a secondary cell group minimization of drive test record measurement report and is configured with SRB 3;
And a tenth sending unit, configured to send a second RRC message to the network side device through SRB2 when the second RRC message includes the secondary cell group minimization of drive test record measurement report and SRB3 is not configured.
By means of the method, the device and the system, the network side equipment can optimize network side parameters through the report corresponding to the SN, the problem that interaction of MN-related reports is only allowed between the MN and the terminal in the prior art is solved, and application scenes for acquiring the reports are enriched.
The processing device of the report in the embodiment of the application can be a device, a component in a terminal, an integrated circuit or a chip. The device may be a mobile terminal or a non-mobile terminal. By way of example, mobile terminals may include, but are not limited to, the types of terminals 11 listed above, and non-mobile terminals may be servers, network attached storage (Network Attached Storage, NAS), personal computers (personal computer, PCs), televisions (TVs), teller machines, self-service machines, etc., and embodiments of the present application are not limited in particular.
The report processing device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an ios operating system, or other possible operating systems, and the embodiment of the present application is not limited specifically.
The report processing device provided by the embodiment of the present application can implement each process implemented by the method embodiments of fig. 2 and fig. 3, and achieve the same technical effects, and in order to avoid repetition, a detailed description is omitted here.
Optionally, as shown in fig. 6, the embodiment of the present application further provides a communication device 600, including a processor 601, a memory 602, and a program or an instruction stored in the memory 602 and capable of running on the processor 601, where, for example, the communication device 600 is a terminal, the program or the instruction is executed by the processor 601 to implement each procedure of the above-mentioned report processing method embodiment, and achieve the same technical effects. When the communication device 600 is a network side device, the program or the instruction, when executed by the processor 601, implements the respective processes of the above-described processing method embodiment of the report, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.
Fig. 7 is a schematic diagram of a hardware structure of a terminal for implementing an embodiment of the present application.
The terminal 700 includes, but is not limited to: radio frequency unit 701, network module 702, audio output unit 703, input unit 704, sensor 705, display unit 706, user input unit 707, interface unit 708, memory 709, and processor 710.
Those skilled in the art will appreciate that the terminal 700 may further include a power source (e.g., a battery) for powering the various components, and that the power source may be logically coupled to the processor 710 via a power management system so as to perform functions such as managing charging, discharging, and power consumption via the power management system. The terminal structure shown in fig. 7 does not constitute a limitation of the terminal, and the terminal may include more or less components than those in fig. 7, or may combine some components, or may be arranged in different components, which will not be described in detail herein.
It should be appreciated that in embodiments of the present application, the input unit 704 may include a graphics processor (Graphics Processing Unit, GPU) 7041 and a microphone 7042, with the graphics processor 7041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 707 includes a touch panel 7071 and other input devices 7072. The touch panel 7071 is also referred to as a touch screen. The touch panel 7071 may include two parts, a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.
In the embodiment of the present application, after receiving downlink data from a network side device, the radio frequency unit 701 processes the downlink data with the processor 710; in addition, the uplink data is sent to the network side equipment. Typically, the radio unit 701 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
The memory 709 may be used to store software programs or instructions and various data. The memory 709 may mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. In addition, the Memory 709 may include a high-speed random access Memory, and may also include a nonvolatile Memory, wherein the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable EPROM (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device.
Processor 710 may include one or more processing units; alternatively, processor 710 may integrate an application processor that primarily processes operating systems, user interfaces, and applications or instructions, etc., with a modem processor that primarily processes wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 710.
The radio frequency unit 701 is configured to receive a first RRC message sent by a network side device, where the first RRC message carries a request identifier of a report corresponding to the auxiliary node SN;
the radio frequency unit 701 is further configured to send a second RRC message to the network side device, where the second RRC message carries the report corresponding to the request identifier.
The terminal in the embodiment of the application can receive the first RRC message carrying the request identifier of the report corresponding to the auxiliary node SN sent by the network side equipment, and send the second RRC message carrying the report corresponding to the request identifier to the network side equipment, thereby realizing the mode that the network side equipment acquires the report corresponding to the auxiliary node SN, optimizing the network side parameters through the report corresponding to the SN by the network side equipment, solving the problem that only the interaction of the MN related report is allowed between the MN and the terminal in the prior art, and enriching the application scene of acquiring the report.
Specifically, the embodiment of the application also provides network side equipment. As shown in fig. 8, the network device 800 includes: an antenna 81, a radio frequency device 82, a baseband device 83. The antenna 81 is connected to a radio frequency device 82. In the uplink direction, the radio frequency device 82 receives information via the antenna 81, and transmits the received information to the baseband device 83 for processing. In the downlink direction, the baseband device 83 processes information to be transmitted, and transmits the processed information to the radio frequency device 82, and the radio frequency device 82 processes the received information and transmits the processed information through the antenna 81.
The above-described band processing means may be located in the baseband means 83, and the method performed by the network-side device in the above embodiment may be implemented in the baseband means 83, and the baseband means 83 includes the processor 84 and the memory 85.
The baseband device 83 may, for example, comprise at least one baseband board, on which a plurality of chips are disposed, as shown in fig. 8, where one chip, for example, a processor 84, is connected to the memory 85, so as to invoke a program in the memory 85 to perform the network device operation shown in the above method embodiment.
The baseband device 83 may further include a network interface 86 for interacting with the radio frequency device 82, such as a common public radio interface (common public radio interface, CPRI for short).
Specifically, the network side device of the embodiment of the present invention further includes: instructions or programs stored in the memory 85 and executable on the processor 84, the processor 84 invokes the instructions or programs in the memory 85 to perform the method performed by the modules shown in fig. 8 and achieve the same technical effects, and are not repeated here.
The embodiment of the application also provides a readable storage medium, on which a program or an instruction is stored, which when executed by a processor, implements each process of the above-mentioned report processing method embodiment, and can achieve the same technical effects, so that repetition is avoided, and no further description is given here.
Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
The embodiment of the application further provides a chip, the chip comprises a processor and a communication interface, the communication interface is coupled with the processor, the processor is used for running a network side equipment program or instruction, the processes of the report processing method embodiment can be realized, the same technical effects can be achieved, and the repetition is avoided, and the description is omitted here.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present application.
The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.

Claims (23)

1. A method for processing a report, performed by a network-side device, comprising:
Sending a first Radio Resource Control (RRC) message to the terminal, wherein the first RRC message carries a request identifier of a report corresponding to the auxiliary node (SN);
Receiving a second RRC message sent by the terminal, wherein the second RRC message carries the report corresponding to the request identifier;
The first RRC message includes at least one of: terminal information request message and terminal information request message of auxiliary cell group;
The terminal information request message carries a request identifier corresponding to the report; and the terminal information request message of the secondary cell group is generated by the SN and carries a request identifier corresponding to the report.
2. The method according to claim 1, wherein, in case the first RRC message is a terminal information request message of a secondary cell group and the terminal is configured with a signaling radio bearer SRB3, sending the first RRC message to the terminal comprises:
and sending a terminal information request message of the secondary cell group to the terminal through SRB3 or SRB 1.
3. The method according to claim 1, wherein, in case the first RRC message is a terminal information request message of the secondary cell group and the terminal is not configured with a signaling radio bearer SRB3, sending the first RRC message to the terminal comprises:
and sending a terminal information request message of the secondary cell group to the terminal through SRB 1.
4. The method of claim 1, wherein the request corresponding to the report is identified as at least one of:
the method comprises the steps of requesting identification of a random access report of an access auxiliary cell group, requesting identification of a secondary cell group minimization of drive tests record measurement report, requesting identification of a secondary cell group connection establishment failure report, requesting identification of a secondary cell group radio link failure report, and requesting identification of an SN cell movement history information report.
5. The method of claim 4, wherein the requesting access to the requested report of the identification of the secondary cell group random access report comprises at least one of: two-step random access report, four-step random access report.
6. A method for processing a report, performed by a terminal, comprising:
Receiving a first RRC message sent by network side equipment, wherein the first RRC message carries a request identifier of a report corresponding to an auxiliary node SN;
sending a second RRC message to the network side equipment, wherein the second RRC message carries the report corresponding to the request identifier;
the second RRC message includes at least one of: terminal information response message, terminal information response message of auxiliary cell group;
the terminal information response message carries a report corresponding to the identifier; and the terminal information response message of the auxiliary cell group carries a report corresponding to the identifier.
7. The method according to claim 6, wherein in the case that the second RRC message is a terminal information response message of a secondary cell group, sending the second RRC message to the network side device includes at least one of:
transmitting the second RRC message to the network side equipment through the SRB3 based on a bottom layer under the condition that the terminal is under an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network new radio-dual connection (NG EN-DC) or EN-DC and the SRB3 is configured;
And under the condition that the terminal is in NG EN-DC or EN-DC and is not configured with the SRB3, embedding the second RRC message into an evolved universal terrestrial radio access (E-UTRA) RRC message, and sending the E-UTRA RRC message to the network side equipment.
8. The method according to claim 6, wherein in the case that the second RRC message is a terminal information response message of a secondary cell group, sending the second RRC message to the network side device includes at least one of:
Transmitting the second RRC message to the network side device through the SRB3 based on an underlay, in a case where the terminal is under NR-DC and the SRB3 is configured;
and under the condition that the terminal is under NR-DC and is not configured with SRB3, embedding the second RRC message into an NR RRC message, and sending the NR RRC message to the network side equipment.
9. The method of claim 7 or 8, wherein the report to which the request identification corresponds is at least one of:
Random access report of access auxiliary cell group, auxiliary cell group minimization of drive test record measurement report, auxiliary cell group connection establishment failure report, auxiliary cell group radio link failure report, SN cell movement history information report.
10. The method according to claim 6, wherein when the second RRC message is a terminal information response message of a secondary cell group, and the terminal sends the second RRC message to the network side device in the case of dual connectivity, at least one of:
transmitting the second RRC message to the network side equipment through SRB1 under the condition that the secondary cell group minimization of drive test record measurement report is not included in the second RRC message and SRB3 is not configured;
transmitting the second RRC message to the network side equipment through SRB3 when the secondary cell group minimization of drive test record measurement report is not included in the second RRC message and SRB3 is configured;
In the case that the second RRC message includes the secondary cell group minimization of drive test record measurement report and is configured with SRB3, sending the second RRC message to the network side device through SRB3 or SRB 2;
And in the case that the secondary cell group minimization of drive test record (MDT) measurement report is included in the second RRC message and SRB3 is not configured, sending the second RRC message to the network side equipment through SRB 2.
11. A report processing apparatus, comprising:
A first sending module, configured to send a first RRC message to a terminal, where the first RRC message carries a request identifier of a report corresponding to an auxiliary node SN;
the first receiving module is used for receiving a second RRC message sent by the terminal, wherein the second RRC message carries the report corresponding to the request identifier;
The first RRC message includes at least one of: terminal information request message and terminal information request message of auxiliary cell group;
The terminal information request message carries a request identifier corresponding to the report; and the terminal information request message of the secondary cell group is generated by the SN and carries a request identifier corresponding to the report.
12. The apparatus according to claim 11, wherein the first sending module comprises, in the case where the first RRC message is a terminal information request message of a secondary cell group and the terminal is configured with a signaling radio bearer SRB 3:
And the first sending unit is used for sending the terminal information request message of the secondary cell group to the terminal through SRB3 or SRB 1.
13. The apparatus according to claim 11, wherein the first sending module comprises, in the case where the first RRC message is a terminal information request message of the secondary cell group and the terminal is not configured with a signaling radio bearer SRB 3:
And the second sending unit is used for sending the terminal information request message of the secondary cell group to the terminal through SRB 1.
14. The apparatus of claim 11, wherein the request for reporting is identified as at least one of:
the method comprises the steps of requesting identification of a random access report of an access auxiliary cell group, requesting identification of a secondary cell group minimization of drive tests record measurement report, requesting identification of a secondary cell group connection establishment failure report, requesting identification of a secondary cell group radio link failure report, and requesting identification of an SN cell movement history information report.
15. The apparatus of claim 14, wherein the identification of the requested report requesting access to the secondary cell group random access report comprises at least one of: two-step random access report, four-step random access report.
16. A report processing apparatus, comprising:
A second receiving module, configured to receive a first RRC message sent by a network side device, where the first RRC message carries a request identifier of a report corresponding to an auxiliary node SN;
A second sending module, configured to send a second RRC message to the network side device, where the second RRC message carries the report corresponding to the request identifier;
the second RRC message includes at least one of: terminal information response message, terminal information response message of auxiliary cell group;
the terminal information response message carries a report corresponding to the identifier; and the terminal information response message of the auxiliary cell group carries a report corresponding to the identifier.
17. The apparatus of claim 16, wherein in the case where the second RRC message is a terminal information response message of a secondary cell group, the second sending module includes at least one of:
A third sending unit, configured to, in a case where the terminal is under new radio-dual connection NG EN-DC or EN-DC of an evolved universal mobile telecommunications system terrestrial radio access network and SRB3 is configured, transmit, through the SRB3, the second RRC message to the network side device based on a bottom layer;
And a fourth sending unit, configured to embed the second RRC message into an evolved universal terrestrial radio access E-UTRA RRC message and send the second RRC message to the network side device through the E-UTRA RRC message, where the terminal is under NG EN-DC or EN-DC and is not configured with the SRB 3.
18. The apparatus of claim 16, wherein in the case where the second RRC message is a terminal information response message of a secondary cell group, the second sending module includes at least one of:
A fifth transmitting unit, configured to transmit, by the SRB3, the second RRC message to the network side device based on an underlayer, in a case where the terminal is under NR-DC and the SRB3 is configured;
A sixth sending unit, configured to embed the second RRC message into an NR RRC message and send the second RRC message to the network side device through the NR RRC message when the terminal is in NR-DC and is not configured with SRB 3.
19. The apparatus of claim 17 or 18, wherein the report to which the request identification corresponds is at least one of:
Random access report of access auxiliary cell group, auxiliary cell group minimization of drive test record measurement report, auxiliary cell group connection establishment failure report, auxiliary cell group radio link failure report, SN cell movement history information report.
20. The apparatus of claim 16, wherein when the second RRC message is a terminal information response message of a secondary cell group, and the apparatus is in a dual connection case, the second transmitting module includes at least one of:
A seventh sending unit, configured to send, in a case where the second RRC message does not include the secondary cell group minimization of drive test record measurement report and SRB3 is not configured, the second RRC message to the network side device through SRB 1;
An eighth sending unit, configured to send, in a case where the second RRC message does not include the secondary cell group minimization of drive test record measurement report and SRB3 is configured, the second RRC message to the network side device through SRB 3;
A ninth sending unit, configured to send, in the case that the second RRC message includes the secondary cell group minimization of drive test record measurement report and is configured with SRB3, the second RRC message to the network side device through SRB3 or SRB 2;
a tenth sending unit, configured to send the second RRC message to the network side device through SRB2 when the second RRC message includes the secondary cell group minimization of drive test record measurement report and SRB3 is not configured.
21. A network side device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the method of processing a report according to any one of claims 1 to 5.
22. A terminal comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor carries out the steps of the method of processing a report according to any one of claims 6 to 10.
23. A readable storage medium, characterized in that the readable storage medium stores thereon a program or instructions, which when executed by a processor, implement the method of processing a report according to any of claims 1 to 5, or the steps of the method of processing a report according to any of claims 6 to 10.
CN202011066145.3A 2020-09-30 2020-09-30 Report processing method and device, terminal and network side equipment Active CN114339870B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202011066145.3A CN114339870B (en) 2020-09-30 2020-09-30 Report processing method and device, terminal and network side equipment
PCT/CN2021/121691 WO2022068874A1 (en) 2020-09-30 2021-09-29 Report processing method and apparatus, terminal and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011066145.3A CN114339870B (en) 2020-09-30 2020-09-30 Report processing method and device, terminal and network side equipment

Publications (2)

Publication Number Publication Date
CN114339870A CN114339870A (en) 2022-04-12
CN114339870B true CN114339870B (en) 2024-06-11

Family

ID=80949744

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011066145.3A Active CN114339870B (en) 2020-09-30 2020-09-30 Report processing method and device, terminal and network side equipment

Country Status (2)

Country Link
CN (1) CN114339870B (en)
WO (1) WO2022068874A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117882428A (en) * 2022-08-10 2024-04-12 北京小米移动软件有限公司 Random access reporting method, device and storage medium
CN117882477A (en) * 2022-08-10 2024-04-12 北京小米移动软件有限公司 Random access reporting method, device and storage medium
WO2024168627A1 (en) * 2023-02-15 2024-08-22 北京小米移动软件有限公司 Information reporting methods and apparatuses, and medium and communication system
WO2024168597A1 (en) * 2023-02-15 2024-08-22 北京小米移动软件有限公司 Information sending method and apparatus, information receiving method and apparatus, communication apparatus, and storage medium

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103190169A (en) * 2010-11-30 2013-07-03 富士通株式会社 Method, terminal device and base station for reporting radio link failure information
CN104770032A (en) * 2013-10-31 2015-07-08 华为技术有限公司 Dual connection mode resource request method and terminal, and master eNB and secondary eNB
CN105282767A (en) * 2014-07-16 2016-01-27 深圳市中兴微电子技术有限公司 Radio link failure monitoring reporting method, device and system for secondary cell
CN110741679A (en) * 2018-02-14 2020-01-31 Oppo广东移动通信有限公司 Secondary cell group configuration method and related product
CN111066338A (en) * 2017-08-09 2020-04-24 夏普株式会社 Terminal device, communication method, integrated circuit, and system of base station device
WO2020098587A1 (en) * 2018-11-13 2020-05-22 Qualcomm Incorporated Optimized secondary node reporting for multi-radio access technology dual connectivity
CN111417168A (en) * 2019-01-07 2020-07-14 中国移动通信有限公司研究院 System information transmission method, terminal and network equipment
WO2020150952A1 (en) * 2019-01-24 2020-07-30 Qualcomm Incorporated Minimization of drive test for dual connectivity
WO2020186403A1 (en) * 2019-03-15 2020-09-24 Qualcomm Incorporated Access procedure reporting

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10959276B2 (en) * 2017-08-10 2021-03-23 Telefonaktiebolaget Lm Ericsson (Publ) Methods responding to SCG failure in DC communications and related wireless terminals and network nodes
EP3533259B1 (en) * 2017-10-10 2020-01-08 Telefonaktiebolaget LM Ericsson (publ) Report nsa/sa nr indicator

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103190169A (en) * 2010-11-30 2013-07-03 富士通株式会社 Method, terminal device and base station for reporting radio link failure information
CN104770032A (en) * 2013-10-31 2015-07-08 华为技术有限公司 Dual connection mode resource request method and terminal, and master eNB and secondary eNB
CN105282767A (en) * 2014-07-16 2016-01-27 深圳市中兴微电子技术有限公司 Radio link failure monitoring reporting method, device and system for secondary cell
CN111066338A (en) * 2017-08-09 2020-04-24 夏普株式会社 Terminal device, communication method, integrated circuit, and system of base station device
CN110741679A (en) * 2018-02-14 2020-01-31 Oppo广东移动通信有限公司 Secondary cell group configuration method and related product
WO2020098587A1 (en) * 2018-11-13 2020-05-22 Qualcomm Incorporated Optimized secondary node reporting for multi-radio access technology dual connectivity
CN111417168A (en) * 2019-01-07 2020-07-14 中国移动通信有限公司研究院 System information transmission method, terminal and network equipment
WO2020150952A1 (en) * 2019-01-24 2020-07-30 Qualcomm Incorporated Minimization of drive test for dual connectivity
WO2020186403A1 (en) * 2019-03-15 2020-09-24 Qualcomm Incorporated Access procedure reporting

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NEC.R3-151489 "User Inactivity for dual connectivity - alt 1".3GPP tsg_ran\WG3_Iu.2015,(TSGR3_89),全文. *
vivo.R2-1912271 "Early Measurement Reporting for INACTIVE State".3GPP tsg_ran\wg2_rl2.2019,(tsgr2_107bis),全文. *

Also Published As

Publication number Publication date
CN114339870A (en) 2022-04-12
WO2022068874A1 (en) 2022-04-07

Similar Documents

Publication Publication Date Title
CN114339870B (en) Report processing method and device, terminal and network side equipment
CN110972171B (en) Beam failure recovery request transmission method, terminal equipment and network equipment
CN114430578B (en) Configuration and acquisition method of secondary cell group information and communication equipment
KR20230079275A (en) Data transmission method, device, terminal, network-side device and storage medium
US20230138775A1 (en) Method for mapping pusch signal, terminal, and network-side device
EP4181555A1 (en) Data transmission type configuration method and terminal
CN114080055B (en) Method, device, terminal and network side equipment for establishing radio resource control connection
CN113972967B (en) Auxiliary information sending method, auxiliary information receiving device, terminal and network side equipment
US20230199761A1 (en) Uplink channel transmission method and apparatus, and terminal
CN114079869A (en) Method for reporting capability, terminal equipment and network equipment
WO2022222792A1 (en) Service processing method, related device, and readable storage medium
US20240179757A1 (en) Information reporting method, terminal, and network side device
CN114258150B (en) Channel access selection method, device, communication equipment and readable storage medium
CN114374487B (en) Information processing method, device and communication equipment
US20240022998A1 (en) Path switching method, terminal and network side device
CN114071552A (en) Method for transmitting auxiliary information, terminal equipment and network equipment
CN113965998A (en) Uplink transmission method, device and related equipment
CN114501490B (en) Service transfer method, terminal and network side equipment
CN115208529B (en) Signal transmission method, terminal and network side equipment
CN114285534B (en) Method, device and terminal for determining transmission information
CN114080045B (en) Data transmission processing method, resource allocation method and related equipment
CN113973270B (en) Message sending and receiving methods, devices and communication equipment
CN114650120A (en) Information determination method and device and communication equipment
CN114071762A (en) Data transmission method and device and electronic equipment
US20230308225A1 (en) Uplink Control Information Transmission Method, Terminal, and Network Side Device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant