Data transmission method, device and equipment

Abstract

Provided are a data transmission method, device and equipment, the data transmission method comprising: receiving a first non-access stratum (NAS) message sent by a first core network device, the first NAS message comprising at least one of a message type, a first identifier, and a requested data reporting mode; sending a second NAS message to the first core network device, wherein the second NAS message comprises a message type and report data determined according to the first NAS message; wherein the first identifier comprises an identifier of the terminal and / or a group identifier. According to the scheme, the PDU session does not need to be established for the terminal (such as the Ambient IoT equipment), the network does not need to establish and maintain the context for the terminal (such as the Ambient IoT equipment), and meanwhile, the data transmission of the terminal (such as the Ambient IoT equipment) can be accurately carried out.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a data transmission method, device and equipment. Background Art

[0002] Ambient IoT is a newly emerging IoT 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.

[0003] 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 existing UE data transmission mechanism requires the UE to register with the network and establish a 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.

[0004] From the above, the prior art does not have a data transmission method suitable for Ambient IoT devices, and cannot guarantee the data transmission of Ambient IoT devices. Summary of the invention

[0005] The purpose of the present application is to 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 prior art.

[0006] In order to solve the above technical problems, an embodiment of the present application provides a data transmission method, which is applied to a terminal, including:

[0007] Receiving a first non-access layer NAS message sent by a first core network device, where the first NAS message includes at least one of a message type, a first identifier, and a requested data reporting mode;

[0008] Sending a second NAS message to the first core network device, where the second NAS message includes a message type and reporting data determined according to the first NAS message;

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

[0010] Optionally, the message type contained in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or the message type contained in the second NAS message indicates that the second NAS message is a connectionless NAS message.

[0011] Optionally, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or the group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

[0012] Optionally, the requested data reporting method includes: at least one of: single reporting, periodic reporting, and random reporting.

[0013] Optionally, also include:

[0014] Determining to report data according to the first identifier included in the first NAS message;

[0015] The sending a second NAS message to the first core network device includes:

[0016] Sending the second NAS message to the first core network device according to the requested data reporting mode included in the first NAS message;

[0017] The reported data in the second NAS message includes the identifier or group identifier of the terminal.

[0018] Optionally, the first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or,

[0019] The first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

[0020] The embodiment of the present application also provides a data transmission method, which is applied to a first core network device, including:

[0021] Sending a first non-access layer NAS message to the terminal, where the first NAS message includes at least one of a message type, an identifier and / or a group identifier of the terminal, and a requested data reporting mode;

[0022] receiving a second NAS message sent by the terminal, where the second NAS message includes a message type and reporting data determined by the terminal according to the first NAS message;

[0023] Receiving the subscription information of the terminal sent by the second core network device;

[0024] According to the contract information, the reported data is sent to the application server through the third core network device.

[0025] Optionally, the message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or,

[0026] The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

[0027] Optionally, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or,

[0028] The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

[0029] Optionally, the requested data reporting method includes:

[0030] At least one of single reporting, periodic reporting, and random reporting.

[0031] Optionally, the reported data includes an identifier or a group identifier of the terminal.

[0032] Optionally, the contract information of the terminal includes: authorization information for the terminal to transmit data, and / or address information of the third core network device.

[0033] Optionally, sending the reported data to the application server through the third core network device includes:

[0034] The reported data is sent to the third core network device according to the address information, and the reported data is sent to the application server through the third core network device.

[0035] Optionally, the first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or,

[0036] The first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

[0037] Optionally, the second core network device is a unified data management UDM or a policy control function PCF; and / or,

[0038] The third core network device is a network open function NEF or a user plane function UPF.

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

[0040] 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:

[0041] Receiving, by the transceiver, a first non-access layer NAS message sent by a first core network device, where the first NAS message includes at least one of a message type, a first identifier, and a requested data reporting mode;

[0042] Sending a second NAS message to the first core network device through the transceiver, where the second NAS message includes a message type and reporting data determined according to the first NAS message;

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

[0044] Optionally, the message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or,

[0045] The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

[0046] Optionally, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or,

[0047] The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

[0048] Optionally, the requested data reporting method includes:

[0049] At least one of single reporting, periodic reporting, and random reporting.

[0050] Optionally, the operation further includes:

[0051] Determining to report data according to the first identifier included in the first NAS message;

[0052] The sending a second NAS message to the first core network device includes:

[0053] Sending the second NAS message to the first core network device according to the requested data reporting mode included in the first NAS message;

[0054] The reported data in the second NAS message includes the identifier or group identifier of the terminal.

[0055] Optionally, the first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or,

[0056] The first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

[0057] The embodiment of the present application further provides a data transmission device, which is a first core network device and includes a memory, a transceiver, and a processor:

[0058] 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:

[0059] Sending, by the transceiver, a first non-access layer NAS message to the terminal, where the first NAS message includes a message type, an identifier and / or a group identifier of the terminal, and at least one of a requested data reporting mode;

[0060] Receiving, by the transceiver, a second NAS message sent by the terminal, where the second NAS message includes a message type and reporting data determined by the terminal according to the first NAS message;

[0061] Receiving, by the transceiver, the subscription information of the terminal sent by the second core network device;

