WO2025036049A1 - Data transmission method and apparatus, and device - Google Patents

Abstract

The present disclosure provides a data transmission method and apparatus, and a device. The data transmission method comprises: sending a first access stratum (AS) message to an access network device, wherein the first AS message comprises a message type and reported data of a terminal; and receiving a second AS message sent by the access network device, wherein the second AS message is used for indicating whether the access network device successfully receives the first AS message.

Description

Data transmission method, device and equipment

This disclosure claims the priority of the Chinese patent application filed with the Chinese Patent Office on August 11, 2023, with application number 202311012470.5 and application name “A data transmission method, device and equipment”, all of which are incorporated herein by reference.

Technical Field

The present disclosure relates to the field of communication technology, and in particular to a data transmission method, device and equipment.

Background Art

Ambient Internet of Things (Ambient IoT, AIoT) is a newly emerging Internet of Things technology. Ambient IoT devices refer to devices that have no energy or only very limited energy of their own and communicate by obtaining energy from the external environment, such as common Radio Frequency Identification (RFID) devices.

Specifically, Ambient IoT devices are different from general User Equipment (UE) or Narrow Band Internet of Things (NB-IoT) devices. Ambient IoT devices often have no energy or only very limited energy, are generally very low in complexity and cost, and transmit very small amounts of data at very low frequencies. The UE data transmission mechanism defined in the relevant technology requires the UE to register with the network and establish a Protocol Data Unit (PDU) session before data transmission can be performed. This mechanism is too expensive for Ambient IoT devices or the Ambient IoT devices simply cannot support such a complex signaling process.

From the above, the relevant technology does not have a data transmission method suitable for Ambient IoT devices, and the data transmission of Ambient IoT devices cannot be guaranteed.

Summary of the invention

The purpose of the present disclosure is to provide a data transmission method, device and equipment to solve the problem in related technologies that Ambient IoT devices cannot accurately transmit data.

In order to solve the above technical problems, the present disclosure provides a data transmission method, which is applied to a terminal and includes:

Sending a first access stratum (AS) message to the access network device, wherein the first The AS message includes the message type and the reported data of the terminal;

Receive a second AS message sent by the access network device, where the second AS message is used to indicate whether the access network device has successfully received the first AS message.

In some embodiments, before sending the first AS message to the access network device, the method further includes:

receiving a third AS message sent by the access network device, wherein the third AS message includes at least one of a message type, a first identifier, and a requested data reporting method;

The first identifier includes an identifier and/or a group identifier of the terminal.

In some embodiments, the message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or,

The message type included in the third AS message indicates that the third AS message is a connectionless AS message.

In some embodiments, the requested data reporting method includes:

At least one of single reporting, periodic reporting, and random reporting.

In some embodiments, it also includes:

Determining to report data according to the first identifier included in the third AS message;

The sending a first access layer AS message to the access network device includes:

Sending the first AS message to the access network device according to the requested data reporting mode contained in the third AS message;

The reported data in the first AS message includes the identifier or group identifier of the terminal.

In some embodiments, the first AS message is a Radio Resource Control (RRC) message or a random access message; and/or,

The second AS message is an RRC message or a random access message; and/or,

The third AS message is a paging message or an RRC message.

The embodiment of the present disclosure also provides a data transmission method, which is applied to an access network device, including:

Receiving a first access layer AS message sent by a terminal, where the first AS message includes a message type and reported data of the terminal;

A second AS message is sent to the terminal, where the second AS message is used to indicate whether the access network device has successfully received the first AS message.

In some embodiments, before receiving the first access layer AS message sent by the terminal, the method further includes:

Sending a third AS message to the terminal, wherein the third AS message includes at least one of a message type, a first identifier, and a requested data reporting method;

The first identifier includes an identifier and/or a group identifier of the terminal.

In some embodiments, the message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or,

The message type included in the third AS message indicates that the third AS message is a connectionless AS message.

In some embodiments, the requested data reporting method includes:

At least one of single reporting, periodic reporting, and random reporting.

In some embodiments, the first AS message is a radio resource control RRC message or a random access message; and/or,

The second AS message is an RRC message or a random access message; and/or,

The third AS message is a paging message or an RRC message.

In some embodiments, the method further comprises:

Receiving the subscription information of the terminal sent by the first core network device;

According to the contract information, the reported data is sent to the application server through the second core network device.

In some embodiments, the contract information of the terminal includes: authorization information for the terminal to transmit data, and/or address information of the second core network device.

In some embodiments, sending the reported data to the application server through the second core network device according to the subscription information includes:

The reported data is sent to the second core network device according to the address information, and the reported data is sent to the application server through the second core network device.

In some embodiments, the first core network device is a unified data management (UDM) or a policy control function (PCF); and/or,

The second core network device is a network exposure function (NEF) Or user plane function (UPF).

The embodiment of the present disclosure further provides a data transmission device, which is a terminal and includes a memory, a transceiver, and a processor:

A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

Sending a first access layer AS message to an access network device through the transceiver, wherein the first AS message includes a message type and reported data of the terminal;

A second AS message sent by the access network device is received through the transceiver, where the second AS message is used to indicate whether the access network device has successfully received the first AS message.

In some embodiments, the operations further include:

Before sending the first AS message to the access network device, receiving, by the transceiver, a third AS message sent by the access network device, wherein the third AS message includes at least one of a message type, a first identifier, and a requested data reporting method;

The first identifier includes an identifier and/or a group identifier of the terminal.

In some embodiments, the message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or,

The message type included in the third AS message indicates that the third AS message is a connectionless AS message.

In some embodiments, the requested data reporting method includes:

At least one of single reporting, periodic reporting, and random reporting.

In some embodiments, the operations further include:

Determining to report data according to the first identifier included in the third AS message;

The sending a first access layer AS message to the access network device includes:

Sending the first AS message to the access network device according to the requested data reporting mode contained in the third AS message;

The reported data in the first AS message includes the identifier or group identifier of the terminal.

In some embodiments, the first AS message is a radio resource control RRC message or a random access message; and/or,

The second AS message is an RRC message or a random access message; and/or,

The third AS message is a paging message or an RRC message.

The embodiment of the present disclosure further provides a data transmission device, which is an access network device and includes a memory, a transceiver, and a processor:

A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

Receiving, by the transceiver, a first access layer AS message sent by a terminal, wherein the first AS message includes a message type and reported data of the terminal;

A second AS message is sent to the terminal through the transceiver, where the second AS message is used to indicate whether the access network device has successfully received the first AS message.

In some embodiments, the operations further include:

Before the receiving terminal sends the first access layer AS message, the transceiver sends a third AS message to the terminal, wherein the third AS message includes at least one of a message type, a first identifier, and a requested data reporting method;

The first identifier includes an identifier and/or a group identifier of the terminal.

In some embodiments, the message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or,

The message type included in the third AS message indicates that the third AS message is a connectionless AS message.

In some embodiments, the requested data reporting method includes:

At least one of single reporting, periodic reporting, and random reporting.

In some embodiments, the first AS message is a radio resource control RRC message or a random access message; and/or,

The second AS message is an RRC message or a random access message; and/or,

The third AS message is a paging message or an RRC message.

In some embodiments, the operations further include:

Receiving, by the transceiver, the subscription information of the terminal sent by the first core network device;

According to the contract information, the reported data is sent to the application server through the second core network device.

In some embodiments, the contract information of the terminal includes: Authorization information, and/or address information of the second core network device.

In some embodiments, sending the reported data to the application server through the second core network device according to the subscription information includes:

