CN117729652A

CN117729652A - Communication method, apparatus, and storage medium

Info

Publication number: CN117729652A
Application number: CN202410172846.7A
Authority: CN
Inventors: 张明珠
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2024-02-07
Filing date: 2024-02-07
Publication date: 2024-03-19

Abstract

The embodiment of the application provides a communication method, equipment and a storage medium, which relate to the technical field of communication, and the method comprises the following steps: receiving a paging message from a network device; the paging message is used for indicating that the network equipment has the mobile termination small data packet transmission MT-SDT requirement; and sending a Radio Resource Control (RRC) recovery request message to the network equipment, wherein the RRC recovery request message is used for access attempt, and the RRC recovery request message carries a recovery reason which is related to small data packet transmission. The recovery reason is introduced to indicate the RRC recovery triggered by the small data packet transmission paging, so that the network equipment knows that the RRC recovery process is triggered by the small data packet transmission according to the recovery reason, and the scheduling efficiency of the network equipment according to the recovery reason is improved.

Description

Communication method, apparatus, and storage medium

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a communications method, apparatus, and storage medium.

Background

When the network device has the transmission requirement of the downlink small data packet, the paging message can be sent to the terminal device in the radio resource control (radio resource control, RRC) inactive state, and when the terminal device receives the paging message, the terminal device can send an RRC recovery request message to the network device so as to perform access attempt, thereby realizing the reception of the downlink small data packet.

The RRC recovery request message may carry a recovery reason of the terminal device for performing the access attempt, so as to improve resource scheduling efficiency of the network device. However, currently, there is no discussion on the recovery reason in the RRC recovery request message triggered by the downlink small packet transfer requirement.

Disclosure of Invention

The embodiment of the application provides a communication method, equipment and a storage medium, which are applied to the technical field of communication. The recovery reasons in the RRC recovery request message triggered by the downlink small packet transfer requirements are illustrated and discussed.

In a first aspect, an embodiment of the present application proposes a communication method. The method comprises the following steps: receiving a paging message from a network device; the paging message is used for indicating that the network equipment has the mobile termination small data packet transmission MT-SDT requirement;

and sending a Radio Resource Control (RRC) recovery request message to the network equipment, wherein the RRC recovery request message is used for access attempt, and the RRC recovery request message carries a recovery reason which is related to small data packet transmission.

In an optional embodiment of the first aspect, the recovery reason includes:

a first reason for indicating that the access attempt is an MT-SDT access attempt.

In an optional embodiment of the first aspect, the recovery reason includes:

a second reason or a third reason; the second reason is used for indicating that the access attempt is an MT-SDT access attempt and uplink data exists; the third cause is to indicate that the access attempt is an MT-SDT access attempt and that no upstream data is present.

In an optional embodiment of the first aspect, the terminal device has uplink data, where the uplink data includes SDT uplink data and non-SDT uplink data, and the recovery reason includes any one of the following:

fourth, fifth, sixth; the fourth reason is used for indicating that the access attempt is an MT-SDT access attempt, and SDT uplink data exists; the fifth cause is to indicate that the access attempt is an MT-SDT access attempt, and that there is non-SDT uplink data; the sixth cause is to indicate that the access attempt is an MT-SDT access attempt and that no uplink data is present.

In an optional embodiment of the first aspect, the terminal device has uplink data, the uplink data includes uplink service data, and the recovery reason includes:

seventh or eighth reason; the seventh cause is used to indicate that the access attempt is an MT-SDT access attempt and there is upstream traffic data, and the eighth cause is used to indicate that the access attempt is an MT-SDT access attempt and there is no upstream traffic data.

In an optional embodiment of the first aspect, the terminal device has uplink data, the uplink data includes uplink signaling, and the recovery reason includes:

a ninth cause or a tenth cause; the ninth cause is for indicating that the access attempt is an MT-SDT access attempt and there is uplink signaling, and the tenth cause is for indicating that the access attempt is an MT-SDT access attempt and there is no uplink signaling.

In an optional embodiment of the first aspect, the terminal device has uplink data, the uplink data includes uplink signaling and/or uplink service data, and the recovery reason includes any one of the following:

seventh cause, eighth cause, ninth cause, tenth cause; the seventh reason is used for indicating that the access attempt is an MT-SDT access attempt and uplink service data exists, and the eighth reason is used for indicating that the access attempt is an MT-SDT access attempt and no uplink service data exists; the ninth cause is for indicating that the access attempt is an MT-SDT access attempt and there is uplink signaling, and the tenth cause is for indicating that the access attempt is an MT-SDT access attempt and there is no uplink signaling.

In an alternative embodiment of the first aspect, the method further comprises:

And determining the recovery reason according to the access category corresponding to the access attempt and/or the corresponding access identifier of the access attempt and the mapping relation between the access category and/or the access identifier and the recovery reason.

In an alternative embodiment of the first aspect, the method further comprises:

determining the access category according to the access attempt and the mapping relation between the access attempt and the access category; one of the access categories in the mapping corresponds to one or more access attempts.

In an optional embodiment of the first aspect, the access category and/or the access identity, and information about the access category and/or the access identity is defined based on the restoration reason; the information about the access category and/or the access identity includes at least one of access attempt type, requirements that the access attempt needs to meet, RRC establishment cause.

In an optional embodiment of the first aspect, the access category and the access identity are defined based on the restoration reason.

In an optional embodiment of the first aspect, the access attempt type and the requirements that the access attempt needs to meet are defined based on the access category, and the RRC establishment cause is defined based on the access category and/or the access identity.

In an optional embodiment of the first aspect, the access identity is defined based on the restoration reason.

In an optional embodiment of the first aspect, the RRC establishment cause is defined based on the access identity.

In a second aspect, embodiments of the present application provide a communication method. The method comprises the following steps: sending a paging message to a terminal device; the paging message is used for indicating that the network equipment has the mobile termination small data packet transmission MT-SDT requirement;

and receiving a Radio Resource Control (RRC) recovery request message from the terminal equipment, wherein the RRC recovery request message is used for access attempt, and the RRC recovery request message carries a recovery reason which is related to small data packet transmission.

In an alternative embodiment of the second aspect, the recovery reason includes:

In an optional embodiment of the second aspect, the terminal device has uplink data, where the uplink data includes SDT uplink data and non-SDT uplink data, and the recovery reason includes any one of the following:

In an optional embodiment of the second aspect, the terminal device has uplink data, the uplink data includes uplink service data, and the recovery reason includes:

In an optional embodiment of the second aspect, the terminal device has uplink data, the uplink data includes uplink signaling, and the recovery reason includes:

In an optional embodiment of the second aspect, the terminal device has uplink data, the uplink data includes uplink signaling and/or uplink service data, and the recovery reason includes any one of the following:

In an optional embodiment of the second aspect, the restoration reason is determined according to an access category corresponding to the access attempt and/or a corresponding access identifier of the access attempt, and a mapping relationship between the access category and/or the access identifier and the restoration reason.

In an optional embodiment of the second aspect, the access category is determined according to the access attempt, and a mapping relationship between the access attempt and the access category; one of the access categories in the mapping corresponds to one or more access attempts.

In an optional embodiment of the second aspect, the access category and/or the access identity, and the information about the access category and/or the access identity is defined based on the restoration reason; the information about the access category and/or the access identity includes at least one of access attempt type, requirements that the access attempt needs to meet, RRC establishment cause.

In an alternative embodiment of the second aspect, the access category and the access identity are defined based on the restoration reason.

In an alternative embodiment of the second aspect, the access attempt type and the requirements that the access attempt needs to meet are defined based on the access category, and the RRC establishment cause is defined based on the access category and/or the access identity.

