WO2021249467A1 - 接入过程处理方法、装置及通信设备 - Google Patents

接入过程处理方法、装置及通信设备 Download PDF

Info

Publication number
WO2021249467A1
WO2021249467A1 PCT/CN2021/099324 CN2021099324W WO2021249467A1 WO 2021249467 A1 WO2021249467 A1 WO 2021249467A1 CN 2021099324 W CN2021099324 W CN 2021099324W WO 2021249467 A1 WO2021249467 A1 WO 2021249467A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
bearer
access process
configuration
transmission
Prior art date
Application number
PCT/CN2021/099324
Other languages
English (en)
French (fr)
Inventor
吴昱民
Original Assignee
维沃移动通信有限公司
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 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2021249467A1 publication Critical patent/WO2021249467A1/zh
Priority to US18/074,439 priority Critical patent/US20230109276A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0866—Non-scheduled access, e.g. ALOHA using a dedicated channel for access
    • H04W74/0875—Non-scheduled access, e.g. ALOHA using a dedicated channel for access with assigned priorities based access
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections

Definitions

  • This application belongs to the field of communication technology, and in particular relates to a method, device and communication equipment for processing an access process.
  • NR New Radio
  • UE User Equipment
  • MCG Master cell group
  • the purpose of the embodiments of the present application is to provide an access process processing method, device, and communication equipment, which can solve the problem of how to restore data and connections when the UE is configured with multiple bearers and multiple cell groups.
  • an access process processing method including:
  • M transmission data is transmitted in the first access process, and the N transmission data is not transmitted in the second access process;
  • the M transmission data is the sum of the N transmission data
  • M and N are both positive integers, and M is less than or equal to N
  • the first condition is a restriction condition for the data transmitted during the access process, and the first condition includes: the transmission data corresponds to The first bearer information and/or the first transmission mode matches the configuration information, and the configuration information includes the second bearer information and/or the second transmission mode.
  • a device for processing an access process including:
  • the matching module is used to match the N transmission data to be transmitted with the first condition
  • the processing module is configured to execute the first access process or the second access process according to the matching result
  • M transmission data is transmitted in the first access process, and the N transmission data is not transmitted in the second access process;
  • the M transmission data is the sum of the N transmission data
  • M and N are both positive integers, and M is less than or equal to N
  • the first condition is a restriction condition for the data transmitted during the access process, and the first condition includes: the transmission data corresponds to The first bearer information and/or the first transmission mode matches the configuration information, and the configuration information includes the second bearer information and/or the second transmission mode.
  • a communication device in a third aspect, includes a processor, a memory, and a program or instruction that is stored on the memory and can run on the processor.
  • the program or instruction is executed by the processor. When executed, the steps of the method described in the first aspect are realized.
  • a readable storage medium is provided, and a program or instruction is stored on the readable storage medium, and the program or instruction implements the steps of the method described in the first aspect when the program or instruction is executed by a processor.
  • a chip in a fifth aspect, includes a processor and a communication interface.
  • the communication interface is coupled to the processor. Methods.
  • a computer software product is provided, the computer software product is stored in a non-volatile storage medium, and the software product is configured to be executed by at least one processor to implement the computer software product described in the first aspect Method steps.
  • a communication device configured to perform the method according to the first aspect.
  • the N transmission data to be transmitted are matched with the first condition; according to the matching result, the first access process or the second access process is executed.
  • M transmission data is transmitted in the first access process, and the N transmission data is not transmitted in the second access process;
  • the M transmission data is the sum of the N transmission data Data matching the first condition;
  • the first condition includes: the first bearer information corresponding to the transmission data and/or the first transmission mode matches the configuration information, and the configuration information includes the second bearer information and/or the second transfer method.
  • the embodiment of the present application solves the problem that when the UE is configured with multiple bearers and multiple cell groups, How to recover data and connections.
  • Figure 1 is a structural diagram of a network system applicable to an embodiment of the present application
  • FIG. 2 is a flowchart of a method for processing an access process provided by an embodiment of the present application
  • Fig. 3 is a structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 4 is a structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 5 is a structural diagram of a terminal provided by an embodiment of the present application.
  • Fig. 6 is a structural diagram of a network device provided by an embodiment of the present application.
  • first and second in the specification and claims of this application are used to distinguish similar objects, but not to describe a specific sequence or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first” and “second” It is usually one type, and the number of objects is not limited.
  • the first object may be one or more.
  • “and/or” in the description and claims means at least one of the connected objects, and the character “/” generally means that the associated objects before and after are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used for the aforementioned systems and radio technologies as well as other systems and radio technologies.
  • NR New Radio
  • 6G 6th Generation
  • Fig. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network side device 12.
  • the terminal 11 may also be referred to as a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer or a personal digital device.
  • UE User Equipment
  • Terminal-side devices such as Vehicle User Equipment (VUE) and Pedestrian User Equipment (PUE), and wearable devices include: bracelets, headsets, 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 Node B, Evolved Node B, Access Point, Base Transceiver Station (BTS), radio base station, radio transceiver, basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, Wireless Local Area Network, WLAN ) Access point, Wireless Fidelity (WiFi) node, Transmitting Receiving Point (TRP) or some other appropriate term in the field, as long as the same technical effect is achieved, the base station is not limited to For specific technical vocabulary, it should be noted that, in the embodiments 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.
  • the data can be sent directly to the network device through the following methods:
  • Dedicated uplink resources configured by the network, for example, Physical Uplink Shared Channel (PUSCH) resources, that is, pre-configured PUSCH; or, Preallocated Uplink Resources (PUR).
  • PUSCH Physical Uplink Shared Channel
  • PUR Preallocated Uplink Resources
  • the network device can send data directly to the UE in the following ways:
  • the downlink feedback resource corresponding to the dedicated uplink resource configured by the network is configured by the network.
  • the network side When the network side releases the UE from the connected state to the IDLE/INACTIVE state, it retains the context configuration information of the UE.
  • the UE wants to send small data if the system message on the network side indicates that the transmission of small data is supported, for example, the transmission of small data less than 10Kbyte is supported, the UE in the IDLE/INACTIVE state does not enter the connected state through the above method, but directly Receiving or sending of data.
  • Step 0 The network device configures the UE with new 2-step random access configuration information, for example, including: MsgA and MsgB corresponding transmission resource information.
  • Step 1 The UE triggers the 2-step RACH process. Send the request information to the network side, such as sending MsgA via PUSCH. At the same time, the UE may also send physical random access channel (Physical Random Access Channel, PRACH) information to the network device.
  • Physical Random Access Channel Physical Random Access Channel
  • Step 2 The network device sends a confirmation message to the UE, and the confirmation message is MsgB. If the UE fails to receive MsgB, the UE retransmits MsgA.
  • the random access procedure of the UE includes any of the following:
  • Random access process based on contention
  • the random access process can be understood as a 4-step random access process, namely 4-step RACH.
  • the UE sends Msg1 to the network device, and the Msg1 can be understood as a random access request.
  • the network device After receiving Msg1, the network device sends Msg2 to the UE.
  • the Msg2 can be understood as a random access response (Random Access Response, RAR) message, which carries uplink grant (uplink grant) information.
  • RAR Random Access Response
  • the UE executes the Medium Access Control (MAC) layer grouping function to generate a MAC protocol data unit (PDU), and stores the MAC PDU in the Msg3 buffer, and then the UE
  • the MAC PDU in the Msg3 buffer is sent through a hybrid automatic repeat request (Hybrid automatic repeat request, HARQ) process.
  • the network device After receiving Msg3, the network device sends Msg4 to the UE, for example, a contention resolution identifier. The UE receives the Msg4 and judges whether the contention resolution is successful, if it succeeds, the random access process is successful, otherwise the random access process is re-initiated.
  • the UE For the re-initiated random access process, when the UE receives the uplink grant in Msg2 again, the UE directly retrieves the previously stored MAC PDU from the Msg3 buffer and sends it through the HARQ process. After the random access process is completed, the UE will clear the HARQ buffer of the Msg3 transmission of the random access process.
  • C-RNTI Cell Radio Network Temporary Identifier
  • PDCCH Physical downlink control channel
  • the Msg4 contention resolution verification is: the "UE Contention Resolution Identity) in the "MAC Control Element (CE) used to carry the UE Contention Resolution Identity” it receives "The information matches the first 48 bits of the "Uplink (Uplink) Common Control Channel (CCCH) Service Data Unit (SDU)” sent by it.
  • the MAC CE used to carry the UE's contention resolution identity can become the UE Contention Resolution Identity MAC CE.
  • the DC architecture is adopted, including two MCGs and SCG (Secondary Cell Group, secondary cell group), and the MCG corresponds to the master node (Master Node, MN) of the network equipment, and the SCG corresponds to the network equipment SN (Secondary Node).
  • the primary cell of MCG is called PCell (Primary Cell)
  • the primary cell of SCG is called PSCell (Primary Secondary Cell)
  • PCell and PSCell are collectively called SpCell (Special Cell).
  • the secondary cells of MCG and SCG are both called SCell (Secondary Cell).
  • Signaling Radio Bearer 1 (Signaling Radio Bearer 1, SRB1) is the signaling bearer between the UE and the MCG
  • SRB3 is the signaling bearer between the UE and the SCG.
  • the bearer types of UE include:
  • MCG Radio Bearer (Radio Bearer, RB): 1 PDCP and 1 RLC corresponding to RB are in MCG;
  • SCG RB 1 PDCP and 1 RLC corresponding to RB are in SCG;
  • Split RB 1 Packet Data Convergence Protocol (PDCP) corresponding to RB is in MCG or SCG, and 2 Radio Link Control (RLC) corresponding to RB are in MCG and SCG respectively.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • FIG. 2 is a flowchart of an access process processing method provided by an embodiment of the present application. The method is applied to a network device or a terminal, as shown in FIG. 2, and includes the following steps:
  • Step 201 Match the N transmission data to be transmitted with the first condition
  • Step 202 Perform the first access process or the second access process according to the matching result
  • M transmission data is transmitted in the first access process, and the N transmission data is not transmitted in the second access process;
  • the M transmission data is the sum of the N transmission data
  • M and N are both positive integers, and M is less than or equal to N
  • the first condition is a restriction condition for the data transmitted during the access process, and the first condition includes: the transmission data corresponds to The first bearer information and/or the first transmission mode matches the configuration information, and the configuration information includes the second bearer information and/or the second transmission mode.
  • the above-mentioned first condition can be understood as a restriction condition of the direct data sending or receiving method.
  • "direct data transmission or reception” may be adopted for small data transmission or reception.
  • some or all of the above N transmission data are small data, and the above M transmission data can be understood as transmission data that satisfies the "direct data sending or receiving mode" among the N transmission data.
  • the foregoing configuration information may be a network device configuration or protocol agreement, and may specifically include at least one of the second bearer information and the second transmission mode.
  • the above first condition corresponds to the configuration information.
  • the configuration information only includes the second bearer information
  • the above first condition is that the first bearer information corresponding to the transmission data matches the second bearer information
  • the configuration information only includes In the second transmission mode
  • the above-mentioned first condition can be understood as the first transmission mode corresponding to the transmitted data matches the second transmission mode.
  • the foregoing first condition includes at least one of the following:
  • the first bearer information corresponding to the transmitted data matches the second bearer information
  • the first transmission mode corresponding to the transmitted data matches the second transmission mode.
  • matching can be understood as the same bearer information and/or the same transmission method.
  • the first bearer information corresponding to the transmission data and the second bearer information matching can be understood as the first bearer information and the second bearer information corresponding to the transmitted data. Part of the carried information is the same; the first transmission mode corresponding to the transmission data matches the second transmission mode can be understood as the first transmission mode corresponding to the transmission data and the second transmission mode are partially or completely the same.
  • Transmitting M transmission data can be understood as sending M transmission data or receiving M transmission data.
  • the network device may send M transmission data during the first access process, and the terminal may receive M transmission data during the first access process; or the network device may receive M transmission data during the first access process.
  • the terminal sends M transmission data during the first access process.
  • the N transmission data to be transmitted are matched with the first condition; according to the matching result, the first access process or the second access process is executed.
  • M transmission data is transmitted in the first access process, and the N transmission data is not transmitted in the second access process;
  • the M transmission data is the sum of the N transmission data Data matching the first condition;
  • the first condition includes: the first bearer information corresponding to the transmission data and/or the first transmission mode matches the configuration information, and the configuration information includes the second bearer information and/or the second transfer method.
  • the embodiment of the present application solves the problem that when the UE is configured with multiple bearers and multiple cell groups, How to recover data and connections.
  • the execution of the first access process can be understood as allowing the transmission of the foregoing M transmission data in a "direct data transmission or reception" manner.
  • the above configuration information can be understood as configuration information in a direct data receiving or sending manner.
  • the executing the first access process or the second access process according to the matching result includes:
  • the foregoing second access process may be understood as not transmitting the foregoing transmission data during the initial access process.
  • the foregoing first access process may be understood as transmitting the transmission data that meets the first condition in the initial access process.
  • the terminal can be sent when the terminal enters the connected state. In this way, the transmission delay of the transmission data that meets the first condition can be reduced.
  • the network device configuration or protocol stipulates that only MCG DRB can use direct data reception or transmission, while the UE's MCG DRB and SCG DRB both have data transmission. Then, the UE only uses "direct data transmission or reception" for MCG DRB, and SCG DRB is still in a suspended state.
  • the executing the first access process or the second access process according to the matching result includes:
  • the second access procedure is performed.
  • N transmission data are transmitted during the initial access process only when N transmission data meets the first preset condition, when at least one transmission data does not meet the first condition , Then any one of the N transmission data is not transmitted during the initial access process. In this way, when the N transmission data all meet the first condition, the N transmission data can be directly transmitted. In the case where at least one transmission data does not meet the first condition, the time for performing the access process can be shortened.
  • the foregoing second bearer information may include at least one of the following: a bearer identifier and a bearer type.
  • the content contained in the first bearer information is a subset or a complete set of the second bearer information.
  • the first bearer information can be understood as a bearer identifier;
  • the second bearer information includes a bearer type, the above-mentioned first bearer information can be understood as the bearer type.
  • the foregoing second bearer information includes a bearer identifier and a bearer type, the foregoing first bearer information may be understood as at least one of a bearer identifier and a bearer type.
  • the foregoing bearer types include at least one of the following: MCG Data Radio Bearer (DRB), SCG DRB, MCG Split DRB (MCG Split DRB), and SCG Split DRB (SCG Split DRB).
  • DRB MCG Data Radio Bearer
  • MCG Split DRB MCG Split DRB
  • SCG Split DRB SCG Split DRB
  • MCG Split DRB can be understood as: the PDCP carried is in the MCG, and the two RLCs carried are in the MCG and SCG respectively.
  • SCG Split DRB can be understood as: the PDCP carried is in the SCG, and the two RLCs carried are in the MCG and SCG respectively.
  • the above-mentioned bearer identifier includes at least one of the following: a DRB identifier, a Quality of Service flow (Quality of Service flow, QoS flow) identifier, a protocol data unit session identifier, and a cell group identifier.
  • a bearer type corresponding to a certain transmission data when a bearer type corresponding to a certain transmission data is included in the second bearer information, it can be determined that the first bearer information corresponding to the transmission data matches the configuration information.
  • the bearer identifier corresponding to a certain transmission data when the bearer identifier corresponding to a certain transmission data is included in the second bearer information, it can be determined that the first bearer information corresponding to the transmission data matches the configuration information.
  • the bearer identifier and bearer type corresponding to a certain piece of transmission data are included in the second bearer information, it can be determined that the first bearer information corresponding to the transmission data matches the configuration information.
  • the second transmission mode includes at least one of the following: a data sending mode and a data receiving mode.
  • the above-mentioned data sending method includes at least one of the following:
  • the terminal sends data in Msg3 in the 4-step random access process
  • the terminal sends data in MsgA in the 2-step random access process
  • the terminal sends data in the configured dedicated uplink resource
  • the network device sends data in Msg4 in the 4-step random access process
  • the network device sends data in MsgB in the 2-step random access process
  • the network device sends data in the downlink resource corresponding to the configured dedicated uplink resource.
  • the aforementioned data receiving method includes at least one of the following:
  • the network device receives data in Msg3 in the 4-step random access process
  • the network device receives data in MsgB in the 2-step random access process
  • the network device receives data in the configured dedicated uplink resource
  • the terminal receives data in Msg4 in the 4-step random access process
  • the terminal receives data in MsgB in the 2-step random access process
  • the terminal receives data in the downlink resource corresponding to the configured dedicated uplink resource.
  • the above-mentioned dedicated uplink resources can be understood as dedicated uplink PUSCH resources.
  • the general above-mentioned first transmission manner may be understood as a certain data sending manner or a certain data receiving manner. It should be noted that in this embodiment of the application, when the first transmission mode corresponding to the above-mentioned transmission data is the same as one of the second transmission modes, the first transmission mode and configuration information corresponding to the transmission data can be determined match.
  • the data types of the aforementioned N transmission data may include at least one of control signaling and user data.
  • the M pieces of transmission data include at least one of the following:
  • the user plane data is added to the container (container) in the CCCH message, and the container contains the user's QoS flow or PDU session data.
  • configuration information may be configured by a network device or agreed upon by a protocol.
  • the configuration information when the configuration information is configured by a network device, the configuration information is carried in a radio resource control RRC release (RRCRelease) message or a system information block (System Information Block, SIB) message.
  • RRC release RRCRelease
  • SIB System Information Block
  • the method before the matching the N transmission data to be transmitted with the first condition, the method further includes:
  • Transmission instruction information the instruction information is used to instruct the terminal to retain the context configuration, and the context configuration is used to restore the connection and/or resume data transmission.
  • the foregoing context configuration may include DRB configuration, security configuration, and so on.
  • the transmission instruction information can be understood as suspend instruction information.
  • the network device sends the suspend instruction information, and instructs the terminal to retain the context configuration by releasing the terminal in the CONNECTED state to the IDLE/INACTVIE state.
  • performing the first access procedure includes:
  • the first operation includes any one of the following:
  • Operation 1 In a case where the M transmission data are sent through the MCG bearer, restore the configuration of the bearer MCG;
  • Operation 3 In the case where the M transmission data are sent through the MCG separated bearer, restore the configuration of the bearer MCG;
  • Operation 4 In a case where the M transmission data are sent through the SCG split bearer, restore the configuration of the bearer SCG;
  • Operation 5 in the case that the M transmission data are sent through the SCG separated bearer, restore the PDCP configuration and the MCG configuration of the SCG separated bearer.
  • the network device configuration or protocol stipulates that only MCG DRB can use direct data reception or transmission, and the DRB corresponding to the data to be sent by the UE is MCG DRB. If the UE uses Msg3 to send uplink data, the UE is using Msg3 to send uplink data.
  • the configuration information may include: PDCP configuration information of the SRB and DRB corresponding to the MCG (for example, establishing a PDCP entity or rebuilding a PDCP entity; restoring PDCP state variables); the security context of the MCG; and the (header) compression function of the MCG.
  • the network device configuration or protocol stipulates that SCG DRB can use direct data reception or transmission, and the DRB corresponding to the data to be sent by the UE is SCG DRB, and the UE uses Msg3 to send uplink data, then the UE is using Msg3 to send uplink data Restore the configuration information corresponding to the previously stored SCG.
  • the configuration information may include: PDCP configuration information of the SRB and DRB corresponding to the SCG; the security context of the SCG; and the (header) compression function of the SCG.
  • the network equipment configuration or protocol stipulates that MCG split DRB can use direct data reception or transmission, and the DRB corresponding to the data to be sent by the UE is MCG split DRB. If the UE uses Msg3 to send uplink data, the UE is using Msg3 to send The configuration information corresponding to the previously stored MCG is restored before the uplink data.
  • the configuration information may include: the PDCP configuration information of the SRB and DRB corresponding to the MCG; the security context of the MCG; and the (header) compression function of the MCG.
  • the network device configuration or protocol stipulates that SCG split DRB can use direct data reception or transmission, and the DRB corresponding to the data to be sent by the UE is SCG split DRB. If the UE uses Msg3 to send uplink data, the UE is using Msg3 to send Restore the previously stored configuration information corresponding to the SCG before the uplink data.
  • the configuration information may include: PDCP configuration information of the SRB and DRB corresponding to the SCG; the security context of the SCG; and the (header) compression function of the SCG.
  • the network side configuration or protocol stipulates that SCG split DRB can use direct data reception or transmission, and the DRB corresponding to the data to be sent by the UE is SCG split DRB. If the UE uses Msg3 to send uplink data, the UE is using Msg3 to send The previously stored PDCP configuration information corresponding to the SCG split bearer, the RLC configuration of the SCG split bearer of the MCG, and the SRB configuration of the MCG are restored before the uplink data. At this time, the RLC configuration of the SCG split DRB is still suspended, so the data of the SCG split DRB is sent through its MCG RLC.
  • the PDCP configuration information corresponding to the SCG separated bearer may include: the PDCP configuration information corresponding to the SCG separated bearer, and the PDCP configuration information may include establishing a PDCP entity or rebuilding a PDCP entity; restoring PDCP state variables; SCG security context; SCG ( Head) compression function.
  • the first operation further includes: retaining and suspending the configuration of the borne SCG.
  • the first operation further includes: retaining and suspending the bearer MCG configuration.
  • the first operation further includes at least one of the following:
  • Restoring the configuration of the MCG includes the configuration of the MCG radio link control carried by the SCG separated bearer;
  • Restoring the configuration of the MCG includes the configuration of the MCG signaling radio bearer
  • restriction conditions for direct data reception or transmission may also include other restriction conditions, that is, the above-mentioned first condition may also include at least one of the following:
  • the size of the transmission data is equal to or smaller than or larger than the first threshold value preset by the threshold value;
  • the signal strength of the cell measured by the terminal is equal to or less than or greater than the second threshold value preset by the threshold value.
  • Step 1 The network device sends the indication information for retaining the context configuration to the UE, instructing the UE to retain its context configuration.
  • the context configuration is used for the UE to resume connection and/or resume data transmission and reception. For example, when the network device releases the UE in the CONNECTED state to the IDLE/INACTVIE state, the suspend indication information is sent in the RRCRelease message, and the suspend indication information is used to instruct the UE to retain the context configuration.
  • the network device configuration or protocol stipulates the "configuration information of the direct data reception or transmission mode" of the UE.
  • the “configuration information of the direct data receiving or sending mode” includes at least one of the following:
  • instruction information for the reserved context configuration and the “configuration information for the direct data reception or transmission mode” can be sent in the same message, for example, sent by the RRCRelease message. It can also be sent in different messages, for example, "instruction information for preserving context configuration” is sent through an RRCRelease message, and "configuration information for direct data reception or transmission mode” is sent through a SIB message.
  • the "data type" of the "direct data reception or transmission” includes at least one of the following:
  • the "direct data receiving or sending method” includes at least one of the following:
  • Direct data transmission method for example, uplink data transmission
  • Direct data reception for example, downlink data reception.
  • the direct data sending method includes at least one of the following:
  • the data is sent in the dedicated uplink PUSCH resource configured by the network.
  • the direct data receiving method includes at least one of the following:
  • the PDSCH includes downlink reception data of the UE's DRB.
  • the "bearer information using direct data reception or transmission” includes at least one of the following:
  • the bearer identifier for direct data reception or transmission is adopted.
  • "bearer information using direct data reception or transmission” includes at least one of the following:
  • MCG Split DRB that is, the carried PDCP is in the MCG, and the two RLCs carried are in the MCG and SCG;
  • SCG Split DRB that is, the carried PDCP is in the SCG, and the two RLCs carried are in the MCG and SCG respectively.
  • "using the bearer identifier for direct data reception or transmission” includes at least one of the following:
  • Cell group identity such as MCG identity or SCG identity.
  • Step 2 When the UE has data to send or receive, and the conditions for sending or receiving the data meet the direct data receiving or sending restrictions stipulated in the network configuration or protocol, the UE is allowed to trigger direct data sending or receiving . Otherwise, the UE triggers the second access procedure to establish or restore the connection.
  • the "restrictions on direct data reception or transmission" include at least one of the following:
  • the bearer identifier corresponding to the data is the same as the "bearer identifier for direct data reception or transmission" agreed in the network device configuration or protocol.
  • the data sending method corresponding to the data is the same as the "direct data receiving or sending method" agreed by the network side configuration or protocol.
  • the network device configuration or protocol agreement can adopt "data sent in Msg3 of the 4-step random access process", and the sending mode supported by the data to be sent by the UE is also "data sent in Msg3 of the 4-step random access process”.
  • restriction conditions for direct data reception or transmission may also be used in combination with other restriction conditions, and the other restriction conditions may include at least one of the following:
  • the size of the transmission data is less than or equal to the first threshold
  • the signal strength of the cell measured by the terminal is greater than or equal to the second threshold value.
  • the size of the transmitted data can also be set to be greater than or equal to the third threshold, and the cell signal strength measured by the terminal is less than or equal to the fourth threshold, which is not further limited here.
  • the UE processing method includes any of the following:
  • the "direct data reception or transmission” method is adopted.
  • the network device configuration or protocol stipulates that only MCG DRB can use direct data reception or transmission, while the UE's MCG DRB and SCG DRB both have data transmission. Then, the UE only uses "direct data transmission or reception" for MCG DRB, and SCG DRB is still in a suspended state.
  • the UE behavior of "direct data transmission or reception” includes any of the following:
  • Method 1 If the "direct data transmission or reception" data is sent through the MCG bearer, the UE restores the configuration of the bearer MCG when the "direct data transmission or reception" is adopted.
  • the network equipment configuration or protocol stipulates that only MCG DRB can use direct data reception or transmission, and the DRB corresponding to the data to be sent by the UE is MCG DRB.
  • the UE uses Msg3 to send uplink data, and the UE restores it before sending the uplink data with Msg3.
  • the configuration information may include: PDCP configuration information of the SRB and DRB corresponding to the MCG (for example, establishing a PDCP entity or rebuilding a PDCP entity; restoring PDCP state variables); the security context of the MCG; and the (header) compression function of the MCG.
  • Method 2 If the data of the "direct data transmission or reception" is sent through the SCG bearer, the UE restores the configuration of the bearer SCG when the "direct data transmission or reception" is adopted.
  • the network device configuration or protocol stipulates that SCG DRB can use direct data reception or transmission, and the DRB corresponding to the data to be sent by the UE is SCG DRB.
  • the UE uses Msg3 to send uplink data, and the UE restores its previous data before sending uplink data with Msg3.
  • Configuration information corresponding to the stored SCG may include: PDCP configuration information of the SRB and DRB corresponding to the SCG; the security context of the SCG; and the (header) compression function of the SCG.
  • Method 3 If the data of the "direct data transmission or reception" is sent through MCG separated bearer, the UE restores the configuration of the bearer MCG when the "direct data transmission or reception" is adopted.
  • the network equipment configuration or protocol stipulates that MCG split DRB can be used to receive or send data directly, and the DRB corresponding to the data to be sent by the UE is MCG split DRB.
  • the UE uses Msg3 to send uplink data, and the UE uses Msg3 to send uplink data before sending uplink data.
  • the configuration information may include: the PDCP configuration information of the SRB and DRB corresponding to the MCG; the security context of the MCG; and the (header) compression function of the MCG.
  • Method 4 If the data of the "direct data transmission or reception" is sent through the SCG separation bearer, the UE restores the configuration of the bearer SCG when the "direct data transmission or reception" is adopted.
  • the network device configuration or protocol stipulates that SCG split DRB can use direct data reception or transmission, and the DRB corresponding to the data to be sent by the UE is SCG split DRB.
  • the UE uses Msg3 to send uplink data, and the UE uses Msg3 to send uplink data before sending uplink data.
  • the configuration information may include: PDCP configuration information of the SRB and DRB corresponding to the SCG; the security context of the SCG; and the (header) compression function of the SCG.
  • Method 5 If the "direct data transmission or reception" data is sent through the SCG separated bearer, the UE restores the PDCP configuration and the MCG configuration of the SCG separated bearer when the "direct data transmission or reception" is adopted.
  • the network-side configuration or protocol stipulates that SCG split DRB can use direct data reception or transmission, and the DRB corresponding to the data to be sent by the UE is SCG split DRB.
  • the UE uses Msg3 to send uplink data, and the UE uses Msg3 to send uplink data before sending uplink data. Restore the previously stored PDCP configuration information corresponding to the SCG split bearer, the RLC configuration of the SCG split bearer of the MCG, and the SRB configuration of the MCG.
  • the PDCP configuration information corresponding to the SCG separated bearer may include: the PDCP configuration information corresponding to the SCG separated bearer, and the PDCP configuration information may include establishing a PDCP entity or rebuilding a PDCP entity; restoring PDCP state variables; SCG security context; SCG ( Head) compression function.
  • the behavior of the UE may also include: if the configuration information stored by the UE includes the configuration information of the bearer SCG, the UE deletes or retains the SCG configuration of the bearer according to the network side configuration or protocol agreement information. In an embodiment, the UE deletes the bearer's SCG configuration while restoring the bearer's MCG configuration. In another embodiment, the UE retains but keeps suspended (that is, does not use) the bearer's MCG configuration while restoring the bearer's MCG configuration. After receiving the restoration of the SCG configuration information indicated by the network side (eg, receiving the RRCResume Message), the UE then executes the SCG configuration process of restoring the bearer. For example, restore the configuration information of the DRB and SRB of the bearer SCG (eg, PDCP and RLC configuration); restore the security context of the SCG, etc.
  • restore the configuration information of the DRB and SRB of the bearer SCG eg, PDCP and RLC configuration
  • the behavior of the UE may further include: the UE retains the MCG configuration information of the bearer according to the network side configuration or protocol agreement. For example, when the UE restores the SCG configuration, it retains but keeps the MCG configuration of the bearer suspended (that is, does not use). After receiving the MCG configuration information instructed by the network device (for example, receiving the RRCResume message), the UE executes it again Restore the MCG configuration process of the bearer. For example, restore the configuration information of the DRB and SRB of the MCG carried.
  • the behavior of the UE further includes at least one of the following:
  • the configuration of the restored MCG includes the MCG and RLC configuration of the separated bearer of the SCG.
  • the configuration of the restored MCG includes the configuration of the MCG and SRB.
  • the data sender may indicate which cell group the sent data comes from.
  • the UE indicates that the logical channel ID (LCID)-1 in the MAC PDU sent is the LCID-1 of the MCG or SCG.
  • LCID logical channel ID
  • the conventional connection establishment (or recovery) process can be understood as a process in which the data carried or received by the data is not sent or received before the initial access process is completed.
  • the UE only sends a connection recovery request message in Msg3 or Msg4, and does not send the data in the DRB.
  • the UE resumes the data transmission and reception of the data bearer only after receiving the connection recovery message sent by the network side.
  • the execution subject may be an access process processing device, or a control module in the access process processing device for executing the access process processing method.
  • the access process processing method executed by the access process processing apparatus is taken as an example to illustrate the access process processing apparatus provided in the embodiment of the present application.
  • FIG. 3 is a structural diagram of an access process processing apparatus provided by an embodiment of the present application. As shown in FIG. 3, the access process processing apparatus 300 includes:
  • the matching module 301 is configured to match the N transmission data to be transmitted with the first condition
  • the processing module 302 is configured to execute the first access process or the second access process according to the matching result
  • M transmission data is transmitted in the first access process, and the N transmission data is not transmitted in the second access process;
  • the M transmission data is the sum of the N transmission data
  • M and N are both positive integers, and M is less than or equal to N
  • the first condition is a restriction condition for the data transmitted during the access process, and the first condition includes: the transmission data corresponds to The first bearer information and/or the first transmission mode matches the configuration information, and the configuration information includes the second bearer information and/or the second transmission mode.
  • the processing module 302 is specifically configured to: perform the first access procedure when at least one of the N transmission data satisfies the first condition; or, in the N transmission data If none of the transmission data meets the first condition, execute the second access procedure.
  • the processing module 302 is specifically configured to: perform the first access procedure when the N pieces of transmission data all satisfy the first condition; or, among the N pieces of transmission data In a case where at least one transmission data does not meet the first condition, execute the second access procedure.
  • the second bearer information includes at least one of the following: a bearer identifier and a bearer type.
  • the bearer type includes at least one of the following: primary cell group MCG data radio bearer DRB, secondary cell group SCG DRB, MCG separated DRB, and SCG separated DRB.
  • the bearer identifier includes at least one of the following: a DRB identifier, a quality of service flow identifier, a protocol data unit session identifier, and a cell group identifier.
  • the second transmission mode includes at least one of the following: a data sending mode and a data receiving mode.
  • the data sending manner includes at least one of the following:
  • the terminal sends data in Msg3 in the 4-step random access process
  • the terminal sends data in MsgA in the 2-step random access process
  • the terminal sends data in the configured dedicated uplink resource
  • the network device sends data in Msg4 in the 4-step random access process
  • the network device sends data in MsgB in the 2-step random access process
  • the network device sends data in the downlink resource corresponding to the configured dedicated uplink resource.
  • the data receiving manner includes at least one of the following:
  • the network device receives data in Msg3 in the 4-step random access process
  • the network device receives data in MsgB in the 2-step random access process
  • the network device receives data in the configured dedicated uplink resource
  • the terminal receives data in Msg4 in the 4-step random access process
  • the terminal receives data in MsgB in the 2-step random access process
  • the terminal receives data in the downlink resource corresponding to the configured dedicated uplink resource.
  • the M pieces of transmission data include at least one of the following:
  • the user plane data carried in the signaling radio bearer SRB is the user plane data carried in the signaling radio bearer SRB.
  • the configuration information is agreed upon by a network device configuration or protocol.
  • the configuration information is carried in a radio resource control RRC release message or a system information block message.
  • the method before the matching the N transmission data to be transmitted with the first condition, the method further includes:
  • Transmission instruction information the instruction information is used to instruct the terminal to retain the context configuration, and the context configuration is used to restore the connection and/or resume data transmission.
  • performing the first access procedure includes:
  • the first operation includes any one of the following:
  • the PDCP configuration and the MCG configuration of the SCG separated bearer are restored.
  • the first operation further includes: retaining and suspending the bearer SCG configuration.
  • the first operation further includes: retaining and suspending the bearer MCG configuration.
  • the first operation further includes at least one of the following:
  • Restoring the configuration of the MCG includes the configuration of the MCG radio link control carried by the SCG separated bearer;
  • Restoring the configuration of the MCG includes the configuration of the MCG signaling radio bearer
  • the access process processing apparatus provided in the embodiment of the present application can implement each process in the method embodiment in FIG. 2. To avoid repetition, details are not described herein again.
  • the access process processing device in the embodiment of the present application may be a device, or a component, integrated circuit, or chip in a terminal.
  • the device can be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include but is not limited to the types of the terminal 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (PC), a television ( Television, TV), teller machines, self-service machines, etc., are not specifically limited in the embodiments of the present application.
  • the access process processing device in the embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.
  • the access process processing apparatus provided in the embodiment of the present application can implement each process implemented by the method embodiment in FIG. 2 and achieve the same technical effect. To avoid repetition, details are not described herein again.
  • an embodiment of the present application further provides a communication device 400, which includes a processor 401, a memory 402, and a program or instruction that is stored on the memory 402 and can run on the processor 401,
  • a communication device 400 which includes a processor 401, a memory 402, and a program or instruction that is stored on the memory 402 and can run on the processor 401
  • the communication device 400 is a terminal
  • the program or instruction is executed by the processor 401
  • each process of the foregoing access process processing method embodiment is realized, and the same technical effect can be achieved.
  • the communication device 400 is a network side device, when the program or instruction is executed by the processor 401, each process of the foregoing access process processing method embodiment is realized, and the same technical effect can be achieved. To avoid repetition, details are not described herein again.
  • FIG. 5 is a schematic diagram of the hardware structure of a terminal that implements each embodiment of the present application.
  • the terminal 500 includes but is not limited to: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, a memory 509, a processor 510 and other components.
  • the terminal 500 may also include a power source (such as a battery) for supplying power to various components.
  • the power source may be logically connected to the processor 510 through a power management system, so that the power management system can manage charging, discharging, and power consumption. Management and other functions.
  • the terminal structure shown in FIG. 5 does not constitute a limitation on the terminal.
  • the terminal may include more or fewer components than shown in the figure, or a combination of some components, or a different component arrangement, which will not be repeated here.
  • the input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042.
  • the graphics processor 5041 is paired by the image capture device ( For example, the image data of the still picture or video obtained by the camera) is processed.
  • the display unit 506 may include a display panel 5061, and the display panel 5061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 507 includes a touch panel 5071 and other input devices 5072.
  • the touch panel 5071 is also called a touch screen.
  • the touch panel 5071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackball, mouse, and joystick, which will not be repeated here.
  • the radio frequency unit 501 receives the downlink data from the network-side device and sends it to the processor 510 for processing; in addition, it sends the uplink data to the network device.
  • the radio frequency unit 501 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 509 can be used to store software programs or instructions and various data.
  • the memory 109 may mainly include a storage program or instruction area and a data storage area, where the storage program or instruction area may store an operating system, an application program or instruction required by at least one function (such as a sound playback function, an image playback function, etc.).
  • the memory 509 may include a high-speed random access memory, and may also include a non-volatile memory, where the non-volatile memory may be a read-only memory (Read-Only Memory, ROM) or a programmable read-only memory (Programmable ROM).
  • PROM erasable programmable read-only memory
  • Erasable PROM EPROM
  • Electrically erasable programmable read-only memory Electrically EPROM, EEPROM
  • flash memory For example, at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 510 may include one or more processing units; optionally, the processor 510 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc.
  • the modem processor mainly deals with wireless communication, such as a baseband processor. It can be understood that the foregoing modem processor may not be integrated into the processor 510.
  • the processor 510 is configured to match the N transmission data to be transmitted with the first condition
  • the radio frequency unit 501 is configured to execute the first access process or the second access process according to the matching result
  • M transmission data is transmitted in the first access process, and the N transmission data is not transmitted in the second access process;
  • the M transmission data is the sum of the N transmission data
  • M and N are both positive integers, and M is less than or equal to N
  • the first condition is a restriction condition for the data transmitted during the access process, and the first condition includes: the transmission data corresponds to The first bearer information and/or the first transmission mode matches the configuration information, and the configuration information includes the second bearer information and/or the second transmission mode.
  • processor 510 and radio frequency unit 501 can implement various processes implemented by the terminal in the method embodiment of FIG.
  • the embodiment of the present application also provides a network side device.
  • the network equipment 600 includes an antenna 601, a radio frequency device 602, and a baseband device 603.
  • the antenna 601 is connected to the radio frequency device 602.
  • the radio frequency device 602 receives information through the antenna 601, and sends the received information to the baseband device 603 for processing.
  • the baseband device 603 processes the information to be sent and sends it to the radio frequency device 602, and the radio frequency device 602 processes the received information and sends it out via the antenna 601.
  • the foregoing frequency band processing apparatus may be located in the baseband apparatus 603, and the method executed by the network-side device in the above embodiments may be implemented in the baseband apparatus 603.
  • the baseband apparatus 603 includes a processor 604 and a memory 605.
  • the baseband device 603 may include, for example, at least one baseband board, and multiple chips are arranged on the baseband board, as shown in FIG.
  • the network device shown in the above method embodiment operates.
  • the baseband device 603 may also include a network interface 606 for exchanging information with the radio frequency device 602, and the interface is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device of the embodiment of the present invention further includes: instructions or programs stored in the memory 605 and running on the processor 604, and the processor 604 calls the instructions or programs in the memory 605 to execute the modules shown in FIG. 3
  • the method of implementation and achieve the same technical effect, in order to avoid repetition, so I will not repeat it here.
  • the embodiment of the present application also provides a readable storage medium with a program or instruction stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the foregoing access process processing method embodiment is realized, and can be To achieve the same technical effect, in order to avoid repetition, I will not repeat them here.
  • the processor is the processor in the electronic device described in the foregoing embodiment.
  • the readable storage medium includes a computer readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disks, or optical disks.
  • An embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used to run a network device program or instruction to implement the above-mentioned access process processing
  • the chip includes a processor and a communication interface
  • the communication interface is coupled with the processor
  • the processor is used to run a network device program or instruction to implement the above-mentioned access process processing
  • chips mentioned in the embodiments of the present application may also be referred to as system-level chips, system-on-chips, system-on-chips, or system-on-chips.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to make a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a base station, etc.) execute the methods described in the various embodiments of the present application.
  • a terminal which can be a mobile phone, a computer, a server, an air conditioner, or a base station, etc.
  • the program can be stored in a computer readable storage medium. When executed, it may include the procedures of the above-mentioned method embodiments.
  • the storage medium may be a magnetic disk, an optical disc, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM), etc.
  • modules, units, and sub-units can be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (Digital Signal Processor, DSP), and digital signal processing equipment (DSP Device, DSPD). ), programmable logic devices (Programmable Logic Device, PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, used to execute the present disclosure Described functions in other electronic units or combinations thereof.
  • ASIC application specific integrated circuits
  • DSP Digital Signal Processor
  • DSP Device digital signal processing equipment
  • PLD programmable logic devices
  • Field-Programmable Gate Array Field-Programmable Gate Array
  • FPGA Field-Programmable Gate Array
  • the technology described in the embodiments of the present disclosure can be implemented by modules (for example, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure.
  • the software codes can be stored in the memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.

Landscapes

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

Abstract

本申请公开了一种接入过程处理方法、装置及通信设备，该方法包括：将待传输的N个传输数据与第一条件进行匹配；根据匹配的结果，执行第一接入过程或者第二接入过程；在所述第一接入过程中传输M个传输数据，在所述第二接入过程中不传输所述N个传输数据；所述M个传输数据为所述N个传输数据中与所述第一条件匹配的数据，M和N均为正整数，且M小于或等于N，所述第一条件为接入过程传输的数据的限制条件，所述第一条件包括：传输数据对应的第一承载信息和/或第一传输方式与配置信息匹配，所述配置信息包括第二承载信息和/或第二传输方式。

Description

接入过程处理方法、装置及通信设备
相关申请的交叉引用
本申请主张在2020年6月11日在中国提交的中国专利申请号No.202010531606.3的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，尤其涉及一种接入过程处理方法、装置及通信设备。
背景技术
在新空口(New Radio，NR)系统中，为了支持小数据的发送，网络侧在将终端(User Equipment，UE)从连接态释放到空闲(IDLE)态或去激活(INACTIVE)态的时候，仅保留了UE的主小区组(Master cell group，MCG)上下文配置信息。当UE要进行小数据发送的时候，如果网络侧的系统消息指示支持小数据的发送，则IDLE/INACTIVE态的UE通过上述方式不进入连接态，而直接进行数据的接收或发送。然而，在UE被配置了多个承载和多个小区组的情况下，如何进行数据和连接的恢复是亟需解决的问题。
发明内容
本申请实施例的目的是提供一种接入过程处理方法、装置及通信设备，能够解决在UE被配置了多个承载和多个小区组的情况下，如何进行数据和连接的恢复的问题。
为了解决上述技术问题，本申请是这样实现的：
第一方面，提供了一种接入过程处理方法，包括：
将待传输的N个传输数据与第一条件进行匹配；
根据匹配的结果，执行第一接入过程或者第二接入过程；
其中，在所述第一接入过程中传输M个传输数据，在所述第二接入过程中不传输所述N个传输数据；所述M个传输数据为所述N个传输数据中与 所述第一条件匹配的数据，M和N均为正整数，且M小于或等于N，所述第一条件为接入过程传输的数据的限制条件，所述第一条件包括：传输数据对应的第一承载信息和/或第一传输方式与配置信息匹配，所述配置信息包括第二承载信息和/或第二传输方式。
第二方面，提供了一种接入过程处理装置，包括：
匹配模块，用于将待传输的N个传输数据与第一条件进行匹配；
处理模块，用于根据匹配的结果，执行第一接入过程或者第二接入过程；
其中，在所述第一接入过程中传输M个传输数据，在所述第二接入过程中不传输所述N个传输数据；所述M个传输数据为所述N个传输数据中与所述第一条件匹配的数据，M和N均为正整数，且M小于或等于N，所述第一条件为接入过程传输的数据的限制条件，所述第一条件包括：传输数据对应的第一承载信息和/或第一传输方式与配置信息匹配，所述配置信息包括第二承载信息和/或第二传输方式。
第三方面，提供了一种通信设备，该通信设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第四方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤。
第五方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络设备程序或指令，实现如第一方面所述的方法。
第六方面，提供了一种计算机软件产品，所述计算机软件产品被存储在非易失的存储介质中，所述软件产品被配置成被至少一个处理器执行以实现如第一方面所述的方法的步骤。
第七方面，提供了一种通信设备，所述通信设备被配置成用于执行如第一方面所述的方法。
本申请实施例中，通过待传输的N个传输数据与第一条件进行匹配；根据匹配的结果，执行第一接入过程或者第二接入过程。其中，在所述第一接入过程中传输M个传输数据，在所述第二接入过程中不传输所述N个传输数 据；所述M个传输数据为所述N个传输数据中与所述第一条件匹配的数据；所述第一条件包括：传输数据对应的第一承载信息和/或第一传输方式与配置信息匹配，所述配置信息包括第二承载信息和/或第二传输方式。由于将承载信息和传输方式作为接入过程传输的数据的限制条件，明确了数据和连接的恢复过程，因此本申请实施例解决在UE被配置了多个承载和多个小区组的情况下，如何进行数据和连接的恢复的问题。
附图说明
图1是本申请实施例可应用的一种网络系统的结构图；
图2是本申请实施例提供的一种接入过程处理方法的流程图；
图3是本申请实施例提供的一种通信设备的结构图；
图4是本申请实施例提供的另一种通信设备的结构图；
图5是本申请实施例提供的一种终端的结构图；
图6是本申请实施例提供的一种网络设备的结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用 于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。然而，以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，尽管这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、无线局域网(Wireless Local Area Network，WLAN)接入点、无线保真(Wireless Fidelity，WiFi)节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
为了方便理解，以下对本发明实施例涉及的一些内容进行说明：
一、小数据传输(Small Data Transmission，SDT)。
根据网络设备配置的资源，UE在IDLE/INACTIVE状态的时候，可以通过以下方法发送将数据直接发送给网络设备：
初始接入的4步随机接入过程的Msg3；
初始接入的2步随机接入过程的MsgA；
网络配置的专属上行资源，例如，上行物理上行共享信道(Physical Uplink Shared Channel，PUSCH)资源，即，pre-configured PUSCH；或，预分配的上行资源(Preallocated Uplink Resource，PUR)。
网络设备可以通过以下方式将数据直接发送给UE：
初始接入的4步随机接入过程的Msg4；
初始接入的2步随机接入过程的MsgB；
网络配置的专属上行资源对应的下行反馈资源。
网络侧在将UE从连接态释放到IDLE/INACTIVE态的时候，保留UE的上下文配置信息。当UE要进行小数据发送的时候，如果网络侧的系统消息指示支持小数据的发送，例如支持小于10Kbyte的小数据发送，则IDLE/INACTIVE态的UE通过上述方式不进入连接态，而直接进行数据的接收或发送。
二、新2步随机接入(2-Step Random Access Channel，2-Step RACH)。
步骤0：网络设备给UE配置新2步随机接入的配置信息，如包括：MsgA和MsgB对应的发送资源信息。
步骤1：UE触发2-step RACH过程。将请求信息发送给网络侧，如通过PUSCH发送MsgA。同时UE也可能会发送物理随机接入信道(Physical Random Access Channel，PRACH)信息给网络设备。
步骤2：网络设备发送确认信息给UE，该确认信息为MsgB。如果UE接收MsgB失败，则UE重新发送MsgA。
三、传统4步随机接入过程。
UE的随机接入过程包括以下任一项：
基于竞争的随机接入过程；
基于非竞争的随机接入过程；
其中随机接入过程可以理解为4步随机接入过程，即4-step RACH。
对于“基于竞争的随机接入过程”，UE发送Msg1给网络设备，该Msg1可以理解为随机接入请求。网络设备接收到Msg1后给UE发送Msg2给UE，该Msg2可以理解为随机接入响应(Random Access Response，RAR)消息，该消息中携带了上行授权(uplink grant)信息。UE根据Msg2中的uplink grant，执行媒体接入控制(Medium Access Control，MAC)层组包功能生成MAC协议数据单元(Protocol Data Unit，PDU)，并将该MAC PDU存储在Msg3缓存中，然后UE将Msg3缓存中的MAC PDU通过混合自动重传请求(Hybrid automatic repeat request，HARQ)进程进行发送。网络设备接收到Msg3后发送Msg4给UE，例如，竞争解决标识。UE接收到Msg4判断是否竞争解决成功，如果成功则随机接入过程成功过，否则重新发起随机接入过程。对于重新发起的随机接入过程，当UE又接收到Msg2中的uplink grant后，UE直接从Msg3缓存中取出之前存储的MAC PDU并通过HARQ进程进行发送。UE在随机接入过程完成后会清空随机接入过程的Msg3传输的HARQ缓存。
对于连接的(CONNECTED)UE，其Msg4竞争解决验证为：小区无线网络临时标识(Cell Radio Network Temporary Identifier，C-RNTI)物理下行控制信道(Physical downlink control channel，PDCCH)调度的上行传输为新传。
对于IDLE/INACTIVE UE，其Msg4竞争解决验证为：其接收的“用于承载UE竞争解决方案标识的MAC控制单元(Control Element，CE)”中的“UE竞争解决方案标识(UE Contention Resolution Identity)”信息与其发送的“上行UL(Uplink)公共控制信道(Common Control Channel，CCCH)服务数据单元(Service Data Unit，SDU)”的前48bit匹配。用于承载UE竞争解决方案标识的MAC CE可以成为UE Contention Resolution Identity MAC CE。
四、双连接(Dual Connectivity，DC)。
在NR系统中采用了DC架构中，包括两个MCG和SCG(Secondary Cell Group，辅小区组)，而该MCG对应于网络设备的主节点(Master Node，MN)，而该SCG对应于网络设备的SN(辅节点，Secondary Node)。MCG的主小区 称为PCell(Primary Cell)，SCG的主小区称为PSCell(Primary Secondary Cell)，PCell和PSCell统称为SpCell(Special Cell)。MCG和SCG的辅小区都称为SCell(Secondary Cell)。信令无线承载1(Signaling Radio Bearer 1，SRB1)为UE和MCG之间的信令承载，SRB3为UE和SCG之间的信令承载。
UE的承载类型包括：
MCG无线承载(Radio Bearer，RB):RB对应的1个PDCP和1个RLC都在MCG；
SCG RB：RB对应的1个PDCP和1个RLC都在SCG；
分离(Split)RB：RB对应的1个分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)在MCG或SCG，RB对应的2个无线链路控制(Radio Link Control，RLC)分别在MCG和SCG。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的接入过程处理方法进行详细地说明。
请参见图2，图2是本申请实施例提供的一种接入过程处理方法的流程图，该方法应用于网络设备或终端，如图2所示，包括以下步骤：
步骤201，将待传输的N个传输数据与第一条件进行匹配；
步骤202，根据匹配的结果，执行第一接入过程或者第二接入过程；
其中，在所述第一接入过程中传输M个传输数据，在所述第二接入过程中不传输所述N个传输数据；所述M个传输数据为所述N个传输数据中与所述第一条件匹配的数据，M和N均为正整数，且M小于或等于N，所述第一条件为接入过程传输的数据的限制条件，所述第一条件包括：传输数据对应的第一承载信息和/或第一传输方式与配置信息匹配，所述配置信息包括第二承载信息和/或第二传输方式。
上述第一条件可以理解为直接的数据发送或接收方式的限制条件。本申请实施例中，针对小数据发送或接收可以采用“直接的数据发送或接收”。可选地，上述N个传输数据中部分或者全部的数据均为小数据，上述M个传输数据可以理解为N个传输数据中满足“直接的数据发送或接收方式”的传输数据。
上述配置信息可以是网络设备配置或协议约定，具体可以包括第二承载 信息和第二传输方式中的至少一项。应理解，上述第一条件与配置信息对应，例如，当配置信息仅包括第二承载信息时，上述第一条件为传输数据对应的第一承载信息与第二承载信息匹配；当配置信息仅包括第二传输方式时，上述第一条件可以理解为传输数据对应的第一传输方式与第二传输方式匹配。当配置信息包括第二承载信息和第二传输方式时，上述第一条件包括以下至少一项：
传输数据对应的第一承载信息与第二承载信息匹配；
传输数据对应的第一传输方式与第二传输方式匹配。
其中，匹配可以理解为承载信息相同和/或传输方式相同，例如，传输数据对应的第一承载信息与第二承载信息匹配可以理解为传输数据对应的第一承载信息与第二承载信息中的部分承载信息相同；传输数据对应的第一传输方式与第二传输方式匹配可以理解为，传输数据对应的第一传输方式与第二传输方式的部分或者全部传输方式相同。
应理解，待传输可以理解为待发送或者待接收。传输M个传输数据可以理解为发送M个传输数据或者接收M个传输数据。例如，可以由网络设备在执行第一接入过程中发送M个传输数据，终端在执行第一接入过程中接收M个传输数据；或者是网络设备在执行第一接入过程中接收M个传输数据，终端在执行第一接入过程中发送M个传输数据。
本申请实施例中，通过待传输的N个传输数据与第一条件进行匹配；根据匹配的结果，执行第一接入过程或者第二接入过程。其中，在所述第一接入过程中传输M个传输数据，在所述第二接入过程中不传输所述N个传输数据；所述M个传输数据为所述N个传输数据中与所述第一条件匹配的数据；所述第一条件包括：传输数据对应的第一承载信息和/或第一传输方式与配置信息匹配，所述配置信息包括第二承载信息和/或第二传输方式。由于将承载信息和传输方式作为接入过程传输的数据的限制条件，明确了数据和连接的恢复过程，因此本申请实施例解决在UE被配置了多个承载和多个小区组的情况下，如何进行数据和连接的恢复的问题。
本申请实施例中，执行第一接入过程，可以理解为允许采用“直接的数据发送或接收”方式传输上述M个传输数据。上述配置信息可以理解为直接 的数据接收或发送的方式的配置信息。
可选地，在一实施例中，所述根据匹配的结果，执行第一接入过程或者第二接入过程包括：
在所述N个传输数据中至少一个传输数据满足所述第一条件的情况下，执行所述第一接入过程；
或，在所述N个传输数据均未满足所述第一条件的情况下，执行所述第二接入过程。
本申请实施例中，上述第二接入过程可以理解为在初始接入过程中不传输上述传输数据。上述第一接入过程可以理解为在初始接入过程中传输满足第一条件的传输数据。对于不满足预设条件的传输数据在接入过程完成后，在终端进入连接态的情况下，可以进行发送。这样，可以减小满足第一条件的传输数据的传输时延。例如，网络设备配置或协议约定只有MCG DRB可以采用直接的数据接收或发送，而UE的MCG DRB和SCG DRB都有数据发送。则，UE仅对MCG DRB采用“直接的数据发送或接收”，SCG DRB仍然是挂起状态。
可选地，在另一实施例中，所述根据匹配的结果，执行第一接入过程或者第二接入过程包括：
在所述N个传输数据均满足所述第一条件的情况下，执行所述第一接入过程；
或，在所述N个传输数据中至少一个传输数据未满足所述第一条件的情况下，执行所述第二接入过程。
本申请实施例中，由于仅在N个传输数据满足第一预设条件的情况下，在初始接入过程中传输N个传输数据，在至少一个传输数据未满足所述第一条件的情况下，则在初始接入过程中不传输N个传输数据中的任一个传输数据，这样，可以在所述N个传输数据均满足所述第一条件的情况下，直接传输N个传输数据，在至少一个传输数据不满足第一条件的情况下，可以缩短执行接入过程的时间。
可选地，上述第二承载信息可以包括以下至少一项：承载标识和承载类型。
本实施例中，上述第一承载信息所包含的内容为第二承载信息的子集或者全集，例如，上述第二承载信息包括承载标识时，上述第一承载信息可以理解为承载标识；上述第二承载信息包括承载类型时，上述第一承载信息可以理解为承载类型。上述第二承载信息包括承载标识和承载类型时，上述第一承载信息可以理解为承载标识和承载类型中的至少一项。
其中，上述承载类型包括以下至少一项：MCG数据无线承载(Data Radio Bearer，DRB)、SCG DRB、MCG分离DRB(MCG Split DRB)和SCG分离DRB(SCG Split DRB)。
MCG Split DRB可以理解为：承载的PDCP在MCG，承载的2个RLC分别在MCG和SCG。SCG Split DRB可以理解为：承载的PDCP在SCG，承载的2个RLC分别在MCG和SCG。
上述承载标识包括以下至少一项：DRB标识、服务质量流(Quality of Service flow，QoS flow)标识、协议数据单元会话标识和小区组标识。
需要说明的是，在一实施例中，当某一个传输数据对应的承载类型包含于第二承载信息时，则可以确定该传输数据对应的第一承载信息与配置信息匹配。在另一实施例中，当某一个传输数据对应的承载标识包含于第二承载信息时，则可以确定该传输数据对应的第一承载信息与配置信息匹配。在又一实施例中，当某一个传输数据对应的承载标识和承载类型均包含于第二承载信息时，则可以确定该传输数据对应的第一承载信息与配置信息匹配。
可选地，所述第二传输方式包括以下至少一项：数据发送方式和数据接收方式。
其中，上述数据发送方式包括以下至少一项：
终端在4步随机接入过程中的Msg3中发送数据；
终端在2步随机接入过程中的MsgA中发送数据；
终端在配置的专属上行资源中发送数据；
网络设备在4步随机接入过程中的Msg4中发送数据；
网络设备在2步随机接入过程中的MsgB中发送数据；
网络设备在配置的专属上行资源对应的下行资源中发送数据。
相应的，上述数据接收方式包括以下至少一项：
网络设备在4步随机接入过程中的Msg3中接收数据；
网络设备在2步随机接入过程中的MsgB中接收数据；
网络设备在配置的专属上行资源中接收数据；
终端在4步随机接入过程中的Msg4中接收数据；
终端在2步随机接入过程中的MsgB中接收数据；
终端在配置的专属上行资源对应的下行资源中接收数据。
本实施例中，上述专属上行资源可以理解为专属上行PUSCH资源。应理解，通常的上述第一传输方式可以理解为某一种数据发送方式或者某一种数据接收方式。需要说明的是，在本申请实施例中，当上述传输数据对应的第一传输方式与第二传输方式中的某一种传输方式相同时，可以确定传输数据对应的第一传输方式与配置信息匹配。
可选地，上述N个传输数据的数据类型可以包括控制信令和用户数据其中至少之一。在一实施例中，所述M个传输数据包括以下至少一项：
DRB的数据；
服务质量流的数据
PDU会话(PDU session)的数据；
承载在SRB中的用户面数据。
其中，用户面数据通过在CCCH消息加入容器(container)，该容器中包含了用户的QoS flow或PDU session的数据。
应理解，上述配置信息可以由网络设备配置或协议约定。
一实施例中，在所述配置信息由网络设备配置的情况下，所述配置信息承载于无线资源控制RRC释放(RRCRelease)消息或系统信息块(System Information Block，SIB)消息中。
可选地，所述将待传输的N个传输数据与第一条件进行匹配之前，所述方法还包括：
传输指示信息，所述指示信息用于指示终端保留上下文配置，所述上下文配置用于恢复连接和/或恢复数据传输。
本申请实施例中，上述上下文配置可以包括DRB配置和安全配置等。该传输指示信息可以理解为suspend指示信息。例如，网络设备在RRCRelease 消息中，发送suspend指示信息，通过将CONNECTED态终端释放到IDLE/INACTVIE态时，指示终端保留上下文配置。
应理解，上述配置信息可以与传输指示信息在同一消息中发送，也可以在不同的消息中发送，在此不做进一步的限定。
可选地，执行所述第一接入过程包括：
在传输所述M个传输数据之前，执行第一操作；
其中，所述第一操作包括以下任一项：
操作1，在所述M个传输数据通过MCG承载发送的情况下，恢复承载的MCG的配置；
操作2，在所述M个传输数据通过SCG承载发送的情况下，恢复承载的SCG的配置；
操作3，在所述M个传输数据通过MCG分离承载发送的情况下，恢复承载的MCG的配置；
操作4，在所述M个传输数据通过SCG分离承载发送的情况下，恢复承载的SCG的配置；
操作5，在所述M个传输数据通过SCG分离承载发送的情况下，恢复SCG分离承载的PDCP配置和MCG的配置。
针对上述操作1，网络设备配置或协议约定只有MCG DRB可以采用直接的数据接收或发送，而UE要发送的数据对应的DRB为MCG DRB，UE采用Msg3发送上行数据，则UE在用Msg3发送上行数据前恢复其之前存储的MCG对应的配置信息。例如，该配置信息可以包括：MCG对应的SRB和DRB的PDCP配置信息(如，建立PDCP实体或重建PDCP实体；恢复PDCP状态变量)；MCG的安全性上下文；MCG的(头)压缩功能。
针对上述操作2，网络设备配置或协议约定SCG DRB可以采用直接的数据接收或发送，而UE要发送的数据对应的DRB为SCG DRB，UE采用Msg3发送上行数据，则UE在用Msg3发送上行数据前恢复其之前存储的SCG对应的配置信息。例如，该配置信息可以包括：SCG对应的SRB和DRB的PDCP配置信息；SCG的安全性上下文；SCG的(头)压缩功能。
针对上述操作3，网络设备配置或协议约定MCG split DRB可以采用直 接的数据接收或发送，而UE要发送的数据对应的DRB为MCG split DRB，UE采用Msg3发送上行数据，则UE在用Msg3发送上行数据前恢复其之前存储的MCG对应的配置信息。例如，该配置信息可以包括：MCG对应的SRB和DRB的PDCP配置信息；MCG的安全性上下文；MCG的(头)压缩功能。
针对上述操作4，网络设备配置或协议约定SCG split DRB可以采用直接的数据接收或发送，而UE要发送的数据对应的DRB为SCG split DRB，UE采用Msg3发送上行数据，则UE在用Msg3发送上行数据前恢复其之前存储的SCG对应的配置信息。例如，该配置信息可以包括：SCG对应的SRB和DRB的PDCP配置信息；SCG的安全性上下文；SCG的(头)压缩功能。
针对上述操作5，网络侧配置或协议约定SCG split DRB可以采用直接的数据接收或发送，而UE要发送的数据对应的DRB为SCG split DRB，UE采用Msg3发送上行数据，则UE在用Msg3发送上行数据前恢复其之前存储的SCG分离承载对应的PDCP配置信息、MCG的该SCG分离承载的RLC配置和MCG的SRB的配置。此时，SCG split DRB的RLC配置仍然挂起，因此该SCG split DRB的数据为通过其MCG RLC进行发送。其中，SCG分离承载对应的PDCP配置信息可以包括：SCG分离承载对应的PDCP配置信息，该PDCP配置信息可以包括建立PDCP实体或重建PDCP实体；恢复PDCP状态变量；SCG的安全性上下文；SCG的(头)压缩功能。
其中，一实施例中，在仅恢复承载的MCG的配置的情况下，所述第一操作还包括：保留并挂起承载的SCG的配置。
另一实施例中，在仅恢复承载的SCG的配置的情况下，所述第一操作还包括：保留并挂起承载的MCG的配置。
又一实施例中，在恢复SCG分离承载的PDCP配置和MCG的配置的情况下，所述第一操作还包括以下至少一项：
恢复所述MCG的配置中包括所述SCG分离承载的MCG无线链路控制的配置；
恢复所述MCG的配置中包括MCG信令无线承载的配置；
保留并挂起所述MCG配置中除所述SCG分离承载外的其他DRB的配置。
应理解，在一实施例中，直接的数据接收或发送的限制条件还可以包括其他限制条件，也就是说，上述第一条件还可以包括以下至少一项：
所述传输数据的大小等于或小于或大于门限值预设的第一门限值；
终端测量的小区信号强度等于或小于或大于门限值预设的第二门限值。
本实施例中，在满足所有的第一条件的情况下，则确定允许采用直接的数据接收和发送的方式进行数据传输。
为了更好的理解本申请，以下以终端发送或者接收数据为例，对本申请具体的实现过程进行详细说明。
步骤1：网络设备给UE发送保留上下文配置的指示信息，指示UE保留其上下文配置。其中，该上下文配置用于UE恢复连接和/或恢复数据收发使用。例如，网络设备在将CONNECTED态UE释放到IDLE/INACTVIE态时，在RRCRelease消息中，发送suspend指示信息，该suspend指示信息用于指示UE保留上下文配置。
可选地，网络设备配置或协议约定UE的“直接的数据接收或发送的方式的配置信息”。其中，该“直接的数据接收或发送的方式的配置信息”包括以下至少一项：
直接的数据接收或发送的方式；
采用直接的数据接收或发送的承载信息。
上述“保留上下文配置的指示信息”和“直接的数据接收或发送的方式的配置信息”可以在同一消息中发送，例如，通过RRCRelease消息发送。也可以在不同消息中发送，例如“保留上下文配置的指示信息”通过RRCRelease消息发送，“直接的数据接收或发送的方式的配置信息”通过SIB消息发送。
可选地，该“直接的数据接收或发送”的“数据类型”包括以下至少一种：
DRB的数据
QoS flow的数据
PDU session的数据
承载在SRB中的用户面数据。
可选地，该“直接的数据接收或发送的方式”包括以下至少一种：
直接的数据发送方式，例如，上行数据发送；
直接的数据接收方式，例如，下行数据接收。
其中，直接的数据发送方式包括以下至少一种：
4步随机接入过程的Msg3中发送数据；
2步随机接入过程的MsgA中发送数据；
网络配置的专属上行PUSCH资源中发送数据。
其中，直接的数据接收方式包括以下至少一种：
4步随机接入过程的Msg4中接收数据；
2步随机接入过程的MsgB中接收数据；
网络配置的专属上行资源对应的下行资源中接收数据；例如，UE在专属PUSCH资源中发送DRB数据或SRB请求消息后，UE在该PUSCH对应的PDCCH资源中通过监听特定UE标识获取物理下行共享信道(Physical downlink shared channel，PDSCH)调度信息，该PDSCH中包括了UE的DRB的下行接收数据。
可选地，该“采用直接的数据接收或发送的承载信息”包括以下至少一项：
采用直接的数据接收或发送的承载类型；
采用直接的数据接收或发送的承载标识。
其中，“采用直接的数据接收或发送的承载信息”包括以下至少一项：
MCG DRB；
SCG DRB；
MCG Split DRB，即承载的PDCP在MCG，承载的2个RLC分别在MCG和SCG；
SCG Split DRB，即承载的PDCP在SCG，承载的2个RLC分别在MCG和SCG。
其中，“采用直接的数据接收或发送的承载标识”包括以下至少一项：
DRB标识；
QoS flow标识；
PDU session标识；
小区组标识，例如MCG标识或SCG标识。
步骤2：当UE有数据发送或接收的时候，且该数据发送或接收的条件满足网络侧配置或协议约定的直接的数据接收或发送的限制条件下，则UE允许触发直接的数据发送或接收。否则，UE触发第二接入过程，以建立连接或恢复连接。其中，该“直接的数据接收或发送的限制条件”包括以下至少一项：
条件1：该数据对应的承载标识与网络设备配置或协议约定的“采用直接的数据接收或发送的承载标识”相同。
条件2：该数据对应的数据发送方式与网络侧配置或协议约定的“直接的数据接收或发送的方式”相同。例如，网络设备配置或协议约定可以采用“4步随机接入过程的Msg3中发送数据”，而UE要发送的数据支持的发送方式也为“4步随机接入过程的Msg3中发送数据”。
可选地，本实施例中，直接的数据接收或发送的限制条件还可以与其他限制条件组合使用，其他限制条件可以包括以下至少一项：
所述传输数据的大小小于或等于第一门限值；
终端测量的小区信号强度大于或等于第二门限值。
当然在其他实施例中，也可以设置传输数据的大小大于或等于第三门限值，终端测量的小区信号强度小于或等于第四门限值，在此不做进一步的限定。
对于条件1，如果UE有部分数据对应的承载信息与网络设备配置或协议约定的“采用直接的数据接收或发送的承载信息”相同，而部分数据对应的承载信息与网络侧配置或协议约定的“采用直接的数据接收或发送的承载指示”不同的情况，根据网络侧配置或协议约定，UE的处理方式包括以下任意一种：
对于数据对应的承载信息与网络侧配置或协议约定的“采用直接的数据接收或发送的承载信息”相同的数据，采用“直接的数据接收或发送”方式。例如，网络设备配置或协议约定只有MCG DRB可以采用直接的数据接收或发送，而UE的MCG DRB和SCG DRB都有数据发送。则，UE仅对MCG DRB采用“直接的数据发送或接收”，SCG DRB仍然是挂起状态。
采用常规连接建立过程或者连接恢复过程。
其中，对于“直接的数据发送或接收”的UE行为包括以下任意一种：
方法1：如果该“直接的数据发送或接收”的数据为通过MCG承载发送，则UE在采用“直接的数据发送或接收”时恢复承载的MCG的配置。例如网络设备配置或协议约定只有MCG DRB可以采用直接的数据接收或发送，而UE要发送的数据对应的DRB为MCG DRB，UE采用Msg3发送上行数据，则UE在用Msg3发送上行数据前恢复其之前存储的MCG对应的配置信息。例如，该配置信息可以包括：MCG对应的SRB和DRB的PDCP配置信息(如，建立PDCP实体或重建PDCP实体；恢复PDCP状态变量)；MCG的安全性上下文；MCG的(头)压缩功能。
方法2：如果该“直接的数据发送或接收”的数据为通过SCG承载发送，则UE在采用“直接的数据发送或接收”时恢复承载的SCG的配置。例如网络设备配置或协议约定SCG DRB可以采用直接的数据接收或发送，而UE要发送的数据对应的DRB为SCG DRB，UE采用Msg3发送上行数据，则UE在用Msg3发送上行数据前恢复其之前存储的SCG对应的配置信息。例如，该配置信息可以包括：SCG对应的SRB和DRB的PDCP配置信息；SCG的安全性上下文；SCG的(头)压缩功能。
方法3：如果该“直接的数据发送或接收”的数据为通过MCG分离承载发送，则UE在采用“直接的数据发送或接收”时恢复承载的MCG的配置。例如，网络设备配置或协议约定MCG split DRB可以采用直接的数据接收或发送，而UE要发送的数据对应的DRB为MCG split DRB，UE采用Msg3发送上行数据，则UE在用Msg3发送上行数据前恢复其之前存储的MCG对应的配置信息。例如，该配置信息可以包括：MCG对应的SRB和DRB的PDCP配置信息；MCG的安全性上下文；MCG的(头)压缩功能。
方法4：如果该“直接的数据发送或接收”的数据为通过SCG分离承载发送，则UE在采用“直接的数据发送或接收”时恢复承载的SCG的配置。例如，网络设备配置或协议约定SCG split DRB可以采用直接的数据接收或发送，而UE要发送的数据对应的DRB为SCG split DRB，UE采用Msg3发送上行数据，则UE在用Msg3发送上行数据前恢复其之前存储的SCG对应 的配置信息。例如，该配置信息可以包括：SCG对应的SRB和DRB的PDCP配置信息；SCG的安全性上下文；SCG的(头)压缩功能。
方法5：如果该“直接的数据发送或接收”的数据为通过SCG分离承载发送，则UE在采用“直接的数据发送或接收”时恢复SCG分离承载的PDCP配置和MCG的配置。例如，网络侧配置或协议约定SCG split DRB可以采用直接的数据接收或发送，而UE要发送的数据对应的DRB为SCG split DRB，UE采用Msg3发送上行数据，则UE在用Msg3发送上行数据前恢复其之前存储的SCG分离承载对应的PDCP配置信息、MCG的该SCG分离承载的RLC配置和MCG的SRB的配置。此时，SCG split DRB的RLC配置仍然挂起，因此该SCG split DRB的数据为通过其MCG RLC进行发送。其中，SCG分离承载对应的PDCP配置信息可以包括：SCG分离承载对应的PDCP配置信息，该PDCP配置信息可以包括建立PDCP实体或重建PDCP实体；恢复PDCP状态变量；SCG的安全性上下文；SCG的(头)压缩功能。
对于方法1和方法3，可选地，UE的行为还可以包括：如果UE存储的配置信息包括承载的SCG的配置信息，则UE根据网络侧配置或协议约定，删除或保留该承载的SCG配置信息。一实施例中，UE在恢复承载的MCG配置的同时删除承载的SCG配置。另一实施例中，UE在恢复承载的MCG配置的同时保留但是保持挂起(即，不使用)该承载的SCG配置，在收到网络侧指示的恢复SCG配置信息后(如，接收到RRCResume消息)，UE再执行恢复承载的SCG配置过程。例如，恢复承载的SCG的DRB和SRB的配置信息(如，PDCP和RLC配置)；恢复SCG的安全上下文等。
对于方法2和方法4，可选地，UE的行为还可以包括：UE根据网络侧配置或协议约定，保留该承载的MCG配置信息。例如，UE在恢复SCG配置的同时保留但是保持挂起(即，不使用)该承载的MCG配置，在收到网络设备指示的恢复MCG配置信息后(如，接收到RRCResume消息)，UE再执行恢复承载的MCG配置过程。例如，恢复承载的MCG的DRB和SRB的配置信息等。
对于方法5，可选地，UE的行为还包括以下至少一项：
该恢复MCG的配置包括该SCG分离承载的MCG RLC配置。
该恢复MCG的配置包括该MCG SRB的配置。
该MCG配置中除SCG分离承载外的其他DRB的配置保留且保持挂起状态。例如，MCG DRB的配置保留。
对于上述“直接的数据发送或接收”，可选地，数据发送端可以指示发送的数据来自哪个小区组。例如，UE指示发送的MAC PDU中的逻辑信道号(Logical Channel ID，LCID)-1为MCG或SCG的LCID-1。
其中，该常规连接建立(或恢复)过程可以理解为在初始接入过程完成前不进行数据承载的数据发送或接收的过程。例如，UE在Msg3或Msg4中只发送连接恢复请求消息，而不发送DRB中的数据。UE只有在接收到网络侧发送的连接恢复消息后，才恢复数据承载的数据收发。
需要说明的是，本申请实施例提供的接入过程处理方法，执行主体可以为接入过程处理装置，或者，该接入过程处理装置中的用于执行接入过程处理方法的控制模块。本申请实施例中以接入过程处理装置执行接入过程处理方法为例，说明本申请实施例提供的接入过程处理装置。
请参见图3，图3是本申请实施例提供的一种接入过程处理装置的结构图，如图3所示，接入过程处理装置300包括：
匹配模块301，用于将待传输的N个传输数据与第一条件进行匹配；
处理模块302，用于根据匹配的结果，执行第一接入过程或者第二接入过程；
其中，在所述第一接入过程中传输M个传输数据，在所述第二接入过程中不传输所述N个传输数据；所述M个传输数据为所述N个传输数据中与所述第一条件匹配的数据，M和N均为正整数，且M小于或等于N，所述第一条件为接入过程传输的数据的限制条件，所述第一条件包括：传输数据对应的第一承载信息和/或第一传输方式与配置信息匹配，所述配置信息包括第二承载信息和/或第二传输方式。
可选地，所述处理模块302具体用于：在所述N个传输数据中至少一个传输数据满足所述第一条件的情况下，执行所述第一接入过程；或，在所述N个传输数据均未满足所述第一条件的情况下，执行所述第二接入过程。
可选地，所述处理模块302具体用于：在所述N个传输数据均满足所述 第一条件的情况下，执行所述第一接入过程；或，在所述N个传输数据中至少一个传输数据未满足所述第一条件的情况下，执行所述第二接入过程。
可选地，所述第二承载信息包括以下至少一项：承载标识和承载类型。
可选地，所述承载类型包括以下至少一项：主小区组MCG数据无线承载DRB、辅小区组SCG DRB、MCG分离DRB和SCG分离DRB。
可选地，所述承载标识包括以下至少一项：DRB标识、服务质量流标识、协议数据单元会话标识和小区组标识。
可选地，所述第二传输方式包括以下至少一项：数据发送方式和数据接收方式。
可选地，所述数据发送方式包括以下至少一项：
终端在4步随机接入过程中的Msg3中发送数据；
终端在2步随机接入过程中的MsgA中发送数据；
终端在配置的专属上行资源中发送数据；
网络设备在4步随机接入过程中的Msg4中发送数据；
网络设备在2步随机接入过程中的MsgB中发送数据；
网络设备在配置的专属上行资源对应的下行资源中发送数据。
可选地，所述数据接收方式包括以下至少一项：
网络设备在4步随机接入过程中的Msg3中接收数据；
网络设备在2步随机接入过程中的MsgB中接收数据；
网络设备在配置的专属上行资源中接收数据；
终端在4步随机接入过程中的Msg4中接收数据；
终端在2步随机接入过程中的MsgB中接收数据；
终端在配置的专属上行资源对应的下行资源中接收数据。
可选地，所述M个传输数据包括以下至少一项：
DRB的数据；
服务质量流的数据
PDU会话的数据；
承载在信令无线承载SRB中的用户面数据。
可选地，所述配置信息由网络设备配置或协议约定。
可选地，在所述配置信息由网络设备配置的情况下，所述配置信息承载于无线资源控制RRC释放消息或系统信息块消息中。
可选地，所述将待传输的N个传输数据与第一条件进行匹配之前，所述方法还包括：
传输指示信息，所述指示信息用于指示终端保留上下文配置，所述上下文配置用于恢复连接和/或恢复数据传输。
可选地，执行所述第一接入过程包括：
在传输所述M个传输数据之前，执行第一操作；
其中，所述第一操作包括以下任一项：
在所述M个传输数据通过MCG承载发送的情况下，恢复承载的MCG的配置；
在所述M个传输数据通过SCG承载发送的情况下，恢复承载的SCG的配置；
在所述M个传输数据通过MCG分离承载发送的情况下，恢复承载的MCG的配置；
在所述M个传输数据通过SCG分离承载发送的情况下，恢复承载的SCG的配置；
在所述M个传输数据通过SCG分离承载发送的情况下，恢复SCG分离承载的PDCP配置和MCG的配置。
可选地，在仅恢复承载的MCG的配置的情况下，所述第一操作还包括：保留并挂起承载的SCG的配置。
可选地，在仅恢复承载的SCG的配置的情况下，所述第一操作还包括：保留并挂起承载的MCG的配置。
可选地，在恢复SCG分离承载的PDCP配置和MCG的配置的情况下，所述第一操作还包括以下至少一项：
恢复所述MCG的配置中包括所述SCG分离承载的MCG无线链路控制的配置；
恢复所述MCG的配置中包括MCG信令无线承载的配置；
保留并挂起所述MCG配置中除所述SCG分离承载外的其他DRB的配 置。
本申请实施例提供的接入过程处理装置能够实现图2的方法实施例中各个过程，为避免重复，这里不再赘述。
本申请实施例中的接入过程处理装置可以是装置，也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的接入过程处理装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的接入过程处理装置能够实现图2的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图4所示，本申请实施例还提供一种通信设备400，包括处理器401，存储器402，存储在存储器402上并可在所述处理器401上运行的程序或指令，例如，该通信设备400为终端时，该程序或指令被处理器401执行时实现上述接入过程处理方法实施例的各个过程，且能达到相同的技术效果。该通信设备400为网络侧设备时，该程序或指令被处理器401执行时实现上述接入过程处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
图5为实现本申请各个实施例的一种终端的硬件结构示意图。
该终端500包括但不限于：射频单元501、网络模块502、音频输出单元503、输入单元504、传感器505、显示单元506、用户输入单元507、接口单元508、存储器509以及处理器510等部件。
本领域技术人员可以理解，终端500还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器510逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图5中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或 者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元504可以包括图形处理器(Graphics Processing Unit，GPU)5041和麦克风5042，图形处理器5041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元506可包括显示面板5061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板5061。用户输入单元507包括触控面板5071以及其他输入设备5072。触控面板5071，也称为触摸屏。触控面板5071可包括触摸检测装置和触摸控制器两个部分。其他输入设备5072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元501将来自网络侧设备的下行数据接收后，给处理器510处理；另外，将上行的数据发送给网络设备。通常，射频单元501包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器509可用于存储软件程序或指令以及各种数据。存储器109可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器509可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器510可包括一个或多个处理单元；可选的，处理器510可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器510中。
其中，处理器510，用于将待传输的N个传输数据与第一条件进行匹配；
射频单元501，用于根据匹配的结果，执行第一接入过程或者第二接入 过程；
其中，在所述第一接入过程中传输M个传输数据，在所述第二接入过程中不传输所述N个传输数据；所述M个传输数据为所述N个传输数据中与所述第一条件匹配的数据，M和N均为正整数，且M小于或等于N，所述第一条件为接入过程传输的数据的限制条件，所述第一条件包括：传输数据对应的第一承载信息和/或第一传输方式与配置信息匹配，所述配置信息包括第二承载信息和/或第二传输方式。
应理解，本实施例中，上述处理器510和射频单元501能够实现图2的方法实施例中终端实现的各个过程，为避免重复，这里不再赘述。
具体地，本申请实施例还提供了一种网络侧设备。如图6所示，该网络设备600包括：天线601、射频装置602、基带装置603。天线601与射频装置602连接。在上行方向上，射频装置602通过天线601接收信息，将接收的信息发送给基带装置603进行处理。在下行方向上，基带装置603对要发送的信息进行处理，并发送给射频装置602，射频装置602对收到的信息进行处理后经过天线601发送出去。
上述频带处理装置可以位于基带装置603中，以上实施例中网络侧设备执行的方法可以在基带装置603中实现，该基带装置603包括处理器604和存储器605。
基带装置603例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图6所示，其中一个芯片例如为处理器604，与存储器605连接，以调用存储器605中的程序，执行以上方法实施例中所示的网络设备操作。
该基带装置603还可以包括网络接口606，用于与射频装置602交互信息，该接口例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本发明实施例的网络侧设备还包括：存储在存储器605上并可在处理器604上运行的指令或程序，处理器604调用存储器605中的指令或程序执行图3所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述接入过程处理方法实施例 的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的电子设备中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络设备程序或指令，实现上述接入过程处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片、系统芯片、芯片系统或片上系统芯片等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应 过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者基站等)执行本申请各个实施例所述的方法。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来控制相关的硬件来完成，所述的程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储器(Read-Only Memory，ROM)或随机存取存储器(Random Access Memory，RAM)等。
可以理解的是，本公开实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，模块、单元、子单元可 以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processor，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本公开实施例所述功能的模块(例如过程、函数等)来实现本公开实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (32)

  1. 一种接入过程处理方法，包括：
    将待传输的N个传输数据与第一条件进行匹配；
    根据匹配的结果，执行第一接入过程或者第二接入过程；
    其中，在所述第一接入过程中传输M个传输数据，在所述第二接入过程中不传输所述N个传输数据；所述M个传输数据为所述N个传输数据中与所述第一条件匹配的数据，M和N均为正整数，且M小于或等于N，所述第一条件为接入过程传输的数据的限制条件，所述第一条件包括：传输数据对应的第一承载信息和/或第一传输方式与配置信息匹配，所述配置信息包括第二承载信息和/或第二传输方式。
  2. 根据权利要求1所述的方法，其中，所述根据匹配的结果，执行第一接入过程或者第二接入过程包括：
    在所述N个传输数据中至少一个传输数据满足所述第一条件的情况下，执行所述第一接入过程；
    或，在所述N个传输数据均未满足所述第一条件的情况下，执行所述第二接入过程。
  3. 根据权利要求1所述的方法，其中，所述根据匹配的结果，执行第一接入过程或者第二接入过程包括：
    在所述N个传输数据均满足所述第一条件的情况下，执行所述第一接入过程；
    或，在所述N个传输数据中至少一个传输数据未满足所述第一条件的情况下，执行所述第二接入过程。
  4. 根据权利要求1所述的方法，其中，所述第二承载信息包括以下至少一项：承载标识和承载类型。
  5. 根据权利要求4所述的方法，其中，所述承载类型包括以下至少一项：主小区组MCG数据无线承载DRB、辅小区组SCG DRB、MCG分离DRB和SCG分离DRB。
  6. 根据权利要求4所述的方法，其中，所述承载标识包括以下至少一项： DRB标识、服务质量流标识、协议数据单元会话标识和小区组标识。
  7. 根据权利要求1所述的方法，其中，所述第二传输方式包括以下至少一项：数据发送方式和数据接收方式。
  8. 根据权利要求7所述的方法，其中，所述数据发送方式包括以下至少一项：
    终端在4步随机接入过程中的Msg3中发送数据；
    终端在2步随机接入过程中的MsgA中发送数据；
    终端在配置的专属上行资源中发送数据；
    网络设备在4步随机接入过程中的Msg4中发送数据；
    网络设备在2步随机接入过程中的MsgB中发送数据；
    网络设备在配置的专属上行资源对应的下行资源中发送数据。
  9. 根据权利要求7所述的方法，其中，所述数据接收方式包括以下至少一项：
    网络设备在4步随机接入过程中的Msg3中接收数据；
    网络设备在2步随机接入过程中的MsgB中接收数据；
    网络设备在配置的专属上行资源中接收数据；
    终端在4步随机接入过程中的Msg4中接收数据；
    终端在2步随机接入过程中的MsgB中接收数据；
    终端在配置的专属上行资源对应的下行资源中接收数据。
  10. 根据权利要求1所述的方法，其中，所述M个传输数据包括以下至少一项：
    DRB的数据；
    服务质量流的数据
    协议数据单元PDU会话的数据；
    承载在信令无线承载SRB中的用户面数据。
  11. 根据权利要求1所述的方法，其中，所述配置信息由网络设备配置或协议约定。
  12. 根据权利要求11所述的方法，其中，在所述配置信息由网络设备配置的情况下，所述配置信息承载于无线资源控制RRC释放消息或系统信息块 消息中。
  13. 根据权利要求1所述的方法，其中，所述将待传输的N个传输数据与第一条件进行匹配之前，所述方法还包括：
    传输指示信息，所述指示信息用于指示终端保留上下文配置，所述上下文配置用于恢复连接和/或恢复数据传输。
  14. 根据权利要求1所述的方法，其中，执行所述第一接入过程包括：
    在传输所述M个传输数据之前，执行第一操作；
    其中，所述第一操作包括以下任一项：
    在所述M个传输数据通过MCG承载发送的情况下，恢复承载的MCG的配置；
    在所述M个传输数据通过SCG承载发送的情况下，恢复承载的SCG的配置；
    在所述M个传输数据通过MCG分离承载发送的情况下，恢复承载的MCG的配置；
    在所述M个传输数据通过SCG分离承载发送的情况下，恢复承载的SCG的配置；
    在所述M个传输数据通过SCG分离承载发送的情况下，恢复SCG分离承载的PDCP配置和MCG的配置。
  15. 根据权利要求14所述的方法，其中，在仅恢复承载的MCG的配置的情况下，所述第一操作还包括：保留并挂起承载的SCG的配置。
  16. 根据权利要求14所述的方法，其中，在仅恢复承载的SCG的配置的情况下，所述第一操作还包括：保留并挂起承载的MCG的配置。
  17. 根据权利要求14所述的方法，其中，在恢复SCG分离承载的PDCP配置和MCG的配置的情况下，所述第一操作还包括以下至少一项：
    恢复所述MCG的配置中包括所述SCG分离承载的MCG无线链路控制的配置；
    恢复所述MCG的配置中包括MCG信令无线承载的配置；
    保留并挂起所述MCG配置中除所述SCG分离承载外的其他DRB的配置。
  18. 一种接入过程处理装置，包括：
    匹配模块，用于将待传输的N个传输数据与第一条件进行匹配；
    处理模块，用于根据匹配的结果，执行第一接入过程或者第二接入过程；
    其中，在所述第一接入过程中传输M个传输数据，在所述第二接入过程中不传输所述N个传输数据；所述M个传输数据为所述N个传输数据中与所述第一条件匹配的数据，M和N均为正整数，且M小于或等于N，所述第一条件为接入过程传输的数据的限制条件，所述第一条件包括：传输数据对应的第一承载信息和/或第一传输方式与配置信息匹配，所述配置信息包括第二承载信息和/或第二传输方式。
  19. 根据权利要求18所述的装置，其中，所述处理模块具体用于：在所述N个传输数据中至少一个传输数据满足所述第一条件的情况下，执行所述第一接入过程；或，在所述N个传输数据均未满足所述第一条件的情况下，执行所述第二接入过程。
  20. 根据权利要求18所述的装置，其中，所述处理模块具体用于：在所述N个传输数据均满足所述第一条件的情况下，执行所述第一接入过程；或，在所述N个传输数据中至少一个传输数据未满足所述第一条件的情况下，执行所述第二接入过程。
  21. 根据权利要求18所述的装置，其中，所述第二承载信息包括以下至少一项：承载标识和承载类型。
  22. 根据权利要求21所述的装置，其中，所述承载类型包括以下至少一项：主小区组MCG数据无线承载DRB、辅小区组SCG DRB、MCG分离DRB和SCG分离DRB。
  23. 根据权利要求21所述的装置，其中，所述承载标识包括以下至少一项：DRB标识、服务质量流标识、协议数据单元会话标识和小区组标识。
  24. 根据权利要求18所述的装置，其中，所述第二传输方式包括以下至少一项：数据发送方式和数据接收方式。
  25. 根据权利要求24所述的装置，其中，所述数据发送方式包括以下至少一项：
    终端在4步随机接入过程中的Msg3中发送数据；
    终端在2步随机接入过程中的MsgA中发送数据；
    终端在配置的专属上行资源中发送数据；
    网络设备在4步随机接入过程中的Msg4中发送数据；
    网络设备在2步随机接入过程中的MsgB中发送数据；
    网络设备在配置的专属上行资源对应的下行资源中发送数据。
  26. 根据权利要求24所述的装置，其中，所述数据接收方式包括以下至少一项：
    网络设备在4步随机接入过程中的Msg3中接收数据；
    网络设备在2步随机接入过程中的MsgB中接收数据；
    网络设备在配置的专属上行资源中接收数据；
    终端在4步随机接入过程中的Msg4中接收数据；
    终端在2步随机接入过程中的MsgB中接收数据；
    终端在配置的专属上行资源对应的下行资源中接收数据。
  27. 根据权利要求18所述的装置，其中，所述M个传输数据包括以下至少一项：
    DRB的数据；
    服务质量流的数据
    PDU会话的数据；
    承载在信令无线承载SRB中的用户面数据。
  28. 一种通信设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序，所述程序被所述处理器执行时实现如权利要求1至17中任一项所述的接入过程处理方法中的步骤。
  29. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至17中任一项所述的接入过程处理方法的步骤。
  30. 一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络设备程序或指令，实现如权利要求1至17中任一项所述的接入过程处理方法。
  31. 一种计算机软件产品，所述计算机软件产品被存储在非易失的存储介 质中，所述软件产品被配置成被至少一个处理器执行以实现如权利要求1至17中任一项所述的接入过程处理方法的步骤。
  32. 一种通信设备，所述通信设备被配置成用于执行如权利要求1至17中任一项所述的接入过程处理方法。