[0062] According to the contract information, the reported data is sent to the application server through the third core network device.

[0063] Optionally, the message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or,

[0064] The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

[0065] Optionally, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or,

[0066] The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

[0067] Optionally, the requested data reporting method includes:

[0068] At least one of single reporting, periodic reporting, and random reporting.

[0069] Optionally, the reported data includes an identifier or a group identifier of the terminal.

[0070] Optionally, the contract information of the terminal includes: authorization information for the terminal to transmit data, and / or address information of the third core network device.

[0071] Optionally, sending the reported data to the application server through the third core network device includes:

[0072] According to the address information, the reported data is sent to the third core network device through the transceiver, and the reported data is sent to the application server through the third core network device.

[0073] Optionally, the first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or,

[0074] The first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

[0075] Optionally, the second core network device is a unified data management UDM or a policy control function PCF; and / or,

[0076] The third core network device is a network open function NEF or a user plane function UPF.

[0077] The embodiment of the present application also provides a data transmission device, applied to a terminal, including:

[0078] A first receiving unit, configured to receive a first non-access layer NAS message sent by a first core network device, where the first NAS message includes at least one of a message type, a first identifier, and a requested data reporting mode;

[0079] A first sending unit, configured to send a second NAS message to the first core network device, where the second NAS message includes a message type and reporting data determined according to the first NAS message;

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

[0081] Optionally, the message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or,

[0082] The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

[0083] Optionally, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or,

[0084] The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

[0085] Optionally, the requested data reporting method includes:

[0086] At least one of single reporting, periodic reporting, and random reporting.

[0087] Optionally, also include:

[0088] A first determining unit, configured to determine to report data according to a first identifier included in the first NAS message;

[0089] The sending a second NAS message to the first core network device includes:

[0090] Sending the second NAS message to the first core network device according to the requested data reporting mode included in the first NAS message;

[0091] The reported data in the second NAS message includes the identifier or group identifier of the terminal.

[0092] Optionally, the first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or,

[0093] The first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

[0094] The embodiment of the present application further provides a data transmission device, which is applied to a first core network device, including:

[0095] A second sending unit, configured to send a first non-access layer NAS message to the terminal, where the first NAS message includes a message type, an identifier and / or a group identifier of the terminal, and at least one of a requested data reporting mode;

[0096] A second receiving unit, configured to receive a second NAS message sent by the terminal, where the second NAS message includes a message type and reporting data determined by the terminal according to the first NAS message;

[0097] A third receiving unit, configured to receive the subscription information of the terminal sent by the second core network device;

[0098] The first processing unit is used to send the reported data to the application server through the third core network device according to the subscription information.

[0099] Optionally, the message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or,

[0100] The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

[0101] Optionally, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or,

[0102] The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

[0103] Optionally, the requested data reporting method includes:

[0104] At least one of single reporting, periodic reporting, and random reporting.

[0105] Optionally, the reported data includes an identifier or a group identifier of the terminal.

[0106] Optionally, the contract information of the terminal includes: authorization information for the terminal to transmit data, and / or address information of the third core network device.

[0107] Optionally, sending the reported data to the application server through the third core network device includes:

[0108] The reported data is sent to the third core network device according to the address information, and the reported data is sent to the application server through the third core network device.

[0109] Optionally, the first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or,

[0110] The first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

[0111] Optionally, the second core network device is a unified data management UDM or a policy control function PCF; and / or,

[0112] The third core network device is a network open function NEF or a user plane function UPF.

[0113] An embodiment of the present application 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 first core network device side.

[0114] The beneficial effects of the above technical solution of the present application are as follows:

[0115] In the above scheme, the data transmission method receives a first non-access layer NAS message sent by a first core network device, wherein the first NAS message includes a message type, a first identifier, and at least one of the requested data reporting methods; sends a second NAS message to the first core network device, wherein the second NAS message includes a message type and reported data determined according to the first NAS message; wherein the first identifier includes an identifier and / or a group identifier of the terminal; 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0116] Figure 1 A schematic diagram of the wireless communication system architecture of an embodiment of the present application;

[0117] Figure 2 The data transmission method of the present invention is shown in the following figure. Figure 1 ;

[0118] Figure 3 The data transmission method of the present invention is shown in the following figure. Figure 2 ;

[0119] Figure 4 The specific implementation process of the data transmission method of the embodiment of the present application is shown as follows: Figure 1 ;

[0120] Figure 5 The specific implementation process of the data transmission method of the embodiment of the present application is shown as follows: Figure 2 ;

[0121] Figure 6 The specific implementation process of the data transmission method of the embodiment of the present application is shown as follows: Figure 3 ;

[0122] Figure 7 The data transmission device structure of the embodiment of the present application is shown in FIG. Figure 1 ;

[0123] Figure 8 The data transmission device structure of the embodiment of the present application is shown in FIG. Figure 2 ;

[0124] Fig. 9 The structure of the data transmission device of the embodiment of the present application is shown as follows: Figure 1 ;

[0125] Fig.10The structure of the data transmission device of the embodiment of the present application is shown as follows: Figure 2 . DETAILED DESCRIPTION

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

[0127] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: 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.