In an alternative embodiment of the second aspect, the access identity is defined based on the recovery reason, and the RRC establishment cause is defined based on the access identity.

In a third aspect, an embodiment of the present application provides a communication apparatus, including:

a receiving module, configured to receive a paging message from a network device; the paging message is used for indicating that the network equipment has the mobile termination small data packet transmission MT-SDT requirement;

and the sending module is used for sending a Radio Resource Control (RRC) recovery request message to the network equipment, wherein the RRC recovery request message is used for access attempt, and the RRC recovery request message carries a recovery reason which is related to small data packet transmission.

In a fourth aspect, embodiments of the present application provide a communication device, including:

a sending module, configured to send a paging message to a terminal device; the paging message is used for indicating that the network equipment has the mobile termination small data packet transmission MT-SDT requirement;

and the receiving module is used for receiving a Radio Resource Control (RRC) recovery request message from the terminal equipment, wherein the RRC recovery request message is used for access attempt, and the RRC recovery request message carries a recovery reason which is related to small data packet transmission.

In a fifth aspect, embodiments of the present application provide a communication device, including: comprising the following steps: a processor and a memory; the memory stores computer-executable instructions; the processor executes computer-executable instructions stored in the memory to cause the terminal device to perform a method as in the first aspect.

In a sixth aspect, embodiments of the present application provide a communication device, including: comprising the following steps: a processor and a memory; the memory stores computer-executable instructions; the processor executes computer-executable instructions stored in the memory to cause the terminal device to perform a method as in the second aspect.

In a seventh aspect, embodiments of the present application provide a computer-readable storage medium storing a computer program. The computer program, when executed by a processor, implements a method as in the first or second aspect.

In an eighth aspect, embodiments of the present application provide a computer program product comprising a computer program which, when run, causes a computer to perform the method as in the first or second aspect.

In a ninth aspect, embodiments of the present application provide a chip comprising a processor for invoking a computer program in a memory to perform a method according to the first or second aspect.

It should be understood that, the third aspect to the ninth aspect of the present application correspond to the technical solutions of the first aspect of the present application, and the beneficial effects obtained by each aspect and the corresponding possible embodiments are similar, and are not repeated.

The embodiment of the application provides a communication method, equipment and a storage medium, wherein the method comprises the following steps: receiving a paging message from a network device; the paging message is used for indicating that the network equipment has the mobile termination small data packet transmission MT-SDT requirement; and sending a Radio Resource Control (RRC) recovery request message to the network equipment, wherein the RRC recovery request message is used for access attempt, and the RRC recovery request message carries a recovery reason which is related to small data packet transmission. The recovery reason is introduced to indicate the RRC recovery triggered by MT-SD paging, so that the network equipment knows that the RRC recovery process is triggered by MT-SDT according to the recovery reason, and the scheduling efficiency of the network equipment according to the recovery reason is improved.

Drawings

Fig. 1 is a schematic view of a scenario provided in an embodiment of the present application;

fig. 2 is a schematic flow chart of a communication method according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 5 is a schematic hardware structure of a communication device according to an embodiment of the present application.

Detailed Description

For purposes of clarity in describing the embodiments of the present application, in the embodiments of the present application, words such as "exemplary" or "such as" are used to indicate by way of example, illustration, or description. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.

The term "at … …" in the embodiment of the present application may be instantaneous when a certain situation occurs, or may be a period of time after a certain situation occurs, which is not particularly limited in the embodiment of the present application.

For ease of understanding, some of the terms in the embodiments of the present application are described below.

1. RRC state:

In the fifth generation mobile communication technology (5th Generation Mobile Communication Technology,5G) network, there are three RRC states for the terminal device, RRC connected, RRC idle and RRC inactive. The three RRC states may be transited to each other, and the transition between the three RRC states may also be referred to as "state switching" or "state transition".

The RRC connected state, simply referred to as connected state. When the terminal equipment is in a connection state, the terminal equipment and the network establish RRC connection, and data transmission can be performed.

The RRC idle state is referred to as idle state for short. When the terminal device is in an idle state, the terminal device does not establish an RRC connection with the network device, and the network device does not store a context (context) of the terminal device. If the terminal device needs to enter the RRC connected state from the RRC idle state, an RRC connection establishment procedure needs to be initiated.

An RRC Inactive (Inactive) state, simply referred to as an Inactive state. The network device may release the terminal device from the connected state to the inactive state. If the terminal device is to re-enter the RRC connected state from the RRC inactive state, an RRC connection recovery procedure needs to be initiated. This procedure may also be referred to as RRC connection reestablishment procedure.

2. Small data packet transmission (small data transmission SDT)

In the embodiment of the present application, a data packet whose data size is smaller than a preset data size threshold may be referred to as a small data packet. In a conventional communication network, a terminal device in an idle state or an inactive state needs to perform transmission of multiple control signaling with a network device to enter a connection state, and then perform data or signaling transmission with the network device. In a communication network such as machine type communication (machine type communication, MTC), the terminal device may frequently send some small data packets to the network device, which may cause the terminal device in an idle state or in an inactive state to need to be frequently switched to a connected state, resulting in a large amount of signaling being turned on, which increases power consumption of the network device.

For this situation, there has been a method in which a terminal device can send small data packets to a network device through some control signaling in an inactive state, and this transmission mode is called a small data packet transmission (small data transmission, SDT) mode.

3. Mobile termination (mobile terminated MT)

Mobile termination, also known as mobile called, involves mobile messages routed from a core network device (e.g., an access management function network element) or network device and sent to a terminal device. Mobile termination also refers to terminating a voice call from another mobile subscriber, public switched telephone network (public switch telephone network, PSTN) or other network to the terminal device.

The term "terminate" means that the message terminates the delivery at the terminal device. The term also describes the communication between the short message service center (short message service center, smsc) and the terminal equipment, and between the mobile switching center (mobile switching center, MSC) and the terminal equipment.

4. Mobile terminated Small data packet transfer (mobile terminated-small data transmission, MT-SDT)

MT-SDT refers to a manner of small packet transmission terminated at a terminal device, also called mobile small packet transmission. When the terminal device receives downlink data and/or signaling from the network device through the MT-SDT manner, signaling overhead and UE power consumption can be reduced by not switching to the RRC connected state, and delay is not reduced by allowing a fast transmission of small data packets (e.g., small data packets for positioning).

Corresponding to MT-SDT is a mobile originated small packet transfer (mobile originating-small datatransmission, MO-SDT), also known as a mobile originated small packet transfer. MO-SDT refers to the manner in which small packets are transmitted as initiated by a terminal device. When the terminal equipment sends uplink data and/or signaling to the network equipment in an MO-SDT mode, the transmission of the small data packet can be carried out in an RRC inactive state, so that signaling overhead and UE power consumption are reduced.

5. Paging based on radio access network (radio access network-based Paging, RAN-based Paging)

Paging based on a radio access network refers to a network device initiating Paging (Paging) within the coverage area of the radio access network to determine the cell in which the terminal device is located. When the network device receives downlink data/signaling from the core network, a radio access network Paging (RAN Paging) message is triggered. Wherein RAN-based Paging, RAN Paging, paging are the same concept, which is not differentiated in the embodiments of the present application.

The technical scheme provided by the embodiment of the application can be suitable for various communication systems. For example, suitable systems may be long term evolution (long term evolution, LTE) systems, LTE frequency division duplex (frequency division duplex, FDD) systems, LTE time division duplex (time division duplex, TDD) systems, long term evolution-advanced (long term evolution advanced, LTE-a) systems, universal mobile systems (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) systems, 5G New Radio, NR systems, evolution communication systems thereof, and the like, e.g., sixth generation (6th generation,6G) communication systems. Terminal devices and network devices may be included in the various systems. Core network parts such as evolved packet system (evolved packet system, EPS), 5G system (5 GS) etc. may also be included in the system.

