Data transmission method, apparatus and device
By receiving and sending non-access layer NAS messages, the problem of inaccurate data transmission of Ambient IoT devices is solved, and accurate data transmission without establishing a PDU session is achieved.
Patent Information
- Application Number
- PCT/CN2024/103467
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-08-11
- Filing Date
- 2024-07-04
- Publication Date
- 2025-02-20
AI Technical Summary
The prior art cannot effectively solve the data transmission problem of Ambient IoT devices, resulting in inaccurate data transmission.
By receiving the first non-access layer NAS message sent by the first core network device, including the message type, terminal identification and requested data reporting method, the second NAS message is sent to the first core network device, including the message type and report data, Implement data transmission of terminals.
This method supports data transmission of Ambient IoT devices, and does not require the establishment of a PDU session, which reduces the signaling overhead of the network to the terminal and realizes accurate data transmission.
Smart Images

Figure CN2024103467_20022025_PF_FP_ABST
Abstract
Description
Data transmission method, device and equipment
[0001] This disclosure claims priority to a Chinese patent application filed with the Patent Office of China on August 11, 2023, with application number 202311012478.1 and application name “A Data Transmission Method, Device and Equipment,” the entire contents of which are incorporated herein by reference. Technical Field
[0002] The present disclosure relates to the field of communication technology, and in particular to a data transmission method, apparatus, and device. Background Art
[0003] The Ambient Internet of Things (Ambient IoT or AIoT) is an emerging IoT technology. Ambient IoT devices refer to devices that have no or very limited energy of their own and communicate by obtaining energy from the external environment, such as common Radio Frequency Identification (RFID) devices.
[0004] Specifically, Ambient IoT devices differ from typical User Equipment (UE) or Narrowband Internet of Things (NB-IoT) devices in that they typically have no or very limited energy, are generally very low-complexity and cost-effective, and transmit very small amounts of data infrequently. The UE data transmission mechanism defined in related technologies requires the UE to register with the network and establish a PDU session before data transmission can proceed. This mechanism is prohibitively expensive for Ambient IoT devices, or they simply cannot support such a complex signaling process.
[0005] From the above, the related art does not have a data transmission method suitable for Ambient IoT devices, and cannot guarantee the data transmission of Ambient IoT devices.
[0006] Summary of the Invention
[0007] The present disclosure aims to provide a data transmission method, apparatus and device to solve the problem in the related art that data transmission of Ambient IoT devices cannot be accurately performed.
[0008] The present disclosure provides a data transmission method, applied to a terminal, including:
[0009] Receiving a first non-access stratum 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;
[0010] Sending a second NAS message to the first core network device, where the second NAS message includes a message type and reported data determined according to the first NAS message;
[0011] The first identifier includes the identifier of the terminal and / or the group identifier.
[0012] Optionally, 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.
[0013] 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.
[0014] Optionally, the requested data reporting method includes: at least one of: single reporting, periodic reporting, and random reporting.
[0015] Optionally, the method further includes:
[0016] Determining to report data according to the first identifier included in the first NAS message;
[0017] The sending the second NAS message to the first core network device includes:
[0018] Sending the second NAS message to the first core network device according to the requested data reporting mode included in the first NAS message;
[0019] The reported data in the second NAS message includes the identifier or group identifier of the terminal.
[0020] 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,
[0021] 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.
[0022] The embodiment of the present disclosure further provides a data transmission method, applied to a first core network device, including:
[0023] Sending a first non-access stratum (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;
[0024] 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;
[0025] Receiving the subscription information of the terminal sent by the second core network device;
[0026] According to the contract information, the reported data is sent to the application server through the third core network device.
[0027] Optionally, the message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or,
[0028] The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.
[0029] Optionally, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or,
[0030] The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.
[0031] Optionally, the requested data reporting method includes:
[0032] At least one of single reporting, periodic reporting, and random reporting.
[0033] Optionally, the reported data includes an identifier or a group identifier of the terminal.
[0034] 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.
[0035] Optionally, the sending the reported data to the application server through the third core network device includes:
[0036] 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.
[0037] 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,
[0038] 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.
[0039] Optionally, the second core network device is a unified data management (UDM) or a policy control function (PCF); and / or,
[0040] The third core network device is a network open function NEF or a user plane function UPF.
[0041] The present disclosure also provides a data transmission device, which is a terminal and includes a memory, a transceiver, and a processor.
[0042] 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:
[0043] Receiving, by the transceiver, a first non-access stratum (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;
[0044] Sending, by the transceiver, a second NAS message to the first core network device, where the second NAS message includes a message type and reported data determined according to the first NAS message;
[0045] The first identifier includes the identifier of the terminal and / or the group identifier.
[0046] Optionally, the message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or,
[0047] The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.
[0048] Optionally, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or,
[0049] The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.
[0050] Optionally, the requested data reporting method includes:
[0051] At least one of single reporting, periodic reporting, and random reporting.
[0052] Optionally, the operation further includes:
[0053] Determining to report data according to the first identifier included in the first NAS message;
[0054] The sending the second NAS message to the first core network device includes:
[0055] Sending the second NAS message to the first core network device according to the requested data reporting mode included in the first NAS message;
[0056] The reported data in the second NAS message includes the identifier or group identifier of the terminal.
[0057] 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,
[0058] 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.
[0059] The embodiment of the present disclosure further provides a data transmission device, which is a first core network device and includes a memory, a transceiver, and a processor:
[0060] 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:
[0061] Sending, by the transceiver, a first non-access stratum (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;
[0062] 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;
[0063] Receiving, through the transceiver, the subscription information of the terminal sent by the second core network device;
[0064] According to the contract information, the reported data is sent to the application server through the third core network device.
[0065] Optionally, the message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or,
[0066] The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.
[0067] Optionally, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or,
[0068] The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.
[0069] Optionally, the requested data reporting method includes:
[0070] At least one of single reporting, periodic reporting, and random reporting.
[0071] Optionally, the reported data includes an identifier or a group identifier of the terminal.
[0072] 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.
[0073] Optionally, the sending the reported data to the application server through the third core network device includes:
[0074] 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.
[0075] 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,
[0076] 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.
[0077] Optionally, the second core network device is a unified data management (UDM) or a policy control function (PCF); and / or,
[0078] The third core network device is a network open function NEF or a user plane function UPF.
[0079] The present disclosure also provides a data transmission device, which is applied to a terminal and includes:
[0080] A first receiving unit is configured to receive a first non-access stratum 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;
[0081] 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;
[0082] The first identifier includes the identifier of the terminal and / or the group identifier.
[0083] Optionally, the message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or,
[0084] The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.
[0085] Optionally, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or,
[0086] The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.
[0087] Optionally, the requested data reporting method includes:
[0088] At least one of single reporting, periodic reporting, and random reporting.
[0089] Optionally, the device further comprises:
[0090] a first determining unit, configured to determine, based on a first identifier included in the first NAS message, whether to report data;
[0091] The sending the second NAS message to the first core network device includes:
[0092] Sending the second NAS message to the first core network device according to the requested data reporting mode included in the first NAS message;
[0093] The reported data in the second NAS message includes the identifier or group identifier of the terminal.
[0094] 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,
[0095] 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.
[0096] The embodiment of the present disclosure further provides a data transmission apparatus, applied to a first core network device, including:
[0097] A second sending unit is configured to send a first non-access stratum 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;
[0098] 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;
[0099] A third receiving unit, configured to receive the subscription information of the terminal sent by the second core network device;
[0100] The first processing unit is used to send the reported data to the application server through the third core network device according to the contract information.
[0101] Optionally, the message type included in the first NAS message indicates that the first NAS message is a connectionless NAS message; and / or,
[0102] The message type included in the second NAS message indicates that the second NAS message is a connectionless NAS message.
[0103] Optionally, the identifier of the terminal is a permanent identifier or a temporary identifier of the terminal; and / or,
[0104] The group identifier of the terminal is a permanent identifier or a temporary identifier of a terminal group including the terminal.
[0105] Optionally, the requested data reporting method includes:
[0106] At least one of single reporting, periodic reporting, and random reporting.
[0107] Optionally, the reported data includes an identifier or a group identifier of the terminal.
[0108] 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.
[0109] Optionally, the sending the reported data to the application server through the third core network device includes:
[0110] 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.
[0111] 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,
[0112] 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.
[0113] Optionally, the second core network device is a unified data management (UDM) or a policy control function (PCF); and / or,
[0114] The third core network device is a network open function NEF or a user plane function UPF.
[0115] An embodiment of the present disclosure also provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable a processor to execute the above-mentioned method on the terminal side or the first core network device side.
[0116] The beneficial effects of the above technical solutions disclosed herein are as follows:
[0117] 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 the identifier and / or group identifier of the terminal; and can support the implementation of: 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
[0118] FIG1 is a schematic diagram of a wireless communication system architecture according to an embodiment of the present disclosure;
[0119] FIG2 is a flowchart of a data transmission method according to an embodiment of the present disclosure;
[0120] FIG3 is a second flow chart of a data transmission method according to an embodiment of the present disclosure;
[0121] FIG4 is a schematic diagram of a first embodiment of a data transmission method according to an embodiment of the present disclosure;
[0122] FIG5 is a second schematic diagram of a specific implementation flow of the data transmission method according to an embodiment of the present disclosure;
[0123] FIG6 is a third schematic diagram of a specific implementation flow of the data transmission method according to an embodiment of the present disclosure;
[0124] FIG7 is a first structural diagram of a data transmission device according to an embodiment of the present disclosure;
[0125] FIG8 is a second structural diagram of a data transmission device according to an embodiment of the present disclosure;
[0126] FIG9 is a first structural diagram of a data transmission device according to an embodiment of the present disclosure;
[0127] FIG10 is a second structural diagram of the data transmission device according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0128] The following will be combined with the accompanying drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure and not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present disclosure.
[0129] In the embodiments of the present disclosure, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.
[0130] In the embodiments of the present disclosure, the term "plurality" refers to two or more than two, and other quantifiers are similar thereto.
[0131] It is explained here that the technical solutions provided by the embodiments of the present disclosure can be applicable to a variety of systems, especially the fifth generation mobile communication (5th-Generation, 5G) system. 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 devices and network devices. The system may also include core network parts, such as the Evolved Packet System (EPS), 5G System (5GS), etc.
[0132] Figure 1 shows a block diagram of a wireless communication system to which embodiments of the present disclosure may be applied. The wireless communication system includes a terminal device (also referred to as a terminal) and a network device.
[0133] The terminal device involved in the embodiments of the present disclosure may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connection function, or other processing device 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 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 "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 voice and / or data with a radio access network. For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital 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, or a user device, but is not limited in the embodiments of the present disclosure.
[0134] The network device involved in the embodiments of the present disclosure may be a base station, which may include multiple cells providing services to terminals. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface, or may be named by another name. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present disclosure may be a base transceiver station (BTS) in the Global System for Mobile communications (GSM) or code division multiple access (CDMA), a network device (NodeB) in wide-band code division multiple access (WCDMA), an evolutionary Node B (eNB or e-NodeB) in the long term evolution (LTE) system, a 5G base station (gNB) in the next generation system, a home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of the present disclosure. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be geographically separated.
[0135] 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 configuration and number of antenna combinations, MIMO transmission can be two-dimensional MIMO (2D-MIMO), three-dimensional MIMO (3D-MIMO), full-dimensional MIMO (FD-MIMO), or massive MIMO. It can also use diversity transmission, precoding, or beamforming.
[0136] The following first introduces the contents involved in the solution provided by the embodiment of the present disclosure.
[0137] Research is currently underway to understand how Ambient IoT devices can access 5G networks for communication, thereby achieving the goal of the 5G Internet of Everything. However, due to the limited power consumption and complexity of Ambient IoT devices, the data transmission method defined by related technologies, whereby user equipment (UE) registers and establishes Protocol Data Unit (PDU) sessions, is not suitable for data transmission on these devices. Therefore, new data transmission methods suitable for Ambient IoT devices are needed. Specifically, the following describes Ambient IoT scenarios and current UE data transmission mechanisms:
[0138] (1) Ambient IoT scenarios;
[0139] Ambient IoT scenarios have been studied in related technologies. 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 as they enter and leave the warehouse. Ambient IoT devices often have no or very limited energy, are generally very low in complexity and cost, transmit very small amounts of data (for example, only tag information needs to be reported), and transmit data infrequently (for example, data may only be transmitted once).
[0140] (2) Current UE data transmission mechanism;
[0141] The currently defined UE data transmission mechanism requires the UE to register with the network and establish a PDU session before data transmission can proceed. The network must maintain context information for each UE. Although some optimized small data transmission methods (such as control plane small data transmission) have been defined for Narrowband Internet of Things (NB-IoT) devices, all optimized methods require the UE to register and establish a PDU session before data transmission can proceed.
[0142] Based on the foregoing, the embodiments of the present disclosure provide a data transmission method, apparatus, and device to address the related art issue of inaccurate data transmission between Ambient IoT devices. The method, apparatus, and device are based on the same patent application concept. Since the principles underlying the problems solved by the method, apparatus, and device are similar, their implementations can be referenced in conjunction with each other, and any repetitions will not be repeated.
[0143] The data transmission method provided in the embodiment of the present disclosure is applied to a terminal, as shown in FIG2 , and includes:
[0144] Step 21: Receive a first non-access stratum (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;
[0145] 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 the identifier and / or group identifier of the terminal.
[0146] The data transmission method provided by the embodiment of the present disclosure 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: no need to establish a PDU session for the terminal (such as an Ambient IoT device), and the network does not need to establish and maintain a context for the terminal (such as an Ambient IoT device), while accurately performing data transmission for the terminal (such as an Ambient IoT device).
[0147] 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.
[0148] In this way, the message type of the first access stratum (AS) message and / or the second AS message can be accurately indicated. Among them, the connectionless AS message can be understood as an AS message that does not require a connection to be established. Current AS messages, such as radio resource control (RRC) messages, do require a connection to be established, but the present invention is not limited thereto.
[0149] In the embodiment of the present disclosure, 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.
[0150] This allows the identification and / or group identification of the terminal to be made clear.
[0151] The requested data reporting method includes at least one of: single reporting, periodic reporting, and random reporting.
[0152] This can support multiple ways of reporting data.
[0153] 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.
[0154] In this way, the second NAS message can be accurately transmitted. Wherein, determining to report data based on 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.
[0155] 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.
[0156] This can support multiple ways to implement this solution.
[0157] The present disclosure also provides a data transmission method, which is applied to a first core network device, as shown in FIG3 , and includes:
[0158] Step 31: Send a first non-access stratum (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;
[0159] Step 32: 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;
[0160] Step 33: Receive the subscription information of the terminal sent by the second core network device;
[0161] Step 34: According to the contract information, the reported data is sent to the application server through the third core network device.
[0162] 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.
[0163] The data transmission method provided by the embodiment of the present disclosure sends 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 the requested data reporting methods; receives a second NAS message sent by the terminal, where the second NAS message includes a message type and reported data determined by the terminal based on the first NAS message; receives the subscription information of the terminal sent by a second core network device; and sends the reported data to an application server through a third core network device based on the subscription information; and can support the implementation of: no need to establish a PDU session for the terminal (such as an Ambient IoT device), and the network does not need to establish and maintain a context for the terminal (such as an Ambient IoT device), while accurately transmitting data for the terminal (such as an Ambient IoT device).
[0164] 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.
[0165] 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 require a connection to be established. Current AS messages such as RRC messages require a connection to be established, but the present invention is not limited thereto.
[0166] In the embodiment of the present disclosure, 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.
[0167] This allows the identification and / or group identification of the terminal to be made clear.
[0168] The requested data reporting method includes at least one of: single reporting, periodic reporting, and random reporting.
[0169] This can support multiple ways of reporting data.
[0170] In the embodiment of the present disclosure, the reported data includes an identifier or a group identifier of the terminal.
[0171] In this way, the reported data can be made clear and specific.
[0172] 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.
[0173] This can clearly define the contract information of the terminal, making it easier to use related information later.
[0174] In the disclosed embodiment, 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.
[0175] This can support accurate transmission of reported data.
[0176] 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.
[0177] This can support multiple ways to implement this solution.
[0178] In the disclosed embodiment, 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 exposure function (NEF) or a user plane function (UPF).
[0179] This also supports multiple ways to implement this solution.
[0180] The data transmission method provided in the embodiment of the present disclosure is illustrated below with an example, taking an Ambient IoT device as an example of a terminal and a Next Generation Radio Access Network (NG-RAN) as an example of an access network device.
[0181] In response to the above technical problems, an embodiment of the present disclosure provides a data transmission method, which can be specifically implemented as an Ambient IoT data transmission method, involving Ambient IoT devices reporting data through non-access stratum (NAS) messages. 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.
[0182] Specifically, this solution can be implemented in at least one of the following ways:
[0183] Method 1: Ambient IoT devices transmit data through the Access and Mobility Management Function (AMF) and the User Plane Function (UPF) / Session Management Function (SMF) / Network Exposure Function (NEF) (see the following embodiment 1 for details); that is, data is transmitted through UPF or SMF or NEF, and AMF.
[0184] Method 2: Ambient IoT devices transmit data through SMF and UPF / NEF (ie, UPF or NEF) (see the following embodiment 2 for details).
[0185] Method 3: Ambient IoT devices transmit data through AMF and AIoT management functions (see Example 3 below for details).
[0186] The following is a specific example to illustrate this solution.
[0187] Example 1: Ambient IoT devices transmit data through AMF and UPF / SMF / NEF. The first core network device takes AMF as an example.
[0188] Specifically as shown in FIG4 , this embodiment includes the following steps:
[0189] 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 the 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 AIoT Device, monitoring data, etc.) and the requested location information.
[0190] 2. AMF sends an N2 message to the Next Generation Radio Access Network (NG-RAN). The N2 message contains the NAS message sent by AMF to the AIoT Device. The NAS message contains the type of data that AMF requests the AIoT Device to report, such as the device identification and monitoring data of the AIoT Device.
[0191] 3. NG-RAN sends an access stratum (AS) message to the AIoT Device. The AS message can be a paging message or a radio resource control (RRC) message. The AS message can include an NAS message, which can 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; this corresponds to the terminal receiving the first non-access stratum NAS message sent by the first core network device.
[0192] 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 random access message or an RRC message. The AS message contains a NAS message, which can include information such as the message type (such as AIoT data transmission), AIoT data (data), and AIoT device identification; this corresponds to the above-mentioned sending of a second NAS message to the first core network device.
[0193] 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.
[0194] 6. NG-RAN sends an uplink N2 message to AMF. The N2 message may include the NAS message received by NG-RAN from the AIoT Device.
[0195] 7. AMF sends a downlink N2 message to NG-RAN.
[0196] 8. AMF sends a request message (AIoT contract or management data request) to the Unified Data Management (UDM) or PCF or Ambient IoT Management Function to request the mobility management or policy management contract data of the AIoT Device, or the Ambient IoT management data.
[0197] 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 AIoT Device 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 Internet Protocol (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.
[0198] 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 the AIoT data, AIoT device identification and other information to the AIoT App Server; corresponding to the above-mentioned first core network device, according to the contract 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.
[0199] Example 2: Ambient IoT devices transmit data through SMF and UPF or NEF. The first core network device takes SMF as an example.
[0200] Specifically as shown in FIG5 , this embodiment includes the following steps:
[0201] 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 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 the 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 AIoT Device, monitoring data, etc.) and the requested location information.
[0202] 2. SMF sends an N1N2 message transmission message to AMF, which contains an N1 session management (SM) 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.
[0203] 3. AMF sends an N2 message to NG-RAN. The N2 message contains the NAS message sent by AMF to AIoT Device, and the NAS message contains the N1 SM container.
[0204] 4. The 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, and the NAS message includes an N1 SM container. This corresponds to the terminal receiving the first NAS message sent by the first core network device.
[0205] 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 Random Access message or an RRC message. The AS message contains a NAS message, which can include information such as the message type (such as AIoT data transmission), N1 SM container (AIoT data, AIoT device identification), etc.; this corresponds to the above-mentioned sending of a second NAS message to the first core network device.
[0206] 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.
[0207] 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.
[0208] 8. AMF sends a downlink N2 message to NG-RAN.
[0209] 9. AMF sends an AIoT data transmission message to SMF, which contains the N1 SM container.
[0210] 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.
[0211] 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 AIoT Device 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 NEF 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.
[0212] 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 the AIoT data, AIoT device identification and other information to the AIoT App Server; corresponding to the above-mentioned first core network device, according to the contract 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.
[0213] Example 3: Ambient IoT devices transmit data through AMF and AIoT management functions. The first core network device takes AMF as an example.
[0214] Specifically as shown in FIG6 , this embodiment includes the following steps:
[0215] 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 exposure, 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 the 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 AIoT Device, monitoring data, etc.) and the requested location information.
[0216] 2. AMF sends an N2 message to NG-RAN. The N2 message contains the 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.
[0217] 3. The 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 an NAS message. The NAS message can include the type of data requested to be reported by the AIoT Device, such as the device identifier and monitoring data of the AIoT Device. This corresponds to the terminal receiving the first NAS message sent by the first core network device.
[0218] 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 Random Access message or an RRC message. The AS message contains a NAS message, which can include information such as the message type (such as AIoT data transmission), AIoT data, and AIoT device identification; this corresponds to the above-mentioned sending of a second NAS message to the first core network device.
[0219] 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.
[0220] 6. NG-RAN sends an uplink N2 message to AMF. The N2 message may include the NAS message received by NG-RAN from the AIoT Device.
[0221] 7. AMF sends a downlink N2 message to NG-RAN.
[0222] 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 the AIoT data, AIoT device identification and other information to the AIoT App Server; this may correspond to sending the reported data to the application server through the third core network device, and the third core network device is the AIoT management function, but is not limited to this.
[0223] It is to be noted that the relevant contents of the above embodiments can be referred to each other, and the repeated parts will not be repeated here.
[0224] As described above, this solution provides a method for Ambient IoT devices to report data through NAS messages, eliminating the need for the network to establish a PDU session for the Ambient IoT device and the need to establish and maintain a context for the Ambient IoT device. This reduces the signaling overhead for both the Ambient IoT device and the network, making it more suitable for Ambient IoT data transmission.
[0225] The embodiment of the present disclosure further provides a data transmission device, which is a terminal, as shown in FIG7 , including a memory 71 , a transceiver 72 , and a processor 73 :
[0226] 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:
[0227] Receiving, through the transceiver 72, a first non-access stratum NAS message sent by the 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;
[0228] 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 reported data determined according to the first NAS message;
[0229] The first identifier includes the identifier of the terminal and / or the group identifier.
[0230] The data transmission device provided by the embodiment of the present disclosure receives a first NAS message sent by a first core network device, where 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, where the second NAS message includes a message type and reported data determined according to the first NAS message; wherein the first identifier includes the identifier and / or group identifier of the terminal; and can support the implementation of: no need to establish a PDU session for the terminal (such as an Ambient IoT device), and the network does not need to establish and maintain a context for the terminal (such as an Ambient IoT device), while accurately transmitting data to the terminal (such as an Ambient IoT device).
[0231] Specifically, the transceiver 72 is used to receive and send data under the control of the processor 73.
[0232] In FIG7 , 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. The bus architecture may also link together various other circuits such as peripheral devices, 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, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. For different user devices, the user interface 74 may also be an interface capable of connecting external or internal devices as required, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
[0233] 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.
[0234] 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.
[0235] The processor calls the computer program stored in the memory to execute any of the methods provided by the embodiments of the present disclosure according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.
[0236] 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.
[0237] In the embodiment of the present disclosure, 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.
[0238] The requested data reporting method includes at least one of: single reporting, periodic reporting, and random reporting.
[0239] Furthermore, the operation also includes: determining data reporting based on the first identifier included in the first NAS message; 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 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.
[0240] 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.
[0241] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned 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.
[0242] The embodiment of the present disclosure further provides a data transmission device, which is a first core network device, as shown in FIG8 , including a memory 81 , a transceiver 82 , and a processor 83 :
[0243] 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:
[0244] Sending a first non-access stratum (NAS) message to the terminal through the transceiver 82, 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;
[0245] 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;
[0246] Receiving, through the transceiver 82, the subscription information of the terminal sent by the second core network device;
[0247] According to the contract information, the reported data is sent to the application server through the third core network device.
[0248] The data transmission device provided in the embodiment of the present disclosure sends a first 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 the requested data reporting methods; receives a second NAS message sent by the terminal, where the second NAS message includes a message type and reported data determined by the terminal based on the first NAS message; receives the contract information of the terminal sent by a second core network device; and sends the reported data to an application server through a third core network device based on the contract information; and can support the implementation of: no need to establish a PDU session for the terminal (such as an Ambient IoT device), and the network does not need to establish and maintain a context for the terminal (such as an Ambient IoT device), while accurately transmitting data for the terminal (such as an Ambient IoT device).
[0249] Specifically, the transceiver 82 is used to receive and send data under the control of the processor 83.
[0250] In FIG8 , 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. The bus architecture may also link together various other circuits such as peripheral devices, 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, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, or the like. 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.
[0251] 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.
[0252] 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.
[0253] In the embodiment of the present disclosure, 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.
[0254] The requested data reporting method includes at least one of: single reporting, periodic reporting, and random reporting.
[0255] In the embodiment of the present disclosure, the reported data includes an identifier or a group identifier of the terminal.
[0256] 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.
[0257] In the embodiment of the present disclosure, 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.
[0258] 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.
[0259] In the disclosed embodiment, 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).
[0260] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned first core network device 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.
[0261] The present disclosure also provides a data transmission device, which is applied to a terminal, as shown in FIG9 , and includes:
[0262] The first receiving unit 91 is configured to receive a first non-access stratum 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;
[0263] 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 reported data determined according to the first NAS message;
[0264] The first identifier includes the identifier of the terminal and / or the group identifier.
[0265] The data transmission device provided by the embodiment of the present disclosure receives a first non-access layer NAS message sent by a first core network device, where 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, where the second NAS message includes a message type and reported data determined according to the first NAS message; wherein the first identifier includes the identifier and / or group identifier of the terminal; and can support the implementation of: no need to establish a PDU session for the terminal (such as an Ambient IoT device), and the network does not need to establish and maintain a context for the terminal (such as an Ambient IoT device), while accurately transmitting data for the terminal (such as an Ambient IoT device).
[0266] 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.
[0267] In the embodiment of the present disclosure, 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.
[0268] The requested data reporting method includes at least one of: single reporting, periodic reporting, and random reporting.
[0269] Optionally, the data transmission device further includes: a first determination unit, used to determine data reporting based on the first identifier contained in the first NAS message; the first sending unit is specifically used to: send the second NAS message to the first core network device according to the requested data reporting method contained in the first NAS message; wherein the reported data in the second NAS message includes the identifier or group identifier of the terminal.
[0270] 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.
[0271] It should be noted here that the above-mentioned device provided by the embodiment of the present disclosure can implement all the method steps implemented by the above-mentioned terminal-side method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.
[0272] The present disclosure also provides a data transmission apparatus, which is applied to a first core network device, as shown in FIG10 , and includes:
[0273] The second sending unit 101 is configured to send a first non-access stratum 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;
[0274] 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;
[0275] The third receiving unit 103 is configured to receive the subscription information of the terminal sent by the second core network device;
[0276] The first processing unit 104 is configured to send the reported data to the application server through the third core network device according to the subscription information.
[0277] The data transmission device provided by the embodiment of the present disclosure sends 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 the requested data reporting methods; receives a second NAS message sent by the terminal, where the second NAS message includes a message type and reported data determined by the terminal based on the first NAS message; receives the contract information of the terminal sent by a second core network device; and sends the reported data to an application server through a third core network device based on the contract information; and can support the implementation of: no need to establish a PDU session for the terminal (such as an Ambient IoT device), and the network does not need to establish and maintain a context for the terminal (such as an Ambient IoT device), while accurately transmitting data for the terminal (such as an Ambient IoT device).
[0278] 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.
[0279] In the embodiment of the present disclosure, 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.
[0280] The requested data reporting method includes at least one of: single reporting, periodic reporting, and random reporting.
[0281] In the embodiment of the present disclosure, the reported data includes an identifier or a group identifier of the terminal.
[0282] 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.
[0283] In the disclosed embodiment, 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.
[0284] 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.
[0285] In the disclosed embodiment, 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).
[0286] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned first core network device 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.
[0287] It should be noted that the division of units in the embodiments of the present disclosure is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0288] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0289] An embodiment of the present disclosure also provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable a processor to execute the above-mentioned method on the terminal side or the first core network device side.
[0290] 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 disk, hard disk, magnetic tape, magneto-optical disk (MO)), etc.), optical storage (such as compact disk (CD), digital video disc (DVD), Blu-ray disc (BD), high-definition versatile disc (HVD), etc.), and semiconductor memory (such as read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), non-volatile memory (NAND FLASH), solid state drive (SSD)), etc.
[0291] 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.
[0292] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program code.
[0293] The present disclosure 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 disclosure. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the 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 produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0294] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0295] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0296] It should be noted that it should be understood that the division of the above modules is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, these modules can all be implemented in the form of software called by a processing element; or they can all be implemented in the form of hardware; or some modules can be implemented in the form of software called by a processing element, and some modules can be implemented in the form of hardware. For example, the determination module can be a separately established processing element, or it can be integrated into a chip of the above-mentioned device. In addition, it can also be stored in the memory of the above-mentioned device in the form of program code, and called by a processing element of the above-mentioned device to perform the functions of the above-mentioned determination module. The implementation of other modules is similar. In addition, these modules can all or partly be integrated together, or they can be implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed by the hardware integrated logic circuit in the processor element or by instructions in the form of software.
[0297] For example, each module, unit, sub-unit or sub-module may be one or more integrated circuits configured to implement the above method, such as one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs). For another example, when a module is implemented by scheduling program code through a processing element, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).
[0298] The terms "first," "second," and the like in the specification and claims of the present disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of the present disclosure described herein may be implemented in a sequence other than that illustrated or described herein. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units need not be limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to these processes, methods, products, or devices. In addition, the use of "and / or" in the specification and claims to indicate at least one of the connected objects, for example, A and / or B and / or C, means that seven situations are included: A alone, B alone, C alone, both A and B present, both B and C present, both A and C present, and all A, B, and C present. Similarly, the use of "at least one of A and B" in the specification and claims should be understood to mean "A alone, B alone, or both A and B present."
[0299] Obviously, those skilled in the art may make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is intended to include these modifications and variations.
Claims
1. A data transmission method, applied to a terminal, the method comprising: 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, wherein: 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, wherein: 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, wherein: 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, further comprising: 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, wherein: 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, the first NAS message and the second NAS message All messages are session management NAS messages.
7. A data transmission method, applied to a first core network device, the method comprising: 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, wherein: 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, wherein: 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, wherein: 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, wherein: The reported data includes the identifier or group identifier of the terminal.
12. The data transmission method according to claim 7, wherein: 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, wherein: 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, wherein: 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, the first NAS message and the second NAS message All messages are session management NAS messages.
15. The data transmission method according to claim 7, wherein: 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, the data transmission device comprising a memory, a transceiver, and a processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Receiving, by the transceiver, a first 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; in, The first identifier includes an identifier and / or a group identifier of the terminal.
17. The data transmission device according to claim 16, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, the data transmission device comprising a memory, a transceiver, and a processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Sending, 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, wherein: 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, wherein: 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, wherein: 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, wherein: The reported data includes the identifier or group identifier of the terminal.
27. The data transmission device according to claim 22, wherein: 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, wherein: 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, wherein: 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, wherein: 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, the data transmission device comprising: 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. The data transmission device according to claim 31, wherein: 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.
33. The data transmission device according to claim 31, wherein: 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.
34. The data transmission device according to claim 31, wherein: The requested data reporting method includes: At least one of single reporting, periodic reporting, and random reporting.
35. The data transmission device according to claim 31, further comprising: A first determining unit, configured to determine to report data according to a first identifier included in the first NAS message; The first sending unit is specifically configured to: 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.
36. The data transmission device according to claim 31, wherein: 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.
37. A data transmission device, applied to a first core network device, the data transmission device comprising: 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.
38. The data transmission device according to claim 37, wherein: 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.
39. The data transmission device according to claim 37, wherein: 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.
40. The data transmission device according to claim 37, wherein: The requested data reporting method includes: At least one of single reporting, periodic reporting, and random reporting.
41. The data transmission device according to claim 37, wherein: The reported data includes the identifier or group identifier of the terminal.
42. The data transmission device according to claim 37, wherein: 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.
43. The data transmission device according to claim 42, wherein: 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.
44. The data transmission device according to claim 37, wherein: 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.
45. The data transmission device according to claim 37, wherein: 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.
46. A non-transitory readable storage medium storing a computer program, wherein the computer program is used to cause a processor to execute the method according to any one of claims 1 to 15.
Citation Information
Patent Citations
Downlink small data transmission method and device
CN110213799A
Low power periodic and triggered location of a mobile device using early data transmission
CN112314021A
Equipment positioning method, system and device, communication equipment and storage medium
CN115428479A
Information transmission method and device
CN116033464A
Method and device for collecting terminal information in 5G network
CN116528278A