[0128] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0129] It is explained here that the technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new air interface (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0130] Figure 1 A block diagram of a wireless communication system applicable to the embodiments of the present application is shown. The wireless communication system includes a terminal device (also referred to as a terminal) and a network device.

[0131] The terminal device involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing 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). A 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 a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0132] The network device involved in the embodiments of the present application 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 application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long-term evolution (long term evolution, LTE) system, a 5G base station (the next Generation Node B, gNB) in the 5G network architecture (next generation system), or a home evolved Node B (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 application. 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.

[0133] 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 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoded transmission or beamforming transmission, etc.

[0134] The following first introduces the contents involved in the solution provided in the embodiment of the present application.

[0135] Currently, we are studying how Ambient IoT devices can access 5G networks for communication, so as to achieve the goal of 5G network interconnection of all things. Among them, due to the very limited power consumption and complexity of Ambient IoT devices, the existing user equipment (UE) defined method of transmitting data by registering and establishing protocol data unit (PDU) sessions 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:

[0136] (1) Ambient IoT scenarios;

[0137] Ambient IoT scenarios have been studied in existing 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, AmbientIoT devices often have no energy or only very limited energy, and are generally very low in complexity and cost. The amount of data transmitted is very small (for example, only tag information needs to be reported) and the frequency is very low (for example, data transmission may only be performed once).

[0138] (2) Current UE data transmission mechanism;

[0139] 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 its 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.

[0140] Based on the above, the embodiments of the present application 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 prior 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.

[0141] The data transmission method provided in the embodiment of the present application is applied to a terminal, such as Figure 2 As shown, including:

[0142] Step 21: receiving a first non-access layer NAS message sent by a first core network device, where the first NAS message includes at least one of a message type, a first identifier, and a requested data reporting mode;

[0143] Step 22: Send a second NAS message to the first core network device, where the second NAS message includes a message type and reporting data determined according to the first NAS message; wherein the first identifier includes an identifier and / or a group identifier of the terminal.

[0144] The data transmission method provided in the embodiment of the present application receives a first non-access layer NAS message sent by a first core network device, wherein the first NAS message includes a message type, a first identifier, and at least one of the requested data reporting methods; sends a second NAS message to the first core network device, wherein the second NAS message includes a message type and reported data determined according to the first NAS message; wherein the first identifier includes an identifier and / or a group identifier of the terminal; and can support the implementation of: there is no need to establish a PDU session for a 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.

[0145] The message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or the message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

[0146] In this way, the message type of the first AS message and / or the second 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.

[0147] In an embodiment of the present application, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or the group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

[0148] This can clarify the identity and / or group identity of the terminal.

[0149] The requested data reporting method includes at least one of single reporting, periodic reporting, and random reporting.

[0150] This can support multiple methods of data reporting.

[0151] Furthermore, the data transmission method also includes: determining data reporting based on the first identifier included in the first NAS message; sending the second NAS message to the first core network device includes: sending the second NAS message to the first core network device according to the requested data reporting method included in the first NAS message; wherein the reported data in the second NAS message includes the identifier or group identifier of the terminal.

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

[0153] The first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or, the first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

[0154] This can support multiple ways to implement this solution.

[0155] The embodiment of the present application also provides a data transmission method, which is applied to a first core network device, such as Figure 3As shown, including:

[0156] Step 31: Send a first non-access layer NAS message to the terminal, where the first NAS message includes a message type, an identifier and / or a group identifier of the terminal, and at least one of a requested data reporting mode;

[0157] Step 32: receiving a second NAS message sent by the terminal, where the second NAS message includes a message type and reporting data determined by the terminal according to the first NAS message;

[0158] Step 33: receiving the subscription information of the terminal sent by the second core network device;

[0159] Step 34: According to the contract information, the reported data is sent to the application server through the third core network device.

[0160] Among them, the information interaction between the first core network device and the terminal can be carried out through the access network device, or through the access network device and the access and mobility management function (Access and Mobility Management Function, AMF), but is not limited to this.

[0161] The data transmission method provided in the embodiment of the present application sends a first non-access layer NAS message to the terminal, wherein the first NAS message includes a message type, an identifier and / or a group identifier of the terminal, and at least one of the requested data reporting methods; receives a second NAS message sent by the terminal, wherein the second NAS message includes a message type and reported data determined by the terminal according to the first NAS message; receives the contract information of the terminal sent by the second core network device; and sends the reported data to the application server through the third core network device according to the contract information; 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.

[0162] The message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or the message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

[0163] In this way, the message type of the first AS message and / or the second 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.

[0164] In an embodiment of the present application, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or the group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

[0165] This can clarify the identity and / or group identity of the terminal.

[0166] The requested data reporting method includes at least one of single reporting, periodic reporting, and random reporting.

[0167] This can support multiple methods of data reporting.

[0168] In the embodiment of the present application, the reported data includes an identifier or a group identifier of the terminal.

[0169] In this way, the reported data can be made clear and specific.

[0170] Among them, the contract information of the terminal includes: authorization information for the terminal to transmit data, and / or address information of the third core network device.

[0171] This can clearly define the contract information of the terminal, making it easier to use related information later.

[0172] In an embodiment of the present application, sending the reported data to the application server through the third core network device includes: sending the reported data to the third core network device according to the address information, and sending the reported data to the application server through the third core network device.

[0173] This can support accurate transmission of reported data.

[0174] The first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or, the first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

[0175] This can support multiple ways to implement this solution.

[0176] In an embodiment of the present application, the second core network device is a unified data management UDM or a policy control function PCF; and / or, the third core network device is a network open function NEF or a user plane function UPF.

[0177] This also supports multiple ways to implement this solution.

[0178] The data transmission method provided in the embodiment of the present application is illustrated below by taking an AmbientIoT device as an example of the terminal and taking the next generation radio access network (NG-RAN) as an example of the access network device.

[0179] In response to the above technical problems, an embodiment of the present application provides a data transmission method, which can be specifically implemented as an Ambient IoT data transmission method, involving an Ambient IoT device reporting data through a non-access stratum (NAS) message. This method does not require establishing 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.

[0180] Specifically, this solution can be implemented in at least one of the following ways:

[0181] Method 1: Ambient IoT devices transmit data through access and mobility management function (Access and Mobility Management Function, AMF) and user plane function (User Plane Function, UPF) / Session Management Function (Session Management Function, SMF) / Network Exposure Function (Network Exposure Function, NEF) (see the following embodiment 1 for details); that is, data is transmitted through UPF or SMF or NEF, and AMF.

[0182] Mode 2: Ambient IoT devices transmit data via SMF and UPF / NEF (ie, UPF or NEF) (see the following embodiment 2 for details).

[0183] Method 3: Ambient IoT devices transmit data through AMF and AIoT management functions (see the following Example 3 for details).

[0184] The following is a specific example to illustrate this solution.

[0185] Embodiment 1: Ambient IoT devices transmit data through AMF and UPF / SMF / NEF. The first core network device takes AMF as an example.

[0186] Specific as Figure 4 As shown, this embodiment includes the following steps:

[0187] 1. AMF receives the Ambient IoT data collection request sent by the Ambient IoT App Server through NEF, SMF or UPF. 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 and the data type of the reported data (i.e. the data type requested to be reported by the AIoT Device); if it is a request for an AIoT Device at a certain location, the request message may include the data type requested to be reported by the AIoT Device (e.g. the device identification of the AIoT Device, monitoring data, etc.) and the requested location information.

[0188] 2. AMF sends an N2 message to the Next Generation Radio Access Network (NG-RAN). The N2 message contains a NAS message sent by AMF to AIoT Device. The NAS message contains the type of data that AMF requests AIoTDevice to report, such as the device identification and monitoring data of AIoT Device.

[0189] 3. NG-RAN sends an access stratum (AS) message to the AIoT Device. The AS message may be a Paging message or a Radio Resource Control (RRC) message. The AS message may include a NAS message, which may include the type of data requested to be reported by the AIoT Device, such as the device identification and monitoring data of the AIoT Device; corresponding to the above-mentioned terminal receiving the first non-access stratum NAS message sent by the first core network device.

[0190] 4. After the AIoT Device receives the request message (i.e., NAS message) from the AMF, or when the AIoT Device actively reports data, the AIoT Device sends an AS request or report message to the NG-RAN. The AS message can be a RandomAccess message or an RRC message. The AS message contains a NAS message, which can contain information such as the message type (such as AIoT data transmission), AIoT data, and AIoT device identification; corresponding to the above-mentioned sending of a second NAS message to the first core network device.

[0191] 5. NG-RAN sends an AS response message to the AIoT Device. The AS message can be a Random Access message or an RRC (Radio Resource Control) message.

[0192] 6. NG-RAN sends an uplink N2 message to AMF. The N2 message may contain the NAS message received by NG-RAN from the AIoT Device.

[0193] 7. AMF sends a downlink N2 message to NG-RAN.

[0194] 8. AMF sends a request message (AIoT contract or management data request) to the Unified Data Management (UDM) or PCF or AmbientIoT Management Function (AIoT management function) to request the mobility management or policy management contract data of the AIoT Device, or the Ambient IoT management data.

[0195] 9. 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) to provide AMF with the mobility management or policy management contract data of AIoT Device, or Ambient IoT management data. The data may include: whether AIoTDevice is allowed to transmit data through the network (corresponding to the authorization information for data transmission of the above-mentioned terminal), the address information of UPF or SMF or NEF (corresponding to the above-mentioned third core network device) used for data transmission (such as IP address, port number), etc.; corresponding to the above-mentioned first core network device receiving the contract information of the terminal sent by the second core network device.