According to the address information, the reported data is sent to the second core network device through the transceiver, and the reported data is sent to the application server through the second core network device.

In some embodiments, the first core network device is a unified data management (UDM) or a policy control function (PCF); and/or,

The second core network device is a network open function NEF or a user plane function UPF.

The present disclosure also provides a data transmission device, which is applied to a terminal and includes:

A first sending unit, configured to send a first access layer AS message to an access network device, wherein the first AS message includes a message type and reported data of the terminal;

The first receiving unit is used to receive a second AS message sent by the access network device, where the second AS message is used to indicate whether the access network device has successfully received the first AS message.

In some embodiments, the apparatus further comprises:

A second receiving unit, configured to receive a third AS message sent by the access network device before sending the first AS message to the access network device, wherein the third AS message includes at least one of a message type, a first identifier, and a requested data reporting method;

The first identifier includes an identifier and/or a group identifier of the terminal.

In some embodiments, the message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or,

The message type included in the third AS message indicates that the third AS message is a connectionless AS message.

In some embodiments, the requested data reporting method includes:

At least one of single reporting, periodic reporting, and random reporting.

In some embodiments, it also includes:

A first determining unit, configured to determine to report data according to a first identifier included in the third AS message;

The sending a first access layer AS message to the access network device includes:

According to the data reporting mode of the request contained in the third AS message, send a request to the access network device. Sending the first AS message;

The reported data in the first AS message includes the identifier or group identifier of the terminal.

In some embodiments, the first AS message is a radio resource control RRC message or a random access message; and/or,

The second AS message is an RRC message or a random access message; and/or,

The third AS message is a paging message or an RRC message.

The embodiment of the present disclosure further provides a data transmission device, which is applied to an access network device, including:

A third receiving unit, configured to receive a first access layer AS message sent by a terminal, wherein the first AS message includes a message type and reported data of the terminal;

The second sending unit is used to send a second AS message to the terminal, where the second AS message is used to indicate whether the access network device has successfully received the first AS message.

In some embodiments, the apparatus further comprises:

A third sending unit, configured to send a third AS message to the terminal before receiving the first access layer AS message sent by the terminal, wherein the third AS message includes at least one of a message type, a first identifier, and a requested data reporting mode;

The first identifier includes an identifier and/or a group identifier of the terminal.

In some embodiments, the message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or,

The message type included in the third AS message indicates that the third AS message is a connectionless AS message.

In some embodiments, the requested data reporting method includes:

At least one of single reporting, periodic reporting, and random reporting.

In some embodiments, the first AS message is a radio resource control RRC message or a random access message; and/or,

The second AS message is an RRC message or a random access message; and/or,

The third AS message is a paging message or an RRC message.

In some embodiments, the apparatus further comprises:

A fourth receiving unit, configured to receive the subscription information of the terminal sent by the first core network device;

The first processing unit is configured to send a request to the application server through the second core network device according to the contract information. The server sends the reported data.

In some embodiments, the contract information of the terminal includes: authorization information for the terminal to transmit data, and/or address information of the second core network device.

In some embodiments, sending the reported data to the application server through the second core network device according to the subscription information includes:

The reported data is sent to the second core network device according to the address information, and the reported data is sent to the application server through the second core network device.

In some embodiments, the first core network device is a unified data management (UDM) or a policy control function (PCF); and/or,

The second core network device is a network open function NEF or a user plane function UPF.

The embodiment of the present disclosure also provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable a processor to execute the above-mentioned method on the terminal side or the access network device side.

The beneficial effects of the above technical solution disclosed in the present invention are as follows:

In the above scheme, the data transmission method sends a first access layer AS message to the access network device, wherein the first AS message includes the message type and the reported data of the terminal; receives a second AS message sent by the access network device, wherein the second AS message is used to indicate whether the access network device has successfully received the first AS message; and can support the implementation of: there is no need to establish a PDU session for the terminal (such as an Ambient IoT device), and the network does not need to establish and maintain a context for the terminal (such as an Ambient IoT device), and at the same time, the data transmission of the terminal (such as an Ambient IoT device) can be accurately performed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a wireless communication system architecture according to an embodiment of the present disclosure;

FIG2 is a schematic diagram of a data transmission method flow chart 1 according to an embodiment of the present disclosure;

FIG3 is a second flow chart of a data transmission method according to an embodiment of the present disclosure;

FIG4 is a schematic diagram of a specific implementation flow of the data transmission method according to an embodiment of the present disclosure;

FIG5 is a second schematic diagram of a specific implementation flow of the data transmission method according to an embodiment of the present disclosure;

FIG6 is a schematic diagram of a third specific implementation flow of the data transmission method according to an embodiment of the present disclosure;

FIG. 7 is a fourth schematic diagram of a specific implementation flow of the data transmission method according to an embodiment of the present disclosure;

FIG8 is a first structural diagram of a data transmission device according to an embodiment of the present disclosure;

FIG9 is a second structural diagram of a data transmission device according to an embodiment of the present disclosure;

FIG10 is a first structural diagram of a data transmission device according to an embodiment of the present disclosure;

FIG. 11 is a second structural diagram of the data transmission device according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

The following will be combined with the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

In the embodiments of the present disclosure, the term "and/or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B may represent three situations: A exists alone, A and B exist at the same time, and B exists alone. The character "/" generally indicates that the associated objects before and after are in an "or" relationship.

The term "plurality" in the embodiments of the present disclosure refers to two or more than two, and other quantifiers are similar thereto.

It should be noted that the technical solution provided in the embodiments of the present disclosure can be applicable to a variety of systems, especially the fifth-generation mobile communication technology (5th-Generation, 5G) system. For example, applicable systems may be global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, long term evolution advanced (LTE-A) system, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) system, 5G new radio (NR) system, etc. These various systems include terminal equipment and network equipment. The system can also include core network parts, such as Evolved Packet System (EPS), 5G System (5G System, 5GS), etc.

FIG1 is a block diagram of a wireless communication system to which the present disclosure can be applied. The system includes terminal equipment (also referred to as terminal for short) and network equipment.

The terminal device involved in the embodiments of the present disclosure 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 devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). The wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device, for example, a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device, which exchanges language and/or data with a radio access network. For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistant (PDA) and other devices. Wireless terminal devices may also be referred to as systems, subscriber units, subscriber stations, mobile stations, mobile stations, remote stations, access points, remote terminal devices, access terminal devices, user terminal devices, user agents, and user devices, which are not limited in the embodiments of the present disclosure.