PCT/CN2021/099324 2020-06-11 2021-06-10 接入过程处理方法、装置及通信设备 WO2021249467A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/074,439 US20230109276A1 (en) 2020-06-11 2022-12-02 Access procedure processing method, apparatus and communications device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010531606.3A CN113811015A (zh) 2020-06-11 2020-06-11 接入过程处理方法、装置及通信设备
CN202010531606.3 2020-06-11

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/074,439 Continuation US20230109276A1 (en) 2020-06-11 2022-12-02 Access procedure processing method, apparatus and communications device

Publications (1)

Publication Number Publication Date
WO2021249467A1 true WO2021249467A1 (zh) 2021-12-16

Family

ID=78845370

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/099324 WO2021249467A1 (zh) 2020-06-11 2021-06-10 接入过程处理方法、装置及通信设备

Country Status (3)

Country Link
US (1) US20230109276A1 (zh)
CN (1) CN113811015A (zh)
WO (1) WO2021249467A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110234112B (zh) * 2018-03-05 2020-12-04 华为技术有限公司 消息处理方法、系统及用户面功能设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108271125A (zh) * 2017-01-04 2018-07-10 中兴通讯股份有限公司 数据发送、数据接收方法及装置
CN109756994A (zh) * 2017-08-25 2019-05-14 电信科学技术研究院 一种终端状态的恢复方法、装置、基站及终端
WO2020088097A1 (en) * 2018-10-30 2020-05-07 Qualcomm Incorporated Configurations for small data transmission

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014047825A1 (zh) * 2012-09-27 2014-04-03 华为技术有限公司 一种寻呼的控制方法、装置、实体及网络设备
CN105264960B (zh) * 2013-09-26 2019-10-01 华为技术有限公司 能力匹配方法、装置及系统
CN107371264B (zh) * 2016-05-12 2019-08-16 电信科学技术研究院 一种上行数据传输的方法及设备
CN107635271B (zh) * 2016-07-18 2020-01-07 电信科学技术研究院 一种传输数据的方法和设备
US11051333B2 (en) * 2017-08-28 2021-06-29 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data transmission method, network device, and terminal device
CN109587704B (zh) * 2017-09-28 2021-05-28 维沃移动通信有限公司 信息传输方法、终端、网络设备及计算机可读存储介质
CN110139365B (zh) * 2018-02-08 2022-08-26 展讯通信（上海）有限公司 在非激活状态下传输数据的方法、装置及用户设备
CN110839301B (zh) * 2018-08-16 2021-09-10 维沃移动通信有限公司 一种无线链路失败的信息处理方法、终端及网络设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108271125A (zh) * 2017-01-04 2018-07-10 中兴通讯股份有限公司 数据发送、数据接收方法及装置
CN109756994A (zh) * 2017-08-25 2019-05-14 电信科学技术研究院 一种终端状态的恢复方法、装置、基站及终端
WO2020088097A1 (en) * 2018-10-30 2020-05-07 Qualcomm Incorporated Configurations for small data transmission