[0196] 10. AMF sends AIoT data, AIoT device identification and other information (i.e., AIoT data, corresponding to the above-mentioned reported data) to UPF, SMF or NEF according to the address information of UPF, SMF or NEF obtained in step 9, and UPF, SMF or NEF sends AIoT data, AIoT device identification and other information to AIoT App Server; corresponding to the above-mentioned first core network device, according to the signing information, the reported data is sent to the application server through the third core network device; specifically, according to the address information, the reported data is sent to the third core network device, and the reported data is sent to the application server through the third core network device.

[0197] Embodiment 2: Ambient IoT devices transmit data through SMF and UPF or NEF. The first core network device takes SMF as an example.

[0198] Specific as Figure 5 As shown, this embodiment includes the following steps:

[0199] 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 or a request for an AIoTDevice 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 and the data type of the reported data (i.e. the data type requested to be reported by the AIoT Device); if it is a request for an AIoT Device at a certain location, the request message may include the data type requested to be reported by the AIoT Device (e.g. the device identification of the AIoT Device, monitoring data, etc.) and the requested location information.

[0200] 2. SMF sends an N1N2 message transmission message to AMF, which contains an N1 SM (session management) container. The N1 SM container includes the data type that SMF requests the AIoT Device to report, such as the device identification and monitoring data of the AIoT Device.