The terminal device according to the embodiments of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing device connected to a wireless modem, etc. The names of the terminal devices may also be different in different systems, for example in a 5G system, the terminal devices may be referred to as User Equipment (UE). The terminal devices may be USB storage devices, other personal computer memory devices and dongles, and may also communicate with one or more Core Networks (CNs) via radio access networks (Radio Access Network, RANs), and the terminal devices may be mobile terminal devices such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket, hand-held, computer-built-in or vehicle-mounted mobile devices that exchange voice and/or data with the radio access networks. For example, personal communication services (personal communication service, PCS) phones, cordless phones, session initiation protocol (session initiated protocol, SIP) phones, wireless local loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistant, PDA), personal computers, tablet computers, machine-type communication (MTC) terminal devices, augmented reality (augmented reality, AR)/Virtual Reality (VR) devices, wearable devices, vehicle-mounted devices (VUE) and the like. The terminal devices may also be referred to as systems, subscriber units (subscriber units), subscriber stations (subscriber station), mobile stations (mobile stations), remote stations (remote stations), access points (access points), remote terminal devices (remote terminals), access terminal devices (access terminals), user terminal devices (user terminals), user agents (user agents), user equipment (user devices), wireless access points and routers/modems satisfying the limitations of the present definition, and the like, and are not limited in this embodiment.

The network device according to the embodiments of the present application may be referred to as an access network device, a radio access network (radio access network, RAN), a radio access network function, or a radio access network unit, where the access network device may include a base station, a WLAN access point, or the like, and the base station may include one or more cells that provide services for terminal devices. A base station may also be called an access point or may be a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or other names, depending on the particular application. For example, the network device according to the embodiments of the present application may be an evolved network device (evolutional Node B, eNB or e-NodeB) in a long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in a 5G network architecture (next generation system), or the like, or may be a home evolved base station (home evolved Node B, heNB), a relay node (relay node), a home base station (femto), a pico base station (pico), a network test device, or some other suitable term in the field, so long as the same technical effect is achieved, and the base station is not limited to a specific technical vocabulary. In some network structures, the network device may include a Centralized Unit (CU) node and a Distributed Unit (DU) node, which may also be geographically separated.

Alternatively, the network device and the terminal device in the embodiments of the present application may also be referred to as a communication apparatus or a communication device, which may be a general-purpose device or a special-purpose device, which is not specifically limited in the embodiments of the present application.

The protocol is predefined with an access identification table, an access category table and an RRC establishment cause table. The following describes the tables respectively:

1. the access identifier table includes a mapping relationship between the configuration of the terminal device and the access identifier number, as shown in the following table 1:

TABLE 1

2. The access category table includes a mapping relationship between an access category, an access attempt type, and a requirement that the access attempt needs to satisfy (simply: a requirement that needs to satisfy) (where the access attempt type and the requirement that the access attempt needs to satisfy may be referred to as related information of the access attempt), as shown in table 2 below:

TABLE 2

/>

3. The RRC establishment cause table includes a mapping relationship between an access category and an access identifier and a cause of RRC establishment, as shown in the following tables 3 and 4:

TABLE 3 Table 3

TABLE 4 Table 4

Note 1 and note 2 in table 3 apply only to table 3, note 1, note 2 and note 3 in table 4 apply only to table 4, and UEs in the above tables may also be referred to as terminal devices.

The RRC establishment cause may include: RRC reestablishment cause, RRC resume setup cause, and RRC setup cause.

It should be understood that MO and MO represent the same concept, MT and MT represent the same concept, MT-SDT, mtstt and MTSDT represent the same concept, X and X, Y and Y represent the same concept in the embodiments of the present application, which are not differentiated.

As shown in fig. 1, when there is a transmission requirement of a downlink data packet in the network device, a paging message may be sent to the terminal device, and when the terminal device receives the paging message, an RRC restoration request message (RRC Resume Request) may be sent to the network device to reply, where the RRC restoration request message may carry a restoration reason, and the network device may schedule according to the received restoration reason.

When determining the restoration reason, the terminal device may determine the restoration reason based on the access identifier table, the access category table, and the RRC establishment cause table predefined in the above protocol. For example, when the terminal device receives the paging message, the paging message indicates that the network device needs to send downlink data, and the Access attempt type of the terminal device is a reply paging message, the Access type is determined to be 0 according to the Access attempt type query Access type table, the RRC establishment cause table is queried according to the Access type, the value set to the RRC establishment cause is determined to be mt-Access, and the terminal device may set the restoration cause to be mt-Access. The access class may also be referred to as an access class value, an access class number, etc., which is not differentiated in the embodiment of the present application.

When the paging message of the network device received by the terminal device is MT-SDT paging, according to the content in the table, it can be known that the relevant content of the Access identifier, the Access category and the value of the cause of RRC establishment related to MT-SDT paging is lacking, when the paging message of the network device received by the terminal device is MT-SDT paging, the terminal device can set the recovery cause to MT-Access according to the content in the table, and when the network device receives the RRC recovery request message, the network device cannot accurately acquire the cause of RRC recovery according to the recovery cause in the RRC recovery request message, which may make the scheduling efficiency of the network device according to the recovery cause not high.

In view of this, the embodiments of the present application provide a communication method, which introduces a new recovery reason for indicating RRC recovery triggered by MT-SD paging for a scenario in which a paging message of a network device is MT-SDT paging, so that the network device knows according to the recovery reason that the RRC recovery process at this time is triggered by MT-SDT, and improves efficiency of scheduling by the network device according to the recovery reason.

The communication method provided in the embodiment of the present application will be described below with reference to the accompanying drawings.

Fig. 2 is a flow chart of a communication method provided in an embodiment of the present application, as shown in fig. 2, including:

S201, the network equipment sends a paging message to the terminal equipment.

In the embodiment of the application, the paging message is used for indicating that the network equipment has the MT-SDT requirement for mobile termination small data packet transmission.

In some embodiments, the paging message includes first indication information, where the first indication information is used to indicate that the paging message is triggered when the network device has MT-SDT requirements, that is, the paging message is triggered when the network device has MT-SDT requirements, or the paging message is paging of MT-SDT.

The paging message may also include an identification of the terminal device so that the terminal device determines itself to be paged.

S202, the terminal equipment receives the paging message from the network equipment.

S203, the terminal equipment sends an RRC recovery request message to the network equipment.

When the terminal device receives the paging message, it can perform paging reply, and in the paging reply process, the terminal device can send an RRC recovery request (RRC Resume Request) message to the network device to perform an access attempt.

In some embodiments, the terminal device may reply with different reply types in the paging reply process, for example, the reply types may include random access SDT (RA-SDT), grant transmission SDT (CG-SDT), or normal RA (legacy RA).

For example, when the terminal device receives the paging message, the reply type may be determined according to whether there is uplink data currently being transmitted or whether there is uplink data to be transmitted. For example, if the terminal device determines that there is no uplink data being transmitted or required to be transmitted, a normal RA may be selected for reply. If the terminal device determines that there is uplink data being transmitted or required to be transmitted, the corresponding reply type can be determined according to whether there is an effective RA-SDT resource or CG-SDT resource currently, for example, when there is an effective RA-SDT resource, RA-SDT is used for reply, and when there is an effective CG-SDT resource, CG-SDT is used for reply.

In some embodiments, the presence of a valid CG-SDT resource may be determined according to at least one of the following conditions:

1. the cell receiving the paging message is a cell configured with CG-SDT resources.

2. CG-SDT resources are configured on the selected carrier.

3. The measurement of the reference signal received power (reference signal receiving power, RSRP) meets a first RSRP threshold.