The network device involved in the embodiments of the present disclosure may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present disclosure may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolution in the long term evolution (LTE) system. The network device may be an evolutionary Node B (eNB or e-NodeB), a 5G base station (the next Generation Node B, gNB) in a 5G network architecture (next generation system), or a home evolved Node B (HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present disclosure. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

Network devices and terminal devices can each use one or more antennas for multiple input multiple output (MIMO) transmission. MIMO transmission can be single user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be two-dimensional MIMO (2D-MIMO), three-dimensional MIMO (3D-MIMO), full-dimensional MIMO (FD-MIMO) or massive MIMO, or it can be diversity transmission, precoded transmission or beamforming transmission, etc.

The following first introduces the contents involved in the solution provided by the embodiment of the present disclosure.

Currently, we are studying how Ambient IoT devices can access 5G networks for communication, so as to achieve the goal of connecting everything in 5G networks. Among them, due to the very limited power consumption and complexity of Ambient IoT devices, the method of transmitting data by registering and establishing protocol data unit (PDU) sessions defined in related technologies is not suitable for data transmission of Ambient IoT devices with very limited capabilities. It is necessary to study new data transmission methods suitable for Ambient IoT devices. Specifically, the Ambient IoT scenario and the current UE data transmission mechanism are introduced as follows:

(1) Ambient IoT scenarios;

Ambient IoT scenarios have been studied in related technology projects. Ambient IoT can be widely used in scenarios such as automated logistics, smart grids, internal factory logistics in manufacturing, and sensor data reporting in smart homes. For example, in automated warehousing scenarios, Ambient IoT technology can be used to count goods when they enter and leave the warehouse. Among them, Ambient IoT devices often have no energy or only very limited energy, and are generally very low in complexity and cost, and the amount of data transmitted is very small. The data is small (for example, only tag information needs to be reported) and the frequency is very low (for example, only one data transmission may be performed).

(2) Current UE data transmission mechanism;

The currently defined UE data transmission mechanism requires the UE to register with the network and establish a PDU session before data transmission can be performed. The network needs to maintain the context information for each UE. Although some optimized small data transmission methods (such as control plane small data transmission) have been defined for Narrow Band Internet of Things (NB-IoT) devices, no matter what optimization method is used, the UE must register and establish a PDU session before it can be performed.

Based on the above, the embodiments of the present disclosure provide a data transmission method, device and equipment to solve the problem that the data transmission of Ambient IoT devices cannot be accurately performed in the related art. Among them, the method, device and equipment are based on the same application concept. Since the principles of solving the problems by the method, device and equipment are similar, the implementation of the method, device and equipment can refer to each other, and the repeated parts will not be repeated.

The data transmission method provided in the embodiment of the present disclosure is applied to a terminal, as shown in FIG2 , and includes:

Step 21: Send a first access layer AS message to the access network device, where the first AS message includes a message type and reported data of the terminal;

Step 22: Receive a second AS message sent by the access network device, where the second AS message is used to indicate whether the access network device has successfully received the first AS message.

The data transmission method provided by the embodiment of the present disclosure sends a first access layer AS message to the access network device, wherein the first AS message includes the message type and the reported data of the terminal; receives a second AS message sent by the access network device, wherein the second AS message is used to indicate whether the access network device has successfully received the first AS message; and can support the implementation of: there is no need to establish a PDU session for the terminal (such as an Ambient IoT device), and the network does not need to establish and maintain a context for the terminal (such as an Ambient IoT device), and at the same time, data transmission of the terminal (such as an Ambient IoT device) can be accurately performed.

Furthermore, before sending the first AS message to the access network device, the method also includes: receiving a third AS message sent by the access network device, the third AS message containing a message type, a first identifier, and at least one of the requested data reporting methods; wherein the first identifier includes the identifier and/or group identifier of the terminal.

In this way, at least one of the message type, the first identifier, and the requested data reporting method can be clarified. One item.

The message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or the message type included in the third AS message indicates that the third AS message is a connectionless AS message.

In this way, the message type of the first AS message and/or the third AS message can be accurately indicated. Wherein, the connectionless AS message can be understood as an AS message that does not need to establish a connection. Current AS messages such as RRC messages need to establish a connection, but are not limited thereto.

In the embodiment of the present disclosure, the requested data reporting method includes: at least one of: single reporting, periodic reporting, and random reporting.

This can support multiple methods of data reporting.

Furthermore, the data transmission method also includes: determining to report data based on a first identifier included in the third AS message; sending a first access layer AS message to the access network device includes: sending the first AS message to the access network device based on a requested data reporting method included in the third AS message; wherein the reported data in the first AS message includes an identifier or a group identifier of the terminal.

In this way, the first AS message can be accurately transmitted. Wherein, determining to report data according to the first identifier included in the third AS message includes: determining to report data when the first identifier included in the third AS message matches the identifier or group identifier of the terminal, but is not limited thereto.

The first AS message is a radio resource control RRC message or a random access message; and/or the second AS message is an RRC message or a random access message; and/or the third AS message is a paging message or an RRC message.

In this way, the first AS message, the second AS message and/or the third AS message can be specifically identified.

The embodiment of the present disclosure further provides a data transmission method, which is applied to an access network device, as shown in FIG3 , and includes:

Step 31: receiving a first access layer AS message sent by a terminal, wherein the first AS message includes a message type and reported data of the terminal;

Step 32: Send a second AS message to the terminal, where the second AS message is used to indicate whether the access network device has successfully received the first AS message.

The data transmission method provided by the embodiment of the present disclosure receives a first access layer AS message sent by a terminal, wherein the first AS message includes a message type and reported data of the terminal; sends a second AS message to the terminal, wherein the second AS message is used to indicate whether the access network device has successfully received the first AS message; and can support the implementation of: there is no need to establish a PDU session for the terminal (such as an Ambient IoT device), and the network does not need to establish and maintain a context for the terminal (such as an Ambient IoT device), while accurately transmitting data to the terminal (such as an Ambient IoT device).

Furthermore, before the receiving terminal sends the first access layer AS message, the method also includes: sending a third AS message to the terminal, the third AS message including a message type, a first identifier, and at least one of the requested data reporting methods; wherein the first identifier includes the identifier and/or group identifier of the terminal.

In this way, the terminal can clearly understand at least one of the message type, the first identifier, and the requested data reporting method.

The message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or the message type included in the third AS message indicates that the third AS message is a connectionless AS message.

In this way, the message type of the first AS message and/or the third AS message can be accurately indicated. Wherein, the connectionless AS message can be understood as an AS message that does not need to establish a connection. Current AS messages such as RRC messages need to establish a connection, but are not limited thereto.

In the embodiment of the present disclosure, the requested data reporting method includes: at least one of: single reporting, periodic reporting, and random reporting.

This can support multiple methods of data reporting.

The first AS message is a radio resource control RRC message or a random access message; and/or the second AS message is an RRC message or a random access message; and/or the third AS message is a paging message or an RRC message.

In this way, the first AS message, the second AS message and/or the third AS message can be specifically identified.

Furthermore, the method also includes: receiving the contract information of the terminal sent by the first core network device; and sending the reported data to the application server through the second core network device based on the contract information.

This can support accurate transmission of reported data.

The contract information of the terminal includes: authorization information for the terminal to transmit data, and/or address information of the second core network device.

This can further support accurate transmission of reported data.

In the disclosed embodiment, sending the reported data to the application server through the second core network device according to the contract information includes: sending the reported data to the second core network device according to the address information, and sending the reported data to the application server through the second core network device.

This supports the complete transmission of reported data.

Among them, the first core network device is a unified data management UDM or a policy control function PCF; and/or, the second core network device is a network open function NEF or a user plane function UPF.

This can support multiple ways to implement the present solution. Among them, the information interaction between the first core network device or the second core network device and the access network device can be carried out through the Access and Mobility Management Function (AMF), but is not limited to this.

The data transmission method provided in the embodiment of the present disclosure is illustrated below with examples, taking Ambient IoT (Enabled Internet of Things) devices as an example of the terminal, and taking Next Generation Radio Access Network (NG-RAN) devices as an example of the access network device.

In view of the above technical problems, the embodiments of the present disclosure provide a data transmission method, which can be specifically implemented as a method for transmitting Ambient IoT (Enabled Internet of Things) data. The method does not require the establishment of a PDU session for the Ambient IoT device, and the network does not need to establish and maintain a context for the Ambient IoT device. Specifically, the solution can be implemented in at least one of the following ways:

Method 1: Ambient IoT devices transmit data through the next generation radio access network (NG-RAN) and user plane function (UPF) (or without UPF) (see the following embodiment 1 for details).

Method 2: Ambient IoT devices transmit data through NG-RAN and AMF, or transmit data through NG-RAN, AMF and Session Management Function (SMF) (see the following Example 2 for details).

Method 3: Ambient IoT devices transmit data through NG-RAN and AIoT management functions (see the following Example 3 for details).

Method 4: Ambient IoT devices obtain the AMF through NG-RAN (Ambient IoT The authorization information of the device and the address information (for data transmission) are then used for data transmission (see the following embodiment 4 for details).

Among them: Method 1-3 is to obtain authorization information and address information during data transmission.

The following is a specific example to illustrate this solution.

Example 1: Ambient IoT devices transmit data through NG-RAN and UPF;

Specifically as shown in FIG4 , this embodiment includes the following steps:

1. AMF receives the Ambient IoT data collection request sent by the Ambient IoT App Server (AIoT App Server) through the Network Exposure Function (NEF). The request can be a request for a single or a group of AIoT Devices or a request for an AIoT Device at a certain location. If it is a request for a single or a group of AIoT Devices, the request message may include the device identification of a single or a group of AIoT Devices, the AIoT Device data reporting request, and the data type of the reported data; if it is a request for an AIoT Device at a certain location, the request message may include the AIoT Device data reporting request, the data type of the reported data (such as the device identification of the AIoT Device, monitoring data, etc.) and the requested location information.

2. AMF sends an N2 message to NG-RAN. The N2 message includes the AIoT Device data reporting request and the data type of the reported data, such as the device identification and monitoring data of the AIoT Device.

3. NG-RAN sends an Access Stratum (AS) message to the AIoT Device (corresponding to the third AS message sent to the terminal). The AS message may be a Paging message or a Radio Resource Control (RRC) message. The AS message may include a request for the AIoT Device to report data and the type of data reported, such as the device identification and monitoring data of the AIoT Device.

4. After the AIoT Device receives the request message from NG-RAN, or when the AIoT Device actively reports data, the AIoT Device sends an AS request or report message to NG-RAN (corresponding to the above-mentioned sending of the first access layer AS message to the access network device). The AS message can be a (Random Access) message or an RRC message (corresponding to the above-mentioned first AS message being a radio resource control RRC message or a random access message). The AS message contains AIoT data (corresponding to the above-mentioned first AS message containing the reported data of the terminal), an AIoT device identifier (corresponding to the above-mentioned first AS message), and an AIoT device identifier. An AS message includes information such as message type.

5. NG-RAN sends an AS response message to the AIoT Device (corresponding to the above-mentioned sending of a second AS message to the terminal). The AS message can be a Random Access message or an RRC message.

6. NG-RAN sends an uplink N2 message to AMF. The N2 message contains the AIoT device identification and authorization check request received by NG-RAN from the AIoT Device.

7. AMF sends a request message (AIoT contract or management data request) to the Unified Data Management (UDM) or PCF or Ambient IoT Management Function. The message may include the Ambient IoT device identifier to request the mobility management or policy management contract data of the AIoT Device, or the Ambient IoT management data.

8. UDM or PCF or Ambient IoT Management Function sends a response message to AMF (i.e. AIoT contract or management data response, which can carry AIoT contract or management data) to provide AMF with the mobility management or policy management contract data of AIoT Device, or Ambient IoT management data, which may include: whether AIoT Device is allowed to transmit data through the network (corresponding to the authorization information of Ambient IoT device), address information of UPF or AIoT App Server used for data transmission (such as IP address, port number), etc. Among them, the above address information corresponds to the AIoT device identifier.

9. AMF sends a downlink N2 message to NG-RAN, which may include the authorization information of the Ambient IoT device and the address information of the UPF or AIoT App Server used for data transmission (such as IP address, port number, etc.); corresponding to the above-mentioned receiving the contract information of the terminal sent by the first core network device; the contract information of the terminal includes: the authorization information of the terminal for data transmission, and/or the address information of the second core network device; the above-mentioned first core network device is the unified data management UDM or the policy control function PCF.

10. NG-RAN sends AIoT data, AIoT device identification and other information (i.e., AIoT data, corresponding to the above-mentioned reported data) to UPF or AIoT App Server based on the address information of UPF or AIoT App Server obtained in step 9, and UPF sends AIoT data, AIoT device identification and other information to AIoT App Server (corresponding to the above-mentioned sending of the reported data to the application server through the second core network device based on the contract information; specifically, sending the reported data to the second core network device based on the address information, and sending the reported data to the application server through the second core network device; the above-mentioned second core network device is the user plane function UPF). If authorization fails Or if the address information cannot be obtained, NG-RAN will discard the AIoT data.

Embodiment 2: Ambient IoT devices transmit data via NG-RAN and AMF (or via NG-RAN, AMF and SMF);

Specifically as shown in FIG5 , this embodiment includes the following steps:

1. SMF receives the Ambient IoT data collection request sent by the Ambient IoT App Server through the NEF or UPF. The request can be a request for a single or a group of AIoT devices (AIoT Device) or a request for an AIoT Device at a certain location. If it is a request for a single or a group of AIoT Devices, the request message may include the device identification of a single or a group of AIoT Devices, the AIoT Device data reporting request, and the data type of the reported data; if it is a request for an AIoT Device at a certain location, the request message may include the AIoT Device data reporting request, the data type of the reported data (such as the device identification of the AIoT Device, monitoring data, etc.) and the requested location information.

2. SMF sends an N1N2 message transmission message to AMF, which includes the AIoT Device data reporting request and the data type of the reported data, such as the device identification and monitoring data of the AIoT Device.

3. AMF sends an N2 message to NG-RAN. The N2 message includes a request message sent by SMF to NG-RAN. The message includes the AIoT Device data reporting request and the data type of the reported data, such as the device identification and monitoring data of the AIoT Device.

4. NG-RAN sends an AS message to the AIoT Device, which corresponds to the above-mentioned sending of a third AS message to the terminal. The AS message may be a Paging message or an RRC message. The AS message includes the AIoT Device's request to report data and the type of data reported, such as the device identification and monitoring data of the AIoT Device.

5. After the AIoT Device receives the request message from NG-RAN, or when the AIoT Device actively reports data, the AIoT Device sends an AS request or reporting message to NG-RAN (corresponding to the sending of the first access layer AS message to the access network device). The AS message can be a Random Access message or an RRC message (corresponding to the first AS message being a radio resource control RRC message or a random access message). The AS message contains information such as AIoT data (corresponding to the reporting data of the terminal contained in the first AS message), AIoT device identification (corresponding to the message type contained in the first AS message), etc.

6. NG-RAN sends an AS response message to the AIoT Device (corresponding to the above-mentioned sending of a second AS message to the terminal). The AS message can be a Random Access message or an RRC message.

7. NG-RAN sends an N2 message to AMF. The N2 message contains the AIoT data and AIoT device identifier received by NG-RAN from the AIoT Device. Execute steps 8a-8c or steps 9a-9c.

Among them, steps 8a-8c are AMF directly sending data to NEF or UPF, as follows:

8a. AMF sends a request message (AIoT contract or management data request) to UDM or PCF or Ambient IoT Management Function. The message may include the AIoT device identifier and request the mobility management or policy management contract data of the AIoT Device, or the Ambient IoT management data.

8b. UDM or PCF or Ambient IoT Management Function sends a response message to AMF (i.e., AIoT contract or management data response, which may carry AIoT contract or management data), and provides AMF with the mobility management or policy management contract data of AIoT Device, or Ambient IoT management data. The data may include: whether AIoT Device is allowed to transmit data through the network (corresponding to the authorization information of Ambient IoT device), the address information of UPF or NEF used for data transmission (such as IP address, port number), etc.

8c. AMF sends AIoT data, AIoT device identification and other information (i.e., AIoT data, corresponding to the above-mentioned reported data) to UPF or NEF according to the address information of UPF or NEF obtained in step 8b, and UPF or NEF sends AIoT data, AIoT device identification and other information to AIoT App Server (corresponding to the above-mentioned sending of the reported data to the application server through the second core network device according to the signing information; the above-mentioned second core network device is the network open function NEF or the user plane function UPF).

Among them, steps 9a-9c are AMF sending data to SMF, and then SMF sends data to NEF or UPF, as follows:

9a. AMF sends an AIoT data transmission message to SMF, which may include the AIoT device identifier and AIoT data.

9b. SMF sends a request message (AIoT contract or management data request) to UDM or PCF or Ambient IoT Management Function. The message may include the AIoT device identifier and request the session management or policy management contract data or Ambient IoT management data of AIoT Device. UDM or PCF or Ambient IoT Management Function sends a response message (i.e. AIoT contract or management data response), providing SMF with AIoT Device's session management or policy management contract data or Ambient IoT management data, which may include: whether AIoT Device is allowed to transmit data through the network (corresponding to the authorization information of Ambient IoT device), address information of UPF or NEF used for data transmission (such as IP address, port number), etc.

9c. SMF sends AIoT data, AIoT device identification and other information (i.e., AIoT data, corresponding to the above-mentioned reported data) to UPF or NEF according to the address information of UPF or NEF obtained in step 9b, and UPF or NEF sends AIoT data, AIoT device identification and other information to AIoT App Server (corresponding to the above-mentioned sending of the reported data to the application server through the second core network device according to the signing information; the above-mentioned second core network device is the network open function NEF or the user plane function UPF).

Example 3: Ambient IoT devices transmit data through NG-RAN and AIoT management functions;

Specifically as shown in FIG6 , this embodiment includes the following steps:

1. NG-RAN receives the Ambient IoT data collection request sent by the Ambient IoT App Server through the AIoT management function (a newly defined network element that can be responsible for AIoT contract management, capability opening and other functions). The request can be a request for a single or a group of AIoT devices (AIoT Device) or a request for an AIoT Device at a certain location. If it is a request for a single or a group of AIoT Devices, the request message may include the device identification of a single or a group of AIoT Devices, the AIoT Device data reporting request and the data type of the reported data; if it is a request for an AIoT Device at a certain location, the request message may include the AIoT Device data reporting request, the data type of the reported data (such as the device identification of the AIoT Device, monitoring data, etc.) and the requested location information. The message may also include the IP address and port number used by the AIoT management function to receive AIoT data.

2. NG-RAN sends an AS message to the AIoT Device (corresponding to the third AS message sent to the terminal as mentioned above). The AS message may be a Paging message or an RRC message. The AS message may include the AIoT Device's request to report data and the type of data reported, such as the device identification and monitoring data of the AIoT Device.

3. After the AIoT Device receives the request message from NG-RAN, or when the AIoT Device actively reports data, the AIoT Device sends an AS request or report message to NG-RAN (corresponding to the above-mentioned sending of the first access layer AS message to the access network device). The AS message can be Random Access message or RRC message (corresponding to the first AS message being a radio resource control RRC message or a random access message). The AS message includes information such as AIoT data (corresponding to the reported data of the terminal included in the first AS message), AIoT device identification (corresponding to the message type included in the first AS message).

4. NG-RAN sends an AS response message to the AIoT Device (corresponding to the above-mentioned sending of a second AS message to the terminal). The AS message can be a Random Access message or an RRC message.

5. NG-RAN sends a data transmission message to the AIoT management function, which may include information such as AIoT data and AIoT device identification received by NG-RAN from the AIoT Device; alternatively, NG-RAN sends AIoT data to the IP address and port number of the AIoT management function obtained in step 1.

6. The AIoT management function performs authorization checks on AIoT devices, such as whether the device is allowed to transmit data over the network.

7. (If the check passes) the AIoT management function sends AIoT data, AIoT device identification and other information to the AIoT App Server; this may correspond to sending the reported data to the application server through the third core network device, and the third core network device is the AIoT management function, but is not limited to this.

Embodiment 4: Ambient IoT device obtains authorization information and address information from AMF through NG-RAN before transmitting data;

Specifically as shown in FIG. 7 , this embodiment includes the following steps:

1. NG-RAN indicates to AMF through NG messages (such as NG SETUP REQUEST, NG establishment request) that it supports communication with AIoT Device (i.e., indicating supported AIoT (AIoT supported)).

2. AMF returns an NG message (such as NG SETUP RESPONSE) to NG-RAN, which may include authorization information for NG-RAN to communicate with AIoT Device, Ambient IoT device identification, address for reporting Ambient IoT data (such as UPF address, NEF address, Ambient IoT management function address or AIoT App Server address) and other information; corresponding to the above-mentioned receiving the contract information of the terminal sent by the first core network device; the contract information of the terminal includes: authorization information for the terminal to transmit data, and/or address information of the second core network device.

3. AMF receives the Ambient IoT data collection request sent by the Ambient IoT App Server through the NEF. The request can be for a single or a group of AIoT Devices or for a certain If the request is for a single/group of AIoT Devices, the request message may include the device identification of a single or group of AIoT Devices, the AIoT Device data reporting request, and the data type of the reported data; if the request is for an AIoT Device at a certain location, the request message may include the AIoT Device data reporting request, the data type of the reported data (such as the device identification of the AIoT Device, monitoring data, etc.), and the requested location information.

4. AMF sends an N2 message to NG-RAN. The N2 message includes the AIoT Device data reporting request and the data type of the reported data, such as the device identification and monitoring data of the AIoT Device.

5. NG-RAN sends an AS message to the AIoT Device (corresponding to the third AS message sent to the terminal as mentioned above). The AS message may be a Paging message or an RRC message. The AS message may include the AIoT Device's request to report data and the type of data reported, such as the device identification and monitoring data of the AIoT Device.

6. After the AIoT Device receives the request message from NG-RAN, or when the AIoT Device actively reports data, the AIoT Device sends an AS request or reporting message to NG-RAN (corresponding to the sending of the first access layer AS message to the access network device). The AS message can be a Random Access message or an RRC message (corresponding to the first AS message being a radio resource control RRC message or a random access message). The AS message contains information such as AIoT data (corresponding to the reporting data of the terminal contained in the first AS message), AIoT device identification (corresponding to the message type contained in the first AS message), etc.

7. NG-RAN sends an AS response message to the AIoT Device (corresponding to the above-mentioned sending of a second AS message to the terminal). The AS message can be a Random Access message or an RRC message.

8. NG-RAN sends AIoT data to the address obtained in step 2 (corresponding to sending the reported data to the application server through the second core network device based on the contract information).

It is to be noted that the relevant contents of the above embodiments can be referenced to each other, and the repeated contents will not be repeated here.

From the above, this solution provides a method for transmitting Ambient IoT data, so that the network does not need to establish a PDU session for the Ambient IoT device, and does not need to establish and maintain a context for the Ambient IoT device; based on this, this solution reduces the signaling overhead of the Ambient IoT device and the network, and is more suitable for Ambient IoT data transmission.

The embodiment of the present disclosure further provides a data transmission device, which is a terminal, as shown in FIG8 , including a memory 81, a transceiver 82, and a processor 83:

The memory 81 is used to store computer programs; the transceiver 82 is used to send and receive data under the control of the processor 83; the processor 83 is used to read the computer program in the memory 81 and perform the following operations:

Sending a first access layer AS message to the access network device through the transceiver 82, wherein the first AS message includes a message type and the reported data of the terminal;

The transceiver 82 receives a second AS message sent by the access network device, where the second AS message is used to indicate whether the access network device has successfully received the first AS message.

The data transmission device provided in the embodiment of the present disclosure sends a first access layer AS message to the access network device, wherein the first AS message includes the message type and the reported data of the terminal; receives a second AS message sent by the access network device, wherein the second AS message is used to indicate whether the access network device has successfully received the first AS message; and can support the implementation of: there is no need to establish a PDU session for the terminal (such as an Ambient IoT device), and the network does not need to establish and maintain a context for the terminal (such as an Ambient IoT device), and at the same time, data transmission of the terminal (such as an Ambient IoT device) can be accurately performed.

Specifically, the transceiver 82 is used to receive and send data under the control of the processor 83.

Among them, in Figure 8, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 83 and various circuits of memory represented by memory 81 are linked together. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits together, which are all well known in the art, so they are not further described herein. The bus interface provides an interface. The transceiver 82 can be a plurality of components, that is, including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, and these transmission media include, these transmission media include wireless channels, wired channels, optical cables and other transmission media. For different user devices, the user interface 84 can also be an interface that can be connected to the required devices externally and internally, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.

The processor 83 is responsible for managing the bus architecture and general processing, and the memory 81 can store data used by the processor 83 when performing operations.

In some embodiments, the processor 83 may be a central processing unit (CPU). The processor can also adopt a multi-core architecture, such as CPU, Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or Complex Programmable Logic Device (CPLD).

The processor calls the computer program stored in the memory to execute any of the methods provided by the embodiments of the present disclosure according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

Furthermore, the operation also includes: before sending the first AS message to the access network device, receiving a third AS message sent by the access network device through the transceiver, the third AS message including a message type, a first identifier, and at least one of the requested data reporting methods; wherein the first identifier includes the identifier and/or group identifier of the terminal.

The message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or the message type included in the third AS message indicates that the third AS message is a connectionless AS message.

In the embodiment of the present disclosure, the requested data reporting method includes: at least one of: single reporting, periodic reporting, and random reporting.

Furthermore, the operation also includes: determining to report data based on the first identifier included in the third AS message; sending the first access layer AS message to the access network device includes: sending the first AS message to the access network device based on the requested data reporting method included in the third AS message; wherein the reported data in the first AS message includes the identifier or group identifier of the terminal.

The first AS message is a radio resource control RRC message or a random access message; and/or the second AS message is an RRC message or a random access message; and/or the third AS message is a paging message or an RRC message.

It should be noted here that the above-mentioned device provided by the embodiment of the present disclosure can implement all the method steps implemented by the above-mentioned terminal side method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

The embodiment of the present disclosure further provides a data transmission device, which is an access network device, as shown in FIG9 , including a memory 91, a transceiver 92, and a processor 93:

The memory 91 is used to store computer programs; the transceiver 92 is used to send and receive data under the control of the processor 93; the processor 93 is used to read the computer program in the memory 91 and perform the following operations:

Receiving, through the transceiver 92, a first access layer AS message sent by the terminal, wherein the first AS message includes a message type and reported data of the terminal;

A second AS message is sent to the terminal via the transceiver 92, where the second AS message is used to indicate whether the access network device has successfully received the first AS message.

The data transmission device provided in the embodiment of the present disclosure receives a first access layer AS message sent by a terminal, wherein the first AS message includes a message type and reported data of the terminal; sends a second AS message to the terminal, wherein the second AS message is used to indicate whether the access network device has successfully received the first AS message; and can support the implementation of: there is no need to establish a PDU session for the terminal (such as an Ambient IoT device), and the network does not need to establish and maintain a context for the terminal (such as an Ambient IoT device), while accurately transmitting data to the terminal (such as an Ambient IoT device).

Specifically, the transceiver 92 is used to receive and send data under the control of the processor 93.

Among them, in Figure 9, the bus architecture can include any number of interconnected buses and bridges, specifically one or more processors represented by processor 93 and various circuits of memory represented by memory 91 are linked together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits together, which are all well known in the art, so they are not further described in this article. The bus interface provides an interface. The transceiver 92 can be a plurality of components, that is, including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, and these transmission media include transmission media such as wireless channels, wired channels, and optical cables. The processor 93 is responsible for managing the bus architecture and general processing, and the memory 91 can store data used by the processor 93 when performing operations.

The processor 93 can be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

Further, the operation further includes: before the receiving terminal sends the first access layer AS message, sending a third AS message to the terminal through the transceiver, wherein the third AS message includes Contains at least one of a message type, a first identifier, and a requested data reporting method; wherein the first identifier includes an identifier and/or a group identifier of the terminal.

The message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or the message type included in the third AS message indicates that the third AS message is a connectionless AS message.

In the embodiment of the present disclosure, the requested data reporting method includes: at least one of: single reporting, periodic reporting, and random reporting.

The first AS message is a radio resource control RRC message or a random access message; and/or the second AS message is an RRC message or a random access message; and/or the third AS message is a paging message or an RRC message.

Furthermore, the operation also includes: receiving, through the transceiver, the contract information of the terminal sent by the first core network device; and sending the reported data to the application server through the second core network device based on the contract information.

The contract information of the terminal includes: authorization information for the terminal to transmit data, and/or address information of the second core network device.

In the disclosed embodiment, sending the reported data to the application server through the second core network device according to the contract information includes: sending the reported data to the second core network device through the transceiver according to the address information, and sending the reported data to the application server through the second core network device.

Among them, the first core network device is a unified data management UDM or a policy control function PCF; and/or, the second core network device is a network open function NEF or a user plane function UPF.

It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned access network device side method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

The embodiment of the present disclosure further provides a data transmission device, which is applied to a terminal, as shown in FIG10 , and includes:

The first sending unit 101 is used to send a first access layer AS message to the access network device, where the first AS message includes a message type and reported data of the terminal;

The first receiving unit 102 is configured to receive a second AS message sent by the access network device. The second AS message is used to indicate whether the access network device has successfully received the first AS message.

The data transmission device provided in the embodiment of the present disclosure sends a first access layer AS message to the access network device, wherein the first AS message includes the message type and the reported data of the terminal; receives a second AS message sent by the access network device, wherein the second AS message is used to indicate whether the access network device has successfully received the first AS message; and can support the implementation of: there is no need to establish a PDU session for the terminal (such as an Ambient IoT device), and the network does not need to establish and maintain a context for the terminal (such as an Ambient IoT device), and at the same time, data transmission of the terminal (such as an Ambient IoT device) can be accurately performed.

Furthermore, the device also includes: a second receiving unit, used to receive a third AS message sent by the access network device before sending the first AS message to the access network device, the third AS message containing a message type, a first identifier, and at least one of the requested data reporting methods; wherein the first identifier includes the identifier and/or group identifier of the terminal.

The message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or the message type included in the third AS message indicates that the third AS message is a connectionless AS message.

In the embodiment of the present disclosure, the requested data reporting method includes: at least one of: single reporting, periodic reporting, and random reporting.

Furthermore, the data transmission device also includes: a first determination unit, used to determine data reporting based on the first identifier included in the third AS message; sending the first access layer AS message to the access network device includes: sending the first AS message to the access network device according to the requested data reporting method included in the third AS message; wherein the reported data in the first AS message includes the identifier or group identifier of the terminal.

The first AS message is a radio resource control RRC message or a random access message; and/or the second AS message is an RRC message or a random access message; and/or the third AS message is a paging message or an RRC message.

It should be noted here that the above-mentioned device provided by the embodiment of the present disclosure can implement all the method steps implemented by the above-mentioned terminal side method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

The present disclosure also provides a data transmission device, which is applied to an access network device, as shown in FIG. As shown, including:

The third receiving unit 111 is configured to receive a first access layer AS message sent by a terminal, where the first AS message includes a message type and reported data of the terminal;

The second sending unit 112 is used to send a second AS message to the terminal, where the second AS message is used to indicate whether the access network device has successfully received the first AS message.

The data transmission device provided in the embodiment of the present disclosure receives a first access layer AS message sent by a terminal, wherein the first AS message includes a message type and reported data of the terminal; sends a second AS message to the terminal, wherein the second AS message is used to indicate whether the access network device has successfully received the first AS message; and can support the implementation of: there is no need to establish a PDU session for the terminal (such as an Ambient IoT device), and the network does not need to establish and maintain a context for the terminal (such as an Ambient IoT device), while accurately transmitting data to the terminal (such as an Ambient IoT device).

Furthermore, the device also includes: a third sending unit, which is used to send a third AS message to the terminal before the first access layer AS message sent by the receiving terminal, and the third AS message includes a message type, a first identifier, and at least one of the requested data reporting methods; wherein the first identifier includes the identifier and/or group identifier of the terminal.

The message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or the message type included in the third AS message indicates that the third AS message is a connectionless AS message.

In the embodiment of the present disclosure, the requested data reporting method includes: at least one of: single reporting, periodic reporting, and random reporting.

The first AS message is a radio resource control RRC message or a random access message; and/or the second AS message is an RRC message or a random access message; and/or the third AS message is a paging message or an RRC message.

Furthermore, the device also includes: a fourth receiving unit, used to receive the contract information of the terminal sent by the first core network device; and a first processing unit, used to send the reported data to the application server through the second core network device according to the contract information.

The contract information of the terminal includes: authorization information for the terminal to transmit data, and/or address information of the second core network device.

In the embodiment of the present disclosure, according to the contract information, the second core network device sends the application The server sends the reported data, including: sending the reported data to the second core network device according to the address information, and sending the reported data to the application server through the second core network device.

Among them, the first core network device is a unified data management UDM or a policy control function PCF; and/or, the second core network device is a network open function NEF or a user plane function UPF.

It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned access network device side method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

It should be noted that the division of units in the embodiments of the present disclosure is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present disclosure may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

The embodiment of the present disclosure also provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable a processor to execute the above-mentioned method on the terminal side or the access network device side.

The non-transitory readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, tapes, magneto-optical disks (MO), etc.), optical storage (such as compact discs (CD), digital video discs (DVD), Blu-ray discs (BD), high-definition universal Optical disks (High-definition Versatile Disc, HVD), etc.), and semiconductor memories (such as ROM, Erasable Programmable Read-Only Memory (Erasable Programmable Read-Only Memory, EPROM), Electrically Erasable Programmable Read only Memory (EEPROM), Non-volatile Memory Device (NAND) FLASH, Solid State Drives (SSD)), etc.

Among them, the implementation embodiments of the methods on the above-mentioned terminal side or access network device side are all applicable to the embodiments of the non-transitory readable storage medium, and can also achieve the same technical effects.

Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.

The present disclosure is described with reference to the flowchart and/or block diagram of the method, device (system), and computer program product according to the embodiment of the present disclosure. It should be understood that each process and/or box in the flowchart and/or block diagram, as well as the combination of the process and/or box in the flowchart and/or block diagram can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.

These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

It should be noted that the division of the above modules is only a division of logical functions. In actual implementation, all or part of them can be integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software calling through processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software calling through processing elements, and some modules can be implemented in the form of hardware. For example, a module can be a separately established processing element, or it can be integrated in a chip of the above-mentioned device for implementation. In addition, it can also be stored in the memory of the above-mentioned device in the form of program code, and called and executed by a processing element of the above-mentioned device. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together, or they can be implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

For example, each module, unit, sub-unit or sub-module may be one or more integrated circuits configured to implement the above method, such as: one or more application specific integrated circuits (ASIC), or one or more microprocessors (digital signal processors, DSP), or one or more field programmable gate arrays (FPGA), etc. For another example, when a module above is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).