[0201] 3. AMF sends an N2 message to NG-RAN. The N2 message contains a NAS message sent by AMF to AIoT Device, and the NAS message contains an N1 SM container.

[0202] 4. NG-RAN sends an AS message to the AIoT Device. The AS message may be a Paging message or an RRC message. The AS message may include a NAS message, and the NAS message includes an N1 SM container; corresponding to the above-mentioned terminal receiving the first non-access layer NAS message sent by the first core network device.

[0203] 5. After the AIoT Device receives the request message (i.e., NAS message) from the SMF, or when the AIoT Device actively reports data, the AIoT Device sends an AS request or report message to the NG-RAN. The AS message can be a RandomAccess message or an RRC message. The AS message contains a NAS message, which can contain information such as the message type (such as AIoT data transmission), N1 SM container (AIoT data, AIoT device identification), etc.; corresponding to the above-mentioned sending of the second NAS message to the first core network device.

[0204] 6. NG-RAN sends an AS response message to the AIoT Device. The AS message can be a Random Access message or an RRC message.

[0205] 7. NG-RAN sends an uplink N2 message to AMF. The N2 message contains the NAS message received by NG-RAN from the AIoT Device, and the NAS message contains the N1 SM container.

[0206] 8. AMF sends a downlink N2 message to NG-RAN.

[0207] 9. AMF sends an AIoT data transmission message to SMF, which contains the N1 SM container.

[0208] 10. SMF sends a request message (AIoT contract or management data request) to UDM or PCF or Ambient IoT Management Function to request the session management or policy management contract data of AIoT Device, or Ambient IoT management data.

[0209] 11. UDM or PCF or Ambient IoT Management Function sends a response message to SMF (i.e., AIoT contract or management data response, which may carry AIoT contract or management data) to provide SMF with the session management or policy management contract data of AIoT Device, or Ambient IoT management data. The data may include: whether AIoTDevice is allowed to transmit data through the network (corresponding to the authorization information for the above-mentioned terminal to perform data transmission), the address information of UPF or NEF used for data transmission (such as IP address, port number), etc.; corresponding to the first core network device receiving the contract information of the terminal sent by the second core network device.

[0210] 12. 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 11, and UPF or NEF sends AIoT data, AIoT device identification and other information to AIoT App Server; corresponding to the above-mentioned first core network device, according to the signing information, the reported data is sent to the application server through the third core network device; specifically, according to the address information, the reported data is sent to the third core network device, and the reported data is sent to the application server through the third core network device.

[0211] Embodiment 3: Ambient IoT devices transmit data through AMF and AIoT management functions. The first core network device takes AMF as an example.

[0212] Specific as Figure 6 As shown, this embodiment includes the following steps:

[0213] 1. AMF 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 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 and the data type of the reported data (i.e., the data type requested to be reported by the AIoT Device); if it is a request for an AIoT Device at a certain location, the request message may include the data type requested to be reported by the AIoT Device (such as the device identification of the AIoTDevice, monitoring data, etc.) and the requested location information.

[0214] 2. AMF sends an N2 message to NG-RAN. The N2 message contains a NAS message sent by AMF to AIoT Device. The NAS message contains the type of data that AMF requests AIoT Device to report, such as the device identification and monitoring data of AIoT Device.

[0215] 3. NG-RAN sends an AS message to the AIoT Device. The AS message can be a Paging message or an RRC message. The AS message can include a NAS message. The NAS message can include the data type requested to be reported by the AIoT Device, such as the device identification and monitoring data of the AIoT Device; corresponding to the above-mentioned terminal receiving the first non-access layer NAS message sent by the first core network device.

[0216] 4. After the AIoT Device receives the request message (i.e., NAS message) from the AMF, or when the AIoT Device actively reports data, the AIoT Device sends an AS request or report message to the NG-RAN. The AS message can be a RandomAccess message or an RRC message. The AS message contains a NAS message, which can contain information such as the message type (such as AIoT data transmission), AIoT data, and AIoT device identification; corresponding to the above-mentioned sending of a second NAS message to the first core network device.

[0217] 5. NG-RAN sends an AS response message to the AIoT Device. The AS message can be a Random Access message or an RRC message.

[0218] 6. NG-RAN sends an uplink N2 message to AMF. The N2 message may contain the NAS message received by NG-RAN from the AIoT Device.

[0219] 7. AMF sends a downlink N2 message to NG-RAN.

[0220] 8. AMF sends AIoT data, AIoT device identification and other information (i.e., AIoT data, corresponding to the above-mentioned reported data) to the AIoT management function, and the AIoT management function sends AIoT data, AIoT device identification and other information to the AIoT AppServer; 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.

[0221] 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.

[0222] From the above, this solution provides a method for Ambient IoT devices to report data through NAS messages, 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.