Wherein the first RSRP threshold is predefined in the protocol standard or configured by the network device.

4. The SSB receiving the paging message configures CG-SDT resources.

In some embodiments, the presence of valid RA-SDT resources may be determined according to any of the following conditions:

1. the cell receiving the paging message is a cell configured with RA-SDT resources or in the case where no CG-SDT resources are determined.

2. RA-SDT resources are configured on the selected carrier.

In the embodiment of the present application, the RRC recovery request message is used for the access attempt, and the RRC recovery request message carries a recovery reason, and since the recovery reason is used for indicating the access attempt triggered by MT-SDT paging (i.e., the recovery reason is related to small packet transmission), the introduced recovery reason may include the following several possible implementation manners:

first category: the first cause is introduced for indicating that the access attempt is an MT-SDT access attempt.

The second category: introducing a second reason and a third reason; the second reason is to indicate that the access attempt is an MT-SDT access attempt, and that there is uplink data (UL data or UL data); the third cause is to indicate that the access attempt is an MT-SDT access attempt and that there is no upstream data. Because the terminal equipment can also have uplink data or uplink data when replying the paging message, the actual situation of the terminal equipment can be indicated more accurately through the second-class recovery reasons.

Third category: fourth, fifth, sixth; a fourth reason is to indicate that the access attempt is an MT-SDT access attempt and that SDT uplink data is present; a fifth cause is to indicate that the access attempt is an MT-SDT access attempt and that there is non-SDT uplink data; the sixth reason is to indicate that the access attempt is an MT-SDT access attempt and that there is no upstream data. Since the types of the uplink data may include SDT uplink data and non-SDT uplink data, the type of the uplink data may be more accurately indicated by the restoration reason of the third type.

Fourth category: introducing a seventh or eighth cause; the seventh reason is for indicating that the access attempt is an MT-SDT access attempt and there is upstream traffic data, and the eighth reason is for indicating that the access attempt is an MT-SDT access attempt and there is no upstream traffic data. Since the uplink data may include uplink service data (MO data, also referred to as uplink user data, or uplink user data packet), the content of the uplink data may be further accurately indicated by the fourth type of recovery reason.

Fifth category: introducing a ninth or tenth cause; the ninth cause is used to indicate that the access attempt is an MT-SDT access attempt and there is uplink signaling, and the tenth cause is used to indicate that the access attempt is an MT-SDT access attempt and there is no uplink signaling. Since the uplink data may include uplink signaling (MO sig), the content of the uplink data may be more accurately indicated by the fifth type of restoration reason.

Sixth category: introducing a seventh reason, an eighth reason, a ninth reason and a tenth reason; the seventh reason is used for indicating that the access attempt is MT-SDT access attempt and uplink service data exists, and the eighth reason is used for indicating that the access attempt is MT-SDT access attempt and no uplink service data exists; the ninth cause is used to indicate that the access attempt is an MT-SDT access attempt and there is uplink signaling, and the tenth cause is used to indicate that the access attempt is an MT-SDT access attempt and there is no uplink signaling. The content of the uplink data can be indicated more accurately and comprehensively through the sixth recovery reasons.

It should be understood that the above is merely exemplary and is not intended to limit the embodiments of the present application to provide some classification of restoration reasons. In the above classification, the presence and absence may also be expressed as presence and absence, and for example, the presence of uplink data may be referred to as absence of uplink data.

In the above description, the possible restoration reasons are described, and since the restoration reasons have a corresponding relationship with the access category and the access identifier, when a new restoration reason is introduced, the relevant contents of the access category and the access identifier need to be updated or set (for example, the access category table and the RRC establishment cause table are updated).

The following describes the relevant contents of the corresponding access category and access identifier when the recovery reasons of the different categories are introduced respectively.

In one possible implementation, a new access class and a new access identity may be introduced when introducing different classes of restoration reasons.

The following describes the relevant content of the corresponding access category and access identifier when different types of restoration reasons are introduced.

When the introduced recovery reasons are of the first type: a new access category, e.g., X, may be set for the corresponding first reason, and the access attempt type corresponding to the access category may be set to respond to paging of the MT-SDT, and the requirements to be met are set to be the access attempt of the MT-SDT access.

The following table (access category table) is specific:

when a new access class is set, a new access identifier (also called an access identifier number, an access identifier value) and an RRC establishment cause may also be set. For example, the Access flag may be set to m, and the value set by the RRC establishment cause is MT-SDT Access (mtsdt-Access).

The following table (RRC establishment cause table) is specific:

it should be understood that the above table may be a new table, or an original table may be supplemented, which is not limited in this embodiment of the present application.

When the introduced recovery reasons are the second type, the second type includes two reasons, two new access categories may be set, corresponding to different recovery reasons, for example X, Y, for corresponding to the second reason and the third reason. The access attempt type corresponding to the access category may be set to respond to the paging of the MT-SDT, and when the access category is X, the requirements to be satisfied include: an access attempt of MT-SDT access with MO signaling, an access attempt of MT-SDT access with MO data, and an access attempt of MT-SDT access with uplink data; when the access class is Y, the requirements to be satisfied include: there is no access attempt for MO signaling and MO data MT-SDT access, no access attempt for MT-SDT access for uplink data.

The following table (access category table) is specific:

when a new access class is set, a new access identifier and an RRC establishment cause may also be set. For example, the access identities may be set to m and p, and the values set by the RRC establishment cause include: MT-SDT Access with upstream data (mtstwithuldata-Access) and MT-SDT Access without upstream data (mtstwithuldata-Access).

The following table (RRC establishment cause table) is specific:

When the introduced restoration reasons are the third class, the third class includes three reasons, and then three new access categories may be set, corresponding to different restoration reasons, for example X, Y, Z, for corresponding to the fourth, fifth and sixth reasons. The access attempt type corresponding to the access category may be set to respond to the paging of the MT-SDT, and when the access category is X, the requirements to be satisfied include: an access attempt for MT-SDT access with SDT uplink data; when the access class is Y, the requirements to be satisfied include: an access attempt for MT-SDT access with non-SDT uplink data; when the access class is Z, the requirements to be satisfied include: no access attempt for MT-SDT access of uplink data.

The following table (access category table) is specific:

when a new access class is set, a new access identifier and an RRC establishment cause may also be set. For example, the access identifier may be set to m, p, w, and the values set by the RRC establishment cause include: MT-SDT Access with SDT upstream data (mtstdwith dtuta-Access), MT-SDT Access with non-SDT upstream data (mtstdwith non-stdtuta-Access), and MT-SDT Access without upstream data (mtststdwith dtuta-Access).

The following table (RRC establishment cause table) is specific:

when the introduced restoration reasons are the fourth class, which includes two reasons, two new access categories may be set, corresponding to different restoration reasons, for example, X, Y, for the seventh reason and the eighth reason, respectively. The access attempt type corresponding to the access category may be set to respond to the paging of the MT-SDT, and when the access category is X, the requirements to be satisfied include: an access attempt for MT-SDT access with uplink traffic data; when the access class is Y, the requirements to be satisfied include: there is no access attempt for MT-SDT access to uplink traffic data.

The following table (access category table) is specific:

when a new access class is set, a new access identifier and an RRC establishment cause may also be set. For example, the access identifier may be set to m, p, and the values set by the RRC establishment cause include: MT-SDT Access with uplink traffic data (mtstdwith mode-Access), MT-SDT Access without uplink traffic data (mtstdwith mode-Access).

The following table (RRC establishment cause table) is specific:

when the introduced restoration reasons are the fifth type, the fourth type includes two reasons, two new access categories may be set, corresponding to different restoration reasons, for example, X, Y, for the ninth and tenth reasons, respectively. The access attempt type corresponding to the access category may be set to respond to the paging of the MT-SDT, and when the access category is X, the requirements to be satisfied include: an access attempt for MT-SDT access with uplink signaling; when the access class is Y, the requirements to be satisfied include: access attempts for MT-SDT access without uplink signaling.

The following table (access category table) is specific:

when a new access class is set, a new access identifier and an RRC establishment cause may also be set. For example, the access identifier may be set to m, p, and the values set by the RRC establishment cause include: MT-SDT Access with uplink signaling (mtsdt with mo signalling (sig) -Access), MT-SDT Access without uplink signaling (mtsdt without mo signalling (sig) -Access).

The following table (RRC establishment cause table) is specific:

when the introduced restoration reasons are the sixth type, the fourth type includes four reasons, four new access categories may be set, corresponding to different restoration reasons, for example, X, Y, Z, W, for the seventh, eighth, ninth and tenth reasons, respectively. The access attempt type corresponding to the access category may be set to respond to the paging of the MT-SDT, and when the access category is X, the requirements to be satisfied include: an access attempt for MT-SDT access with uplink traffic data; when the access class is Y, the requirements to be satisfied include: there is no access attempt for MT-SDT access to uplink traffic data. When the access class is Z, the requirements to be satisfied include: an access attempt for MT-SDT access with uplink signaling; when the access class is W, the requirements to be satisfied include: access attempts for MT-SDT access without uplink signaling.

The following table (access category table) is specific:

when a new access class is set, a new access identifier and an RRC establishment cause may also be set. For example, the access identifier may be set to m, p, v, t, and the values set by the RRC establishment cause include: MT-SDT Access with uplink traffic data (mtstdwith mode-Access), MT-SDT Access without uplink traffic data (mtstdwith mode-Access), MT-SDT Access with uplink signaling (mtstdwith mode-Access), MT-SDT Access without uplink signaling (mtsdtwithoutmo ig-Access).

The following table (RRC establishment cause table) is specific:

in one possible implementation manner, when different types of restoration reasons are introduced, new access attempt types and information of requirements to be met by the new access attempts can be added in the information of the access attempt types and requirements to be met by the access attempts corresponding to the access category 0 (=mt-access) in the original access category table, and new access identifiers are set.

The following describes adding new information and setting new access identifier, corresponding access category and related content of access identifier.

When the introduced recovery reasons are of the first type: the access attempt type corresponding to the increased access category may be set to respond to paging of MT-SDT, and the requirement to be satisfied is set to an access attempt of MT-SDT access.

The following table (access category table) is specific:

the new access attempt type and the requirement to be met are underlined to identify part of the content, it should be understood that the underlined is only used for distinguishing the new content from the existing content, and has no practical meaning, the new content of the subsequent access category table is shown by the underlined, and the existing content can refer to the content in the above table 2.

When the newly added information is set, a new access identifier and an RRC establishment cause may also be set. For example, the Access flag may be set to m and the RRC establishment cause is set to a value of MT-SDT Access (mtsdt-Access).

The following table (RRC establishment cause table) is specific:

when the introduced recovery reasons are the second category, the second category includes two reasons, and the access attempt type corresponding to the added access category can be set to respond to the paging of the MT-SDT, and the requirements to be satisfied include: an access attempt with MO signaling MT-SDT access, an access attempt with MO data MT-SDT access, an access attempt with UL data MT-SDT access; there is no access attempt for MO signaling and MO data MT-SDT access, no access attempt for MT-SDT access for uplink data.

The following table (access category table) is specific:

when the newly added information is set, a new access identifier and an RRC establishment cause may also be set. For example, the access identities may be set to m and p, and the values set by the RRC establishment cause include: MT-SDT Access with uplink data (mtsdt with ul data-Access) and MT-SDT Access without uplink data (mtsdt without ul data-Access).

The following table (RRC establishment cause table) is specific:

when the introduced recovery reason is the third type, the access attempt type corresponding to the added access type may be set to respond to the paging of MT-SDT, and the requirements to be satisfied include: an access attempt for MT-SDT access with SDT uplink data; an access attempt for MT-SDT access with non-SDT uplink data; no access attempt for MT-SDT access of uplink data.

The following table (access category table) is specific:

when the newly added information is set, a new access identifier and an RRC establishment cause may also be set. For example, the access identities may be set to m, p, w.

The values set to the RRC establishment cause include: MT-SDT Access with SDT upstream data (mtsdt with SDT ul data-Access), MT-SDT Access with non-SDT upstream data (mtsdt with non-SDT ul data-Access), and MT-SDT Access without upstream data (mtsdt without ul data-Access).

The following table (RRC establishment cause table) is specific:

when the introduced recovery reason is the fourth type, the access attempt type corresponding to the added access category may be set to respond to the paging of MT-SDT, and the requirements to be satisfied include: an access attempt for MT-SDT access with uplink traffic data; there is no access attempt for MT-SDT access to uplink traffic data.

The following table (access category table) is specific:

when the newly added information is set, a new access identifier and an RRC establishment cause may also be set. For example, the access identifier may be set to m, p, and the values set by the RRC establishment cause include: MT-SDT Access with uplink traffic data (mtsdt with mo data-Access), MT-SDT Access without uplink traffic data (mtsdt without mo data-Access).

The following table (RRC establishment cause table) is specific:

when the introduced recovery reason is the fifth type, the access attempt type corresponding to the added access category may be set to respond to the paging of MT-SDT, and the requirements to be satisfied include: an access attempt for MT-SDT access with uplink signaling; access attempts for MT-SDT access without uplink signaling.

The following table (access category table) is specific:

When the newly added information is set, a new access identifier and an RRC establishment cause may also be set. For example, the access identifier may be set to m, p, and the values set by the RRC establishment cause include: MT-SDT Access with uplink signaling (mtsdt with mo signalling (sig) -Access), MT-SDT Access without uplink signaling (mtsdt without mo signalling (sig) -Access).

The following table (RRC establishment cause table) is specific:

when the introduced recovery reason is the sixth type, the access attempt type corresponding to the added access category may be set to respond to the paging of MT-SDT, and the requirements to be satisfied include: an access attempt for MT-SDT access with uplink traffic data; an access attempt for MT-SDT access without uplink traffic data; an access attempt for MT-SDT access with uplink signaling; access attempts for MT-SDT access without uplink signaling.

The following table (access category table) is specific:

when the newly added information is set, a new access identifier and an RRC establishment cause may also be set. For example, the Access identifier may be set to m, p, v, t, and the value set by the RRC establishment cause includes MT-SDT Access with uplink traffic data (mtsdt with mo data-Access), MT-SDT Access without uplink traffic data (mtsdt without mo data-Access), MT-SDT Access with uplink signaling (mtsdt with mo sig-Access), MT-SDT Access without uplink signaling (mtsdt without mo sig-Access).

The following table (RRC establishment cause table) is specific:

it should be understood that the access class table and the RRC establishment cause table corresponding to the recovery causes of the different classes may be configured for the network device to the terminal device, or may be predefined in the protocol.

The description has been made above of the contents related to the access category and the access identifier corresponding to the introduction of the new restoration cause, and the description is made below of the procedure of determining the restoration cause based on the access identifier table and the RRC establishment cause table.

Taking the introduced recovery reasons as a second class as an example:

in one possible implementation manner, when the access class is a newly set access class, the terminal device may query an access class table corresponding to the second class when receiving the page of the MT-SDT of the network device, and determine the access class, for example, when the terminal device receives the page of the MT-SDT of the network device, the access attempt of the terminal device is used for responding to the page of the MT-SDT, the terminal device queries the access attempt type (Type of access attempt) in the access class table according to the access attempt, and may determine that the corresponding access classes are x and y, at this time, the terminal device may query the access class table for the requirement (Requirements to be met) to be satisfied based on whether there is uplink data currently, and determine which case, for example, if there is MO data currently existing in the terminal device, may determine the access attempt of the MT-SDT access belonging to MO data, thereby determining that the access class is x.