Also Published As

Publication number Publication date
CN113811015A (zh) 2021-12-17
US20230109276A1 (en) 2023-04-06

Similar Documents

Publication Publication Date Title
CN108156670B (zh) 处理通信的装置及方法
TWI709348B (zh) 處理暫時用戶端能力的裝置及方法
EP4007198A1 (en) Carrier aggregation parameter configuration method, device and system
US20230247553A1 (en) DRX Determining Method and Apparatus, Terminal, and Readable Storage Medium
EP4239928A1 (en) Method for configuring, activating or deactivating pdcp duplication and terminal
WO2021239021A1 (zh) 配置信息获取方法、装置、用户设备及系统
WO2022148478A1 (zh) 配置方法、装置、设备及可读存储介质
WO2022068874A1 (zh) 报告的处理方法及装置、终端及网络侧设备
WO2022028473A1 (zh) 数据传输类型的设定方法和终端
EP4171116A1 (en) Cell group processing method and apparatus, and communication device
US20240073650A1 (en) Data Transmission Method and Related Device
US20230189352A1 (en) Service Collision Handling Method and Apparatus, and Terminal
CN114698151A (zh) 定位数据发送方法、接收方法、终端及网络侧设备
WO2022078314A1 (zh) 非激活态配置方法、装置及通信设备
WO2021244572A1 (zh) Mcg挂起方法、装置、用户设备及网络设备
WO2021249467A1 (zh) 接入过程处理方法、装置及通信设备
WO2022199482A1 (zh) 上行传输的控制方法、装置及终端
TWI839709B (zh) 用以處理非小資料傳輸(non-sdt)資料之方法、裝置及媒體
WO2021249296A1 (zh) 数据的传输方法及装置、终端及网络侧设备
WO2022206959A1 (zh) 主辅小区配置方法、装置、ue、网络侧设备及可读存储介质
EP4216624A1 (en) Paging message receiving method, paging configuration method, terminal and network-side device
WO2022028603A1 (zh) 数据传输方法、装置及电子设备
US20220022275A1 (en) Communication method and apparatus
US20200252842A1 (en) Managing cell group configuration in disaggregated base station architecture
WO2023066129A1 (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: 21821081

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 02/05/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 21821081

Country of ref document: EP

Kind code of ref document: A1