[0223] The embodiment of the present application also provides a data transmission device, wherein the data transmission device is a terminal, such as Figure 7 As shown, it includes a memory 71, a transceiver 72, and a processor 73:

[0224] The memory 71 is used to store computer programs; the transceiver 72 is used to send and receive data under the control of the processor 73; the processor 73 is used to read the computer program in the memory 71 and perform the following operations:

[0225] Receiving, by the transceiver 72, a first non-access layer NAS message sent by a first core network device, wherein the first NAS message includes at least one of a message type, a first identifier, and a requested data reporting mode;

[0226] Sending a second NAS message to the first core network device through the transceiver 72, where the second NAS message includes a message type and reporting data determined according to the first NAS message;

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

[0228] The data transmission device provided in the embodiment of the present application receives a first non-access layer NAS message sent by a first core network device, wherein the first NAS message includes a message type, a first identifier, and at least one of the requested data reporting methods; sends a second NAS message to the first core network device, wherein the second NAS message includes a message type and reported data determined according to the first NAS message; wherein the first identifier includes an identifier and / or a group identifier of the terminal; and can support the implementation of: there is no need to establish a PDU session for a 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.

[0229] Specifically, the transceiver 72 is used to receive and send data under the control of the processor 73.

[0230] Among them, Figure 7In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 73 and various circuits of memory represented by memory 71 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 72 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, including wireless channels, wired channels, optical cables, and other transmission media. For different user devices, the user interface 74 may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0231] The processor 73 is responsible for managing the bus architecture and general processing, and the memory 71 can store data used by the processor 73 when performing operations.

[0232] Optionally, the processor 73 may 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), and the processor may also adopt a multi-core architecture.

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

[0234] The message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or the message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

[0235] In an embodiment of the present application, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or the group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

[0236] The requested data reporting method includes at least one of single reporting, periodic reporting, and random reporting.

[0237] Further, the operation also includes: determining data reporting based on the first identifier included in the first NAS message; sending the second NAS message to the first core network device includes: sending the second NAS message to the first core network device according to the requested data reporting method included in the first NAS message; wherein the reported data in the second NAS message includes the identifier or group identifier of the terminal.

[0238] The first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or, the first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

[0239] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in 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.

[0240] The embodiment of the present application also provides a data transmission device, wherein the data transmission device is a first core network device, such as Figure 8 As shown, it includes a memory 81, a transceiver 82, and a processor 83:

[0241] 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:

[0242] Sending a first non-access layer NAS message to the terminal through the transceiver 82, where the first NAS message includes a message type, an identifier and / or a group identifier of the terminal, and at least one of a requested data reporting mode;

[0243] Receiving, by the transceiver 82, a second NAS message sent by the terminal, where the second NAS message includes a message type and reporting data determined by the terminal according to the first NAS message;

[0244] Receiving the subscription information of the terminal sent by the second core network device through the transceiver 82;

[0245] According to the contract information, the reported data is sent to the application server through the third core network device.

[0246] The data transmission device provided in the embodiment of the present application sends a first non-access layer NAS message to the terminal, wherein the first NAS message includes a message type, an identifier and / or a group identifier of the terminal, and at least one of the requested data reporting methods; receives a second NAS message sent by the terminal, wherein the second NAS message includes a message type and reported data determined by the terminal according to the first NAS message; receives the contract information of the terminal sent by the second core network device; and sends the reported data to the application server through the third core network device according to the contract information; 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.

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

[0248] Among them, Figure 8 In the embodiment, 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 may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 82 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 83 is responsible for managing the bus architecture and general processing, and the memory 81 may store data used by the processor 83 when performing operations.

[0249] The processor 83 may 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 may also adopt a multi-core architecture.

[0250] The message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or the message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

[0251] In an embodiment of the present application, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or the group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

[0252] The requested data reporting method includes at least one of single reporting, periodic reporting, and random reporting.

[0253] In the embodiment of the present application, the reported data includes an identifier or a group identifier of the terminal.

[0254] Among them, the contract information of the terminal includes: authorization information for the terminal to transmit data, and / or address information of the third core network device.

[0255] In an embodiment of the present application, sending the reported data to the application server through the third core network device includes: sending the reported data to the third core network device through the transceiver according to the address information, and sending the reported data to the application server through the third core network device.

[0256] The first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or, the first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

[0257] In an embodiment of the present application, the second core network device is a unified data management UDM or a policy control function PCF; and / or, the third core network device is a network open function NEF or a user plane function UPF.

[0258] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned first core 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.

[0259] The present application also provides a data transmission device, which is applied to a terminal, such as Fig. 9 As shown, including:

[0260] A first receiving unit 91 is configured to receive a first non-access layer NAS message sent by a first core network device, where the first NAS message includes at least one of a message type, a first identifier, and a requested data reporting mode;

[0261] A first sending unit 92 is configured to send a second NAS message to the first core network device, where the second NAS message includes a message type and reporting data determined according to the first NAS message;

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

[0263] The data transmission device provided in the embodiment of the present application receives a first non-access layer NAS message sent by a first core network device, wherein the first NAS message includes a message type, a first identifier, and at least one of the requested data reporting methods; sends a second NAS message to the first core network device, wherein the second NAS message includes a message type and reported data determined according to the first NAS message; wherein the first identifier includes an identifier and / or a group identifier of the terminal; and can support the implementation of: there is no need to establish a PDU session for a 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.