Optionally, the terminal device may also determine the access category by querying the access category table for the need to be satisfied and the access attempt type based on both the access attempt and the current presence or absence of uplink data.

When the terminal device determines that the Access class is x, the terminal device may query an RRC establishment cause table corresponding to the second class, and determine that the value set by the RRC establishment cause corresponding to the Access class is MT-SDT Access (mtstwithuldata-Access) without uplink data, then the terminal device may set the recovery cause carried in the RRC recovery request message to be MT-SDT Access (mtststwithuldata-Access) without uplink data.

In one possible implementation, when the access class is multiplexing the original access class, when the terminal device receives the paging of the MT-SDT of the network device, the access class may be determined by querying the access class table based on the access attempt and the current situation of whether there is uplink data, for example, the access attempt is used for responding to the paging of the MT-SDT, and the current MO data exists, and the access class is determined to be 0.

When the terminal device determines that the Access class is 0, the terminal device may query the RRC establishment cause table corresponding to the second class, and determine that the value set by the RRC establishment cause corresponding to the Access class 0 includes MT-SDT Access (mtstwithuldata-Access) with uplink data and MT-SDT Access (mtstdwith ldata-Access) without uplink data, and then the terminal device may set the restoration cause carried in the RRC restoration request message as mtstdwith data-Access or mtststdwith ldata-Access. The embodiment of the present application does not limit the manner in which the terminal device selects one RRC establishment cause from the values to which the multiple RRC establishment causes are set. For example, the terminal device may determine, through the currently corresponding requirement (Requirements to be met) to be met, that the RRC establishment cause is set to a value, e.g., the requirement (Requirements to be met) to be met is an Access attempt of MT-SDT Access with MO data, and then may set the recovery cause to be MT-SDT Access (mtstdwith data-Access) with uplink data.

It should be understood that, when the introduced restoration reason is other types, the manner of determining the restoration reason is similar to that described above, and will not be repeated here.

In some embodiments, the above access class table and RRC establishment cause table are defined in a Non-access stratum (NAS) layer of the terminal device, when the NAS layer of the terminal device determines, according to the access class table and the RRC establishment cause table, a value and an access identifier, to which the RRC establishment cause is set, the RRC layer of the terminal device may send the value or the access identifier, to which the RRC establishment cause is set, and the RRC layer of the terminal device sets a recovery cause according to the value or the access identifier, to which the establishment cause is configured by the NAS layer, to which the RRC establishment cause is set.

In one possible implementation, the NAS layer of the terminal device sends the value to which the RRC establishment cause is set to the RRC layer of the terminal device, and the RRC layer of the terminal device sets the recovery cause to the value to which the RRC establishment cause is set according to the configuration of the NAS layer. For example, when the RRC establishment cause transmitted by the NAS layer of the terminal device is set to an MT-SDT Access (mtstdwith outldata-Access) value of uplink service data, the RRC layer of the terminal device transmits the MT-SDT Access (mtstdwith outldata-Access) set to the uplink service data for the recovery cause to the network device.

In another possible implementation manner, the NAS layer of the terminal device sends the determined access identifier to the RRC layer, and the RRC layer of the terminal device may determine the recovery reason according to the access identifier and the mapping relationship table of the access identifier and the mapping recovery reason. The mapping relationship between the access identifier and the mapping restoration reason may be predefined in the RRC layer.

For example, the mapping relation including the access identity and the restoration reason may be predefined in the RRC layer in the form of a restoration reason table.

The following describes a recovery reason table corresponding to the recovery reasons introduced into different classes:

when the introduced restoration cause is of a first type, the Access identifier (Access identities) may be m, and the value of the restoration cause (Resume cause) is MT-SDT Access (mtsdt-Access).

The recovery cause table is as follows:

when the introduced recovery cause is of the second type, the Access identifier may include m and p, and the value of the recovery cause includes MT-SDT Access (mtstwithuldata-Access) with uplink data and MT-SDT Access (mtstwithuldata-Access) without uplink data. The recovery cause table is as follows:

when the introduced recovery cause is of the third type, the Access identifier may include m, p, and w, and the values of the recovery cause include MT-SDT Access (mtstdwistdtuta-Access) with SDT uplink data, MT-SDT Access (mtstdwistotuta-Access) with non-SDT uplink data, and MT-SDT Access (mtststdwistututa-Access) without uplink data.

The recovery cause table is as follows:

when the introduced recovery cause is the fourth type, the Access identifier may include m and p, and the value of the recovery cause includes MT-SDT Access (mtstwithamodata-Access) with uplink traffic data and MT-SDT Access (mtstwithattmacdata-Access) without uplink traffic data.

The recovery cause table is as follows:

when the introduced recovery cause is of the fifth type, the Access identifier may include m and p, and the value of the recovery cause includes MT-SDT Access (mtstwithenmosig-Access) with uplink signaling and MT-SDT Access (mtstdwith outmosig-Access) without uplink signaling.

The recovery cause table is as follows:

when the recovery cause is introduced as the sixth type, the Access identifier may include m, p, v, t, and the value of the recovery cause includes MT-SDT Access (mtstwithamodata-Access) with uplink traffic data, MT-SDT Access (mtstwithattmacdata-Access) without uplink traffic data, MT-SDT Access (mtstdwithmosig-Access) with uplink signaling, and MT-SDT Access (mtststdwithtosig-Access) without uplink signaling. The recovery cause table is as follows:

it should be understood that the mapping relation between the access identities and the recovery reasons may also be predefined in other forms in the RRC layer, e.g. functions. This is not limiting in this embodiment of the present application.

Taking the introduced recovery reasons as the second class, the mapping relation between the access identifier and the recovery reasons may be predefined in the RRC layer in the form of a recovery reason table as an example:

if the RRC layer of the terminal device receives the Access identifier m sent by the NAS layer of the terminal device, the RRC layer of the terminal device queries a recovery reason table, and determines that the recovery reason corresponding to the Access identifier m is MT-SDT Access (mtstwithuldata-Access) with uplink data, the terminal device may set the recovery reason carried in the RRC recovery request message to be MT-SDT Access (mtstwithuldata-Access) with uplink data, and send the same to the network device.

If the RRC layer of the terminal device receives the Access identifier p issued by the NAS layer of the terminal device, the RRC layer of the terminal device queries the recovery reason table, and determines that the recovery reason corresponding to the Access identifier p is MT-SDT Access (mtstdwith outldata-Access) without uplink data, then the terminal device may set the recovery reason carried in the RRC recovery request message to be MT-SDT Access (mtstdwith outldata-Access) without uplink data, and send the same to the network device.

It should be understood that when the RRC layer sets the recovery cause, the terminal device determines the recovery cause based on the NAS layer configuration, that is, the NAS layer configures the access identifier, and the RRC layer sets the recovery cause as the recovery cause corresponding to the access identifier. When the introduced recovery reasons are other types, the method for determining the recovery reasons according to the access identifier is similar to the above, and is not repeated here.

Optionally, when the RRC layer determines the restoration reason according to the access identifier configured by the NAS layer, there may be a case where the RRC layer cannot query the corresponding restoration reason according to the access identifier, and in this case, the RRC layer may set the restoration reason as a default reason. For example, when the NAS layer sends an Access identifier to the RRC layer, if it detects that the current network load is heavy, if a finer recovery cause is set, the NAS layer may issue another Access identifier (e.g., 0), and the RRC layer cannot query the corresponding recovery cause in the recovery cause table according to the Access identifier 0, in this case, the RRC layer may set the recovery cause as a default cause (e.g., MT Access).