The terms "first", "second", etc. in the specification and claims of the present disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate so that the embodiments of the present disclosure described herein, for example, may be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices. In addition, the use of "and/or" in the specification and claims represents at least one of the connected objects, for example, A and/or B and/or C, which means seven situations including A alone, B alone, C alone, and both A and B exist, both B and C exist, both A and C exist, and A, B, and C exist. Similarly, the use of "in A and B" in the specification and claims refers to the following seven situations: At least one "is intended to be understood as "A alone, B alone, or both A and B are present".

Obviously, those skilled in the art can make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is also intended to include these modifications and variations.

Claims (46)

A data transmission method, applied to a terminal, comprising: Sending a first access layer AS message to the access network device, where the first AS message includes a message type and reported data of the terminal; Receive a second AS message sent by the access network device, where the second AS message is used to indicate whether the access network device has successfully received the first AS message. The data transmission method according to claim 1, wherein before sending the first AS message to the access network device, the method further comprises: receiving a third AS message sent by the access network device, wherein the third AS message includes at least one of a message type, a first identifier, and a requested data reporting method; The first identifier includes an identifier and/or a group identifier of the terminal. The data transmission method according to claim 2, wherein: The message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or, The message type included in the third AS message indicates that the third AS message is a connectionless AS message. The data transmission method according to claim 2, wherein the requested data reporting method comprises: At least one of single reporting, periodic reporting, and random reporting. The data transmission method according to claim 2, further comprising: Determining to report data according to the first identifier included in the third AS message; The sending a first access layer AS message to the access network device includes: Sending the first AS message to the access network device according to the requested data reporting mode contained in the third AS message; The reported data in the first AS message includes the identifier or group identifier of the terminal. The data transmission method according to claim 2, wherein: The first AS message is a radio resource control RRC message or a random access message; and/or, The second AS message is an RRC message or a random access message; and/or, The third AS message is a paging message or an RRC message. A data transmission method, applied to an access network device, comprising: Receiving a first access layer AS message sent by a terminal, where the first AS message includes a message type and reported data of the terminal; A second AS message is sent to the terminal, where the second AS message is used to indicate whether the access network device has successfully received the first AS message. The data transmission method according to claim 7, wherein, before the first access layer AS message sent by the receiving terminal, the method further comprises: Sending a third AS message to the terminal, wherein the third AS message includes at least one of a message type, a first identifier, and a requested data reporting method; The first identifier includes an identifier and/or a group identifier of the terminal. The data transmission method according to claim 8, wherein the message type contained in the first AS message indicates that the first AS message is a connectionless AS message; and/or, The message type included in the third AS message indicates that the third AS message is a connectionless AS message. The data transmission method according to claim 8, wherein the requested data reporting method comprises: At least one of single reporting, periodic reporting, and random reporting. The data transmission method according to claim 8, wherein: The first AS message is a radio resource control RRC message or a random access message; and/or, The second AS message is an RRC message or a random access message; and/or, The third AS message is a paging message or an RRC message. The data transmission method according to claim 7, wherein the method further comprises: Receiving the subscription information of the terminal sent by the first core network device; According to the contract information, the reported data is sent to the application server through the second core network device. According to the data transmission method according to claim 12, the contract information of the terminal includes: authorization information for the terminal to transmit data, and/or address information of the second core network device. The method according to claim 13, wherein the sending the reported data to the application server through the second core network device according to the subscription information comprises: The reported data is sent to the second core network device according to the address information, and the reported data is sent to the application server through the second core network device. The data transmission method according to claim 12, wherein the first core network device is a unified data management UDM or a policy control function PCF; and/or, The second core network device is a network open function NEF or a user plane function UPF. A data transmission device, the data transmission device is a terminal, the device comprises a memory, a transceiver, and a processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Sending a first access layer AS message to an access network device through the transceiver, wherein the first AS message includes a message type and reported data of the terminal; A second AS message sent by the access network device is received through the transceiver, where the second AS message is used to indicate whether the access network device has successfully received the first AS message. The data transmission device according to claim 16, wherein the operation further comprises: Before sending the first AS message to the access network device, receiving, by the transceiver, a third AS message sent by the access network device, wherein the third AS message includes at least one of a message type, a first identifier, and a requested data reporting method; The first identifier includes an identifier and/or a group identifier of the terminal. The data transmission device according to claim 17, wherein: The message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or, The message type included in the third AS message indicates that the third AS message is a connectionless AS message. The data transmission device according to claim 17, wherein the requested data reporting method comprises: At least one of single reporting, periodic reporting, and random reporting. The data transmission device according to claim 17, wherein the operation further comprises: Determining to report data according to the first identifier included in the third AS message; The sending a first access layer AS message to the access network device includes: Sending the first AS message to the access network device according to the requested data reporting mode contained in the third AS message; The reported data in the first AS message includes the identifier or group identifier of the terminal. The data transmission device according to claim 17, wherein: The first AS message is a radio resource control RRC message or a random access message; and/or, The second AS message is an RRC message or a random access message; and/or, The third AS message is a paging message or an RRC message. A data transmission device, the data transmission device is an access network device, the device comprises a memory, a transceiver, and a processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Receiving, by the transceiver, a first access layer AS message sent by a terminal, wherein the first AS message includes a message type and reported data of the terminal; A second AS message is sent to the terminal through the transceiver, where the second AS message is used to indicate whether the access network device has successfully received the first AS message. The data transmission device according to claim 22, wherein the operation further comprises: Before the receiving terminal sends the first access layer AS message, the transceiver sends a third AS message to the terminal, wherein the third AS message includes at least one of a message type, a first identifier, and a requested data reporting method; The first identifier includes an identifier and/or a group identifier of the terminal. The data transmission device according to claim 23, wherein the message type contained in the first AS message indicates that the first AS message is a connectionless AS message; and/or, The message type included in the third AS message indicates that the third AS message is a connectionless AS message. The data transmission device according to claim 23, wherein the requested data reporting method comprises: At least one of single reporting, periodic reporting, and random reporting. The data transmission device according to claim 23, wherein: The first AS message is a radio resource control RRC message or a random access message; and/or, The second AS message is an RRC message or a random access message; and/or, The third AS message is a paging message or an RRC message. The data transmission device according to claim 22, wherein the operation further comprises: Receiving, by the transceiver, the subscription information of the terminal sent by the first core network device; According to the contract information, the reported data is sent to the application server through the second core network device. The data transmission device according to claim 27, wherein the contract information of the terminal includes: authorization information for the terminal to transmit data, and/or address information of the second core network device. The device according to claim 28, wherein the sending the reported data to the application server through the second core network device according to the subscription information comprises: According to the address information, the reported data is sent to the second core network device through the transceiver, and the reported data is sent to the application server through the second core network device. The data transmission device according to claim 27, wherein the first core network device is a unified data management (UDM) or a policy control function (PCF); and/or, The second core network device is a network open function NEF or a user plane function UPF. A data transmission device, applied to a terminal, comprising: A first sending unit, configured to send a first access layer AS message to an access network device, wherein the first AS message includes a message type and reported data of the terminal; The first receiving unit is used to receive a second AS message sent by the access network device, where the second AS message is used to indicate whether the access network device has successfully received the first AS message. The data transmission device according to claim 31, wherein the device further comprises: A second receiving unit, configured to receive a third AS message sent by the access network device before sending the first AS message to the access network device, wherein the third AS message includes at least one of a message type, a first identifier, and a requested data reporting method; The first identifier includes an identifier and/or a group identifier of the terminal. The data transmission device according to claim 32, wherein: The message type included in the first AS message indicates that the first AS message is a connectionless AS message; and/or, The message type included in the third AS message indicates that the third AS message is a connectionless AS message. The data transmission device according to claim 32, wherein the requested data reporting method comprises: At least one of single reporting, periodic reporting, and random reporting. The data transmission device according to claim 32, wherein the device further comprises: A first determining unit, configured to determine to report data according to a first identifier included in the third AS message; The sending a first access layer AS message to the access network device includes: Sending the first AS message to the access network device according to the requested data reporting mode contained in the third AS message; The reported data in the first AS message includes the identifier or group identifier of the terminal. The data transmission device according to claim 32, wherein: The first AS message is a radio resource control RRC message or a random access message; and/or, The second AS message is an RRC message or a random access message; and/or, The third AS message is a paging message or an RRC message. A data transmission device, applied to an access network device, comprising: A third receiving unit, configured to receive a first access layer AS message sent by a terminal, wherein the first AS message includes a message type and reported data of the terminal; The second sending unit is used to send a second AS message to the terminal, where the second AS message is used to indicate whether the access network device has successfully received the first AS message. The data transmission device according to claim 37, wherein the device further comprises: A third sending unit, configured to send a third AS message to the terminal before receiving the first access layer AS message sent by the terminal, wherein the third AS message includes at least one of a message type, a first identifier, and a requested data reporting mode; The first identifier includes an identifier and/or a group identifier of the terminal. The data transmission device according to claim 38, wherein the first AS message The message type included indicates that the first AS message is a connectionless AS message; and/or, The message type included in the third AS message indicates that the third AS message is a connectionless AS message. The data transmission device according to claim 38, wherein the requested data reporting method comprises: At least one of single reporting, periodic reporting, and random reporting. The data transmission device according to claim 38, wherein: The first AS message is a radio resource control RRC message or a random access message; and/or, The second AS message is an RRC message or a random access message; and/or, The third AS message is a paging message or an RRC message. The data transmission device according to claim 37, wherein the device further comprises: A fourth receiving unit, configured to receive the subscription information of the terminal sent by the first core network device; The first processing unit is used to send the reported data to the application server through the second core network device according to the subscription information. According to the data transmission device according to claim 42, the contract information of the terminal includes: authorization information for the terminal to transmit data, and/or address information of the second core network device. The data transmission device according to claim 43, wherein the sending the reported data to the application server through the second core network device according to the contract information comprises: The reported data is sent to the second core network device according to the address information, and the reported data is sent to the application server through the second core network device. The data transmission device according to claim 42, wherein the first core network device is a unified data management (UDM) or a policy control function (PCF); and/or, The second core network device is a network open function NEF or a user plane function UPF. A non-transitory readable storage medium, wherein the non-transitory readable storage medium stores a computer program, wherein the computer program is used to cause a processor to execute the method according to any one of claims 1 to 15.