[0264] The message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or the message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

[0265] In an embodiment of the present application, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or the group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

[0266] The requested data reporting method includes at least one of single reporting, periodic reporting, and random reporting.

[0267] Furthermore, the data transmission device also includes: a first determination unit, used to determine data reporting based on the first identifier included in the first NAS message; sending the second NAS message to the first core network device includes: sending the second NAS message to the first core network device according to the requested data reporting method included in the first NAS message; wherein the reported data in the second NAS message includes the identifier or group identifier of the terminal.

[0268] The first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or, the first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

[0269] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in 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.

[0270] The embodiment of the present application also provides a data transmission device, which is applied to a first core network device, such as Fig.10 As shown, including:

[0271] The second sending unit 101 is configured to send a first non-access layer NAS message to the terminal, where the first NAS message includes a message type, an identifier and / or a group identifier of the terminal, and at least one of a requested data reporting mode;

[0272] A second receiving unit 102 is configured to receive a second NAS message sent by the terminal, where the second NAS message includes a message type and reporting data determined by the terminal according to the first NAS message;

[0273] The third receiving unit 103 is used to receive the subscription information of the terminal sent by the second core network device;

[0274] The first processing unit 104 is used to send the reported data to the application server through the third core network device according to the subscription information.

[0275] The data transmission device provided in the embodiment of the present application sends a first non-access layer NAS message to the terminal, wherein the first NAS message includes a message type, an identifier and / or a group identifier of the terminal, and at least one of the requested data reporting methods; receives a second NAS message sent by the terminal, wherein the second NAS message includes a message type and reported data determined by the terminal according to the first NAS message; receives the contract information of the terminal sent by the second core network device; and sends the reported data to the application server through the third core network device according to the contract information; 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.

[0276] The message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or the message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

[0277] In an embodiment of the present application, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or the group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

[0278] The requested data reporting method includes at least one of single reporting, periodic reporting, and random reporting.

[0279] In the embodiment of the present application, the reported data includes an identifier or a group identifier of the terminal.

[0280] Among them, the contract information of the terminal includes: authorization information for the terminal to transmit data, and / or address information of the third core network device.

[0281] In an embodiment of the present application, sending the reported data to the application server through the third core network device includes: sending the reported data to the third core network device according to the address information, and sending the reported data to the application server through the third core network device.

[0282] The first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or, the first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

[0283] In an embodiment of the present application, the second core network device is a unified data management UDM or a policy control function PCF; and / or, the third core network device is a network open function NEF or a user plane function UPF.

[0284] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned first core 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.

[0285] It should be noted that the division of units in the embodiments of the present application 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 application 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.

[0286] 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 application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of 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 application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0287] An embodiment of the present application 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 first core network device side.

[0288] 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, magnetic tapes, magneto-optical (MO)), etc.), optical storage (such as compact discs (CD), digital video discs (DVD), Blu-ray discs (BD), high-definition versatile discs (HVD), etc.), and semiconductor memories (such as ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read only memory (EEPROM), non-volatile memory (NAND (Non-volatile Memory Device) FLASH), solid-state drives (SSD)), etc.

[0289] Among them, the implementation embodiments of the method on the above-mentioned terminal side or the first core network device side are applicable to the embodiments of the non-transitory readable storage medium, and can also achieve the same technical effect.

[0290] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt 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.) that contain computer-usable program code.

[0291] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes 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 generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0292] 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 an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0293] 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, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

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

Claims

1. A data transmission method, applied to a terminal, characterized in that: include: Receiving a first non-access layer NAS message sent by a first core network device, where the first NAS message includes at least one of a message type, a first identifier, and a requested data reporting mode; Sending a second NAS message to the first core network device, where the second NAS message includes a message type and reporting data determined according to the first NAS message; The first identifier includes an identifier and / or a group identifier of the terminal.

2. The data transmission method according to claim 1, characterized in that: The message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or, The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

3. The data transmission method according to claim 1, characterized in that: The terminal identifier is a permanent identifier or a temporary identifier of the terminal; and / or, The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

4. The data transmission method according to claim 1, characterized in that: The requested data reporting method includes: At least one of single reporting, periodic reporting, and random reporting.

5. The data transmission method according to claim 1, characterized in that: Also includes: Determining to report data according to the first identifier included in the first NAS message; The sending a second NAS message to the first core network device includes: Sending the second NAS message to the first core network device according to the requested data reporting mode included in the first NAS message; The reported data in the second NAS message includes the identifier or group identifier of the terminal.

6. The data transmission method according to claim 1, characterized in that: The first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or, The first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

7. A data transmission method, applied to a first core network device, characterized in that: include: Sending a first non-access layer NAS message to the terminal, where the first NAS message includes at least one of a message type, an identifier and / or a group identifier of the terminal, and a requested data reporting mode; receiving a second NAS message sent by the terminal, where the second NAS message includes a message type and reporting data determined by the terminal according to the first NAS message; Receiving the subscription information of the terminal sent by the second core network device; According to the contract information, the reported data is sent to the application server through the third core network device.