The communication method of the embodiment of the present application has been described above, and the device for executing the communication method provided by the embodiment of the present application is described below. Those skilled in the art will appreciate that the methods and apparatus may be combined and referenced with each other, and that the related apparatus provided in the embodiments of the present application may perform the steps in the methods for ordering the list as described above.

Fig. 3 is a schematic structural diagram of a communication device 30 according to an embodiment of the present application, as shown in fig. 3, including:

A receiving module 301, configured to receive a paging message from a network device; the paging message is used to indicate to the network device that there is a mobile terminated small packet transfer MT-SDT requirement.

A sending module 302, configured to send a radio resource control RRC recovery request message to the network device, where the RRC recovery request message is used for an access attempt, and the RRC recovery request message carries a recovery reason, where the recovery reason is related to small data packet transmission.

In some embodiments, the restoration cause includes: a first reason for indicating that the access attempt is an MT-SDT access attempt.

In some embodiments, the restoration cause includes: a second reason or a third reason; the second reason is used for indicating that the access attempt is an MT-SDT access attempt and uplink data exists; the third cause is to indicate that the access attempt is an MT-SDT access attempt and that no upstream data is present.

In some embodiments, the terminal device has uplink data, the uplink data includes SDT uplink data and non-SDT uplink data, and the recovery reason includes any one of the following:

In some embodiments, the terminal device has uplink data, the uplink data includes uplink service data, and the recovery reason includes: seventh or eighth reason; the seventh cause is used to indicate that the access attempt is an MT-SDT access attempt and there is upstream traffic data, and the eighth cause is used to indicate that the access attempt is an MT-SDT access attempt and there is no upstream traffic data.

In some embodiments, the terminal device has uplink data, the uplink data includes uplink signaling, and the recovery reason includes: a ninth cause or a tenth cause; the ninth cause is for indicating that the access attempt is an MT-SDT access attempt and there is uplink signaling, and the tenth cause is for indicating that the access attempt is an MT-SDT access attempt and there is no uplink signaling.

In some embodiments, the terminal device has uplink data, the uplink data includes uplink signaling and/or uplink service data, and the recovery reason includes any one of the following:

In some embodiments, the communication device 30 further comprises: a processing module 303.

In some embodiments, the processing module 303 is configured to determine the restoration reason according to an access category corresponding to the access attempt and/or a corresponding access identifier of the access attempt, and a mapping relationship between the access category and/or the access identifier and the restoration reason.

In some embodiments, the processing module 303 is further configured to determine the access category according to the access attempt and a mapping relationship between the access attempt and the access category; one of the access categories in the mapping corresponds to one or more access attempts.

In some embodiments, the access category and/or the access identity, and the information about the access category and/or access identity is defined based on the restoration cause; the information about the access category and/or the access identity includes at least one of access attempt type, requirements that the access attempt needs to meet, RRC establishment cause.

In some embodiments, the access category and the access identity are defined based on the restoration reason.

In some embodiments, the access attempt type and the requirements that the access attempt needs to meet are defined based on the access category, and the RRC establishment cause is defined based on the access category and/or the access identity.

In some embodiments, the access identity is defined based on the restoration reason.

In some embodiments, the RRC establishment cause is defined based on the access identity.

The communication device provided in the embodiment of the present application may execute the technical scheme executed by the terminal device in the embodiment shown in fig. 2, and the principle and the technical effect of the communication device are similar, and are not repeated herein.

Fig. 4 is a schematic structural diagram of a communication device 40 according to an embodiment of the present application, as shown in fig. 4, including:

a sending module 401, configured to send a paging message to a terminal device; the paging message is used for indicating that the network equipment has the mobile termination small data packet transmission MT-SDT requirement;

a receiving module 402, configured to receive a radio resource control RRC recovery request message from a terminal device, where the RRC recovery request message is used for an access attempt, and the RRC recovery request message carries a recovery reason, where the recovery reason is related to small data packet transmission.

In some embodiments, the restoration reason is determined according to an access category corresponding to the access attempt and/or a corresponding access identification of the access attempt, and a mapping relationship between the access category and/or the access identification and the restoration reason.

In some embodiments, the access category is determined from the access attempt and a mapping of the access attempt to the access category; one of the access categories in the mapping corresponds to one or more access attempts.

In some embodiments, the access identity is defined based on the recovery reason, and the RRC establishment cause is defined based on the access identity.

The embodiment of the application also provides communication equipment.

Fig. 5 is a schematic structural diagram of a communication device according to an embodiment of the present application. As shown in fig. 5, the communication device 50 may include: at least one processor 501, memory 502, and transceiver 503. Wherein the processor 501, the transceiver 503 and the memory 502 are in communication with each other via an internal connection path, the memory 502 is configured to store instructions, and the processor 501 is configured to execute the instructions stored in the memory 502 to control the transceiver 503 to transmit channels/signals and/or receive channels/signals.

It should be understood that the communication device may correspond to the terminal device in the above-described method embodiment, or may correspond to the network device in the above-described method embodiment. And may be used to perform the various steps and/or flows performed by the terminal device, or network device, in the method embodiments shown above. Alternatively, the memory 502 may include read-only memory and random access memory, and provide instructions and data to the processor 501. A portion of memory 502 may also include non-volatile random access memory. The memory 502 may be a separate device or may be integrated in the processor 501. The processor 501 may be configured to execute instructions stored in the memory 502 and, when the processor 501 executes instructions stored in the memory, the processor 501 is configured to perform the steps and/or processes of the method embodiments described above.

The transceiver 503 may include a transmitter and a receiver, among others. The transceiver 503 may further include antennas, and the number of antennas may be one or more. The processor 501 and memory 502 and transceiver 503 may be devices integrated on different chips. For example, the processor 501 and the memory 502 may be integrated in a baseband chip and the transceiver 503 may be integrated in a radio frequency chip. The processor 501 and memory 502 may also be devices integrated on the same chip as the transceiver 503. The present application is not limited in this regard.

Alternatively, the communication device is a component, such as a chip, a chip system, or the like, configured in a terminal device, or a network device.

The transceiver 503 may also be a communication interface, such as an input/output interface, a circuit, etc. The transceiver 503 may be integrated in the same chip as the processor 501 and the memory 502, e.g. in a baseband chip.

The embodiment of the application further provides a computer readable storage medium, on which a computer program is stored, where the computer program when executed by a processor implements a technical scheme executed by a terminal device or a network device in the embodiment of the communication method, and implementation principles and technical effects are similar, and are not repeated herein.

In one possible implementation, the computer-readable storage medium may include random access Memory (Random Access Memory, RAM), read-Only Memory (ROM), compact disk (compact disc Read-Only Memory, CD-ROM) or other optical disk Memory, magnetic disk Memory or other magnetic storage device, or any other medium targeted for carrying or storing the desired program code in the form of instructions or data structures, and may be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (Digital Subscriber Line, DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes optical disc, laser disc, optical disc, digital versatile disc (Digital Versatile Disc, DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

The embodiment of the application further provides a computer program product, which comprises a computer program, when the computer program is executed by a processor, the technical scheme of the terminal device or the network device in the embodiment of the communication method is implemented, and the implementation principle and the technical effect are similar, and are not repeated here.

The embodiment of the application also provides a chip or a chip system, which comprises at least one processor and a communication interface, wherein the communication interface and the at least one processor are interconnected through a line, and the at least one processor is used for running a computer program or instructions to execute the technical scheme executed by the terminal equipment or the network equipment in the embodiment of the communication method. The implementation principle and technical effect are similar, and are not repeated here. The communication interface in the chip can be an input/output interface, a pin, a circuit or the like.

In one possible implementation, the chip or chip system described above in the present application further includes at least one memory, where the at least one memory stores instructions. The memory may be a memory unit within the chip, such as a register, a cache, etc., or may be a memory unit of the chip (e.g., a read-only memory, a random access memory, etc.).

In the specific implementation of the terminal device or the network device, it should be understood that the processor may be a central processing unit (in english: central Processing Unit, abbreviated as CPU), or may be other general purpose processors, digital signal processors (in english: digital Signal Processor, abbreviated as DSP), application specific integrated circuits (in english: application Specific Integrated Circuit, abbreviated as ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.

Those skilled in the art will appreciate that all or part of the steps of any of the method embodiments described above may be accomplished by hardware associated with program instructions. The foregoing program may be stored in a computer readable storage medium, which when executed, performs all or part of the steps of the method embodiments described above.

The technical solution of the present application, if implemented in the form of software and sold or used as a product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the technical solutions of the present application may be embodied in the form of a software product stored in a storage medium comprising a computer program or several instructions. The computer software product causes a computer device (which may be a personal computer, a server, a network device, or similar electronic device) to perform all or part of the steps of the methods described in embodiments of the present application.

It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of action combinations, but it should be understood by those skilled in the art that the present application is not limited by the order of actions described, as some steps may be performed in other order or simultaneously in accordance with the present application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all alternative embodiments, and that the acts and modules referred to are not necessarily required in the present application.

It should be further noted that, although the steps in the flowchart are sequentially shown as indicated by arrows, the steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps in the flowcharts may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order in which the sub-steps or stages are performed is not necessarily sequential, and may be performed in turn or alternately with at least a portion of the sub-steps or stages of other steps or other steps.

It should be understood that the above-described device embodiments are merely illustrative, and that the device of the present application may be implemented in other ways. For example, the division of the units/modules in the above embodiments is merely a logic function division, and there may be another division manner in actual implementation. For example, multiple units, modules, or components may be combined, or may be integrated into another system, or some features may be omitted or not performed.

In addition, each functional unit/module in each embodiment of the present application may be integrated into one unit/module, or each unit/module may exist alone physically, or two or more units/modules may be integrated together, unless otherwise specified. The integrated units/modules described above may be implemented either in hardware or in software program modules.

The integrated units/modules, if implemented in hardware, may be digital circuits, analog circuits, etc. Physical implementations of hardware structures include, but are not limited to, transistors, memristors, and the like. The processor may be any suitable hardware processor, such as CPU, GPU, FPGA, DSP and ASIC, etc., unless otherwise specified. Unless otherwise indicated, the storage elements may be any suitable magnetic or magneto-optical storage medium, such as resistive Random Access Memory RRAM (Resistive Random Access Memory), dynamic Random Access Memory DRAM (Dynamic Random Access Memory), static Random Access Memory SRAM (Static Random-Access Memory), enhanced dynamic Random Access Memory EDRAM (Enhanced Dynamic Random Access Memory), high-Bandwidth Memory HBM (High-Bandwidth Memory), hybrid Memory cube HMC (Hybrid Memory Cube), etc.

The integrated units/modules may be stored in a computer readable memory if implemented in the form of software program modules and sold or used as a stand-alone product. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a memory, including several instructions for causing a computer device (which may be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned memory includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments. The technical features of the foregoing embodiments may be arbitrarily combined, and for brevity, all of the possible combinations of the technical features of the foregoing embodiments are not described, however, all of the combinations of the technical features should be considered as being within the scope of the disclosure.

The foregoing detailed description of the invention has been presented for purposes of illustration and description, and it should be understood that the foregoing is by way of illustration and description only, and is not intended to limit the scope of the invention.

Claims

1. A method of communication, comprising:

receiving a paging message from a network device; the paging message is used for indicating that the network equipment has the mobile termination small data packet transmission MT-SDT requirement;

2. The method of claim 1, wherein the restoration cause comprises:

3. The method of claim 1, wherein the restoration cause comprises:

4. The method according to claim 1, wherein the terminal device has upstream data, the upstream data includes SDT upstream data and non-SDT upstream data, and the recovery reason includes any one of the following:

5. The method of claim 1, wherein the terminal device has uplink data, the uplink data including uplink traffic data, and the recovery reasons include:

6. The method according to claim 1, wherein there is upstream data in the terminal device, the upstream data including upstream signaling, and the recovery reason includes:

7. Method according to claim 1, characterized in that the terminal device has uplink data comprising uplink signaling and/or uplink traffic data, the recovery reasons comprising any of the following:

8. The method according to any one of claims 2-7, further comprising:

9. The method of claim 8, wherein the method further comprises:

10. Method according to claim 9, characterized in that the access category and/or the access identity and that the information about the access category and/or access identity is defined based on the restoration reason; the information about the access category and/or the access identity includes at least one of access attempt type, requirements that the access attempt needs to meet, RRC establishment cause.

11. The method of claim 10, wherein the access category and the access identity are defined based on the restoration reason.

12. The method according to claim 11, characterized in that the access attempt type and the requirements that the access attempt needs to meet are defined based on the access category and the RRC establishment cause is defined based on the access category and/or the access identity.

13. The method of claim 10, wherein the access identity is defined based on the restoration reason.

14. The method of claim 13, wherein the RRC establishment cause is defined based on the access identity.

15. A method of communication, comprising:

sending a paging message to a terminal device; the paging message is used for indicating that the network equipment has the mobile termination small data packet transmission MT-SDT requirement;

16. The method of claim 15, wherein the restoration cause comprises:

17. The method of claim 15, wherein the restoration cause comprises:

18. The method according to claim 15, wherein the terminal device has upstream data, the upstream data includes SDT upstream data and non-SDT upstream data, and the recovery reason includes any one of the following:

19. The method of claim 15, wherein the terminal device has uplink data, the uplink data including uplink traffic data, and the recovery reasons include:

20. The method of claim 15, wherein the terminal device has uplink data, the uplink data including uplink signaling, and the recovery reason includes:

21. The method according to claim 15, wherein the terminal device has uplink data, the uplink data including uplink signaling and/or uplink traffic data, and the recovery reasons include any of the following:

22. The method according to claim 21, wherein the restoration reason is determined according to an access category corresponding to the access attempt and/or a corresponding access identification of the access attempt, and a mapping relationship between the access category and/or the access identification and the restoration reason.

23. The method of claim 22, wherein the access category is determined based on the access attempt and a mapping of the access attempt to the access category; one of the access categories in the mapping corresponds to one or more access attempts.

24. Method according to claim 23, characterized in that the access category and/or the access identity and that the information about the access category and/or access identity is defined based on the restoration reason; the information about the access category and/or the access identity includes at least one of access attempt type, requirements that the access attempt needs to meet, RRC establishment cause.

25. The method of claim 24, wherein the access category and the access identification are defined based on the restoration reason.

26. The method according to claim 25, wherein the access attempt type and the requirements that the access attempt needs to meet are defined based on the access category, and wherein the RRC establishment cause is defined based on the access category and/or the access identity.

27. The method of claim 24, wherein the access identity is defined based on the recovery reason, and wherein the RRC establishment cause is defined based on the access identity.

28. A communication device, comprising: a processor and a memory;

the memory stores computer-executable instructions;

the processor executing computer-executable instructions stored in the memory to cause the communication device to perform the method of any one of claims 1-14.

29. A communication device, comprising: a processor and a memory;

the memory stores computer-executable instructions;

the processor executing computer-executable instructions stored in the memory to cause the communication device to perform the method of any one of claims 15-27.

30. A computer readable storage medium storing a computer program, which when executed by a processor performs the method of any one of claims 1-27.