8. The data transmission method according to claim 7, characterized in that: The message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or, The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

9. The data transmission method according to claim 7, characterized in that: The terminal identifier is a permanent identifier or a temporary identifier of the terminal; and / or, The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

10. The data transmission method according to claim 7, characterized in that: The requested data reporting method includes: At least one of single reporting, periodic reporting, and random reporting.

11. The data transmission method according to claim 7, characterized in that: The reported data includes the identifier or group identifier of the terminal.

12. The data transmission method according to claim 7, characterized in that: The contract information of the terminal includes: authorization information for the terminal to transmit data, and / or address information of the third core network device.

13. The data transmission method according to claim 12, characterized in that: The sending the reported data to the application server through the third core network device includes: The reported data is sent to the third core network device according to the address information, and the reported data is sent to the application server through the third core network device.

14. The data transmission method according to claim 7, characterized in that: The first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or, The first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

15. The data transmission method according to claim 7, characterized in that: The second core network device is a unified data management (UDM) or a policy control function (PCF); and / or, The third core network device is a network open function NEF or a user plane function UPF.

16. A data transmission device, the data transmission device being a terminal, characterized in that: Including memory, transceiver, 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 non-access layer NAS message sent by a first core network device, where the first NAS message includes at least one of a message type, a first identifier, and a requested data reporting mode; Sending a second NAS message to the first core network device through the transceiver, where the second NAS message includes a message type and reporting data determined according to the first NAS message; The first identifier includes an identifier and / or a group identifier of the terminal.

17. The data transmission device according to claim 16, characterized in that: The message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or, The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

18. The data transmission device according to claim 16, characterized in that: The terminal identifier is a permanent identifier or a temporary identifier of the terminal; and / or, The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

19. The data transmission device according to claim 16, characterized in that: The requested data reporting method includes: At least one of single reporting, periodic reporting, and random reporting.

20. The data transmission device according to claim 16, characterized in that: The operations also include: Determining to report data according to the first identifier included in the first NAS message; The sending a second NAS message to the first core network device includes: Sending the second NAS message to the first core network device according to the requested data reporting mode included in the first NAS message; The reported data in the second NAS message includes the identifier or group identifier of the terminal.

21. The data transmission device according to claim 16, characterized in that: The first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or, The first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

22. A data transmission device, the data transmission device being a first core network device, characterized in that: Including memory, transceiver, 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, by the transceiver, a first non-access layer NAS message to the terminal, where the first NAS message includes a message type, an identifier and / or a group identifier of the terminal, and at least one of a requested data reporting mode; Receiving, by the transceiver, a second NAS message sent by the terminal, where the second NAS message includes a message type and reporting data determined by the terminal according to the first NAS message; Receiving, by the transceiver, the subscription information of the terminal sent by the second core network device; According to the contract information, the reported data is sent to the application server through the third core network device.

23. The data transmission device according to claim 22, characterized in that: The message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or, The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.

24. The data transmission device according to claim 22, characterized in that: The terminal identifier is a permanent identifier or a temporary identifier of the terminal; and / or, The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.

25. The data transmission device according to claim 22, characterized in that: The requested data reporting method includes: At least one of single reporting, periodic reporting, and random reporting.

26. The data transmission device according to claim 22, characterized in that: The reported data includes the identifier or group identifier of the terminal.

27. The data transmission device according to claim 22, characterized in that: The contract information of the terminal includes: authorization information for the terminal to transmit data, and / or address information of the third core network device.

28. The data transmission device according to claim 27, characterized in that: The sending the reported data to the application server through the third core network device includes: According to the address information, the reported data is sent to the third core network device through the transceiver, and the reported data is sent to the application server through the third core network device.

29. The data transmission device according to claim 22, characterized in that: The first core network device is an access and mobility management function, and the first NAS message and the second NAS message are both mobility management NAS messages; or, The first core network device is a session management function, and the first NAS message and the second NAS message are both session management NAS messages.

30. The data transmission device according to claim 22, characterized in that: The second core network device is a unified data management (UDM) or a policy control function (PCF); and / or, The third core network device is a network open function NEF or a user plane function UPF.

31. A data transmission device, applied to a terminal, characterized in that: include: A first receiving unit, configured to receive a first non-access layer NAS message sent by a first core network device, where the first NAS message includes at least one of a message type, a first identifier, and a requested data reporting mode; A first sending unit, configured to send a second NAS message to the first core network device, where the second NAS message includes a message type and reporting data determined according to the first NAS message; The first identifier includes an identifier and / or a group identifier of the terminal.

32. A data transmission device, applied to a first core network device, characterized in that: include: A second sending unit, configured to send a first non-access layer NAS message to the terminal, where the first NAS message includes a message type, an identifier and / or a group identifier of the terminal, and at least one of a requested data reporting mode; A second receiving unit, configured to receive a second NAS message sent by the terminal, where the second NAS message includes a message type and reporting data determined by the terminal according to the first NAS message; A third receiving unit, configured to receive the subscription information of the terminal sent by the second core network device; The first processing unit is used to send the reported data to the application server through the third core network device according to the subscription information.

33. A non-transitory readable storage medium, characterized in that: The non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the method according to any one of claims 1 to 15.

Images