Communication method and device

Abstract

The present application relates to a communication method and device. The method comprises: a first node receiving first task information; the first node converting the first task information into second task information; and the first node sending the second task information. According to the embodiments of the present application, the executability of task information can be improved by means of converting the task information.

Description

Communication method and device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method and device. Background Art

[0002] With the development of Internet of Things (IoT) technology, IoT terminals are being used in a wide range of scenarios and are now proliferating in number. In ambient IoT (A-IoT) communication systems, A-IoT terminals can derive their energy from the surrounding environment. These terminals typically have relatively simple functions. Conventional terminals, such as those with installed applications, are difficult to control.

[0003] Summary of the Invention

[0004] Embodiments of the present application provide a communication method and device that can improve the executability of task information.

[0005] An embodiment of the present application provides a communication method, including:

[0006] The first node receives the first task information;

[0007] The first node converts the first task information into second task information;

[0008] The first node sends the second task information.

[0009] An embodiment of the present application provides a communication method, including:

[0010] The second node receives second task information, where the second task information is converted based on the first task information;

[0011] The second node converts the second task information into third task information;

[0012] The second node sends the third task information.

[0013] An embodiment of the present application provides a first communication device, including:

[0014] A receiving unit, configured to receive first task information;

[0015] a processing unit, configured to convert the first task information into second task information;

[0016] The sending unit is configured to send the second task information.

[0017] An embodiment of the present application provides a second communication device, including:

[0018] a receiving unit, configured to receive second task information, where the second task information is converted based on the first task information;

[0019] a processing unit, configured to convert the second task information into third task information;

[0020] The sending unit is configured to send the third task information.

[0021] An embodiment of the present application provides a communication device, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and execute the computer program stored in the memory so that the communication device performs the above-mentioned communication method.

[0022] An embodiment of the present application provides a chip for implementing the above-mentioned communication method.

[0023] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned communication method.

[0024] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which, when executed by a device, enables the device to execute the above-mentioned communication method.

[0025] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above-mentioned communication method.

[0026] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above-mentioned communication method.

[0027] In the embodiment of the present application, the executability of task information can be improved by converting task information. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0029] Figure 2A is a schematic diagram of the basic structure of the A-IoT communication system.

[0030] 2B-1 to 2B-4 are schematic diagrams of network topology structures.

[0031] FIG2C is a schematic structural diagram of a broadband receiver.

[0032] FIG2D is a schematic structural diagram of a narrowband receiver.

[0033] FIG3 is a schematic flowchart of a communication method according to an embodiment of the present application.

[0034] FIG4 is a schematic flowchart of a communication method according to another embodiment of the present application.

[0035] FIG5 is a schematic flowchart of a communication method according to another embodiment of the present application.

[0036] FIG6 is a schematic flowchart of a communication method according to an embodiment of the present application.

[0037] FIG7 is a schematic block diagram of a first communication device according to an embodiment of the present application.

[0038] FIG8 is a schematic block diagram of a second communication device according to an embodiment of the present application.

[0039] 9A and 9B are schematic flow charts based on the remote conversion method.

[0040] 10A and 10B are schematic flow charts based on the near-end conversion method.

[0041] FIG11 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0042] FIG12 is a schematic block diagram of a chip according to an embodiment of the present application.

[0043] FIG13 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0044] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0045] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), Fifth Generation (5G) system or other communication systems.

[0046] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0047] In one embodiment, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0048] In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0049] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0050] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0051] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0052] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0053] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0054] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in a WLAN, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0055] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0056] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0057] FIG1 exemplarily illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.

[0058] In one embodiment, the communication system 100 may further include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application.

[0059] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment can be an evolutionary base station (evolutional nodeB, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation Node B (gNodeB), etc. in a long-term evolution (LTE) system, a next-generation (mobile communication system) (nextradio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0060] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication device may include a network device and a terminal device having a communication function. The network device and the terminal device may be specific devices in the embodiments of the present application and will not be described in detail here. The communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0061] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0062] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0063] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0064] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0065] The rise of the Internet of Things (IoT) has posed new challenges to communication systems. IoT terminals are used in applications such as logistics, warehousing, factory automation, and animal husbandry. These IoT terminals only need to be able to intermittently communicate with the network or perform basic location tracking. Currently, even the simplest IoT terminals on the market, such as narrowband (NB)-IoT terminals used for coal and electricity metering, require batteries for power. Despite their low energy consumption, the batteries in these terminals deplete after only a few years. This requires extensive labor for battery replacement. Some industrial scenarios are too dangerous for manual operation. Battery-free IoT terminals have emerged as a solution. These battery-free IoT terminals are available in large quantities, are low-cost, and generally require no maintenance after installation. Radio Frequency Identification (RFID) terminals meet this need to some extent. However, the operation of RFID systems requires human intervention (for example, using a handheld reader). Moreover, since the wireless coverage range of a single RFID reader is limited (within 10 meters), it still takes a lot of manpower, material resources and time to take inventory of goods in a large supermarket, for example.

[0066] Transplanting communication systems like RFID into 3GPP cellular networks effectively solves coverage issues. This is because already deployed cellular networks, such as 4G and 5G, have achieved nationwide coverage, or at least coverage of major cities, in China, Europe, and the United States. The benefit of full coverage is that the communication and positioning process between IoT terminals and the network does not require human intervention, so it can operate 24 / 7 and is highly efficient, even in environments unsuitable for human intervention (such as wilderness, mines, and factories). In this way, aside from the initial need to associate the IoT terminal with a specific object, subsequent data reading, writing, and operation and maintenance can be performed simply through an app on a smartphone, which is very convenient and efficient.

[0067] Such a communication system is called an A-oT communication system or a zero-power communication system. A-IoT communication uses energy harvesting and backscattering communication technology. The A-IoT communication network consists of network equipment and A-IoT terminals (such as tag nodes), as shown in Figure 2A. The network equipment is used to send wireless power supply signals, downlink communication signals and receive backscattered signals from tag nodes or zero-power terminals to tag nodes or zero-power terminals. A basic tag node or zero-power terminal includes an energy harvesting module, a backscattering communication module and a low-power computing module. In addition, the tag node or zero-power terminal may also have a memory or sensor for storing some basic information (such as item identification, etc.) or obtaining sensor data such as ambient temperature and ambient humidity.

[0068] 3GPP's SA1 has already categorized and discussed the use cases that such a system can serve, encompassing four major categories: inventory, sensors, tracking, and commands. Inventory involves checking for missing items and replenishing missing items as goods enter and leave the warehouse. Common sensors include temperature, pressure, and humidity, used in industrial, agricultural, and smart city applications. This information is uploaded to a third-party app through the A-IoT system for monitoring and management. Tracking generally refers to obtaining the approximate location of an object at irregular intervals, such as allowing users to track the location of their parcels in near real-time via their smartphones. Commands, on the other hand, involve operating a servo mechanism through the A-IoT communication system. These servos are connected to A-IoT terminals. For example, during a break at the office, you might water your backyard plants using a mobile app, with the watering servo mechanism connected to an A-IoT terminal.

[0069] 3GPP has also studied these SA1 use cases from a wireless perspective, proposing four network topologies, three terminal types, and design functional and performance targets. The following are examples of how Ambient IoT data or signaling can be transmitted within these network topologies. As shown in Figure 2B-1, a tag node (e.g., an Ambient IoT device) communicates directly with a base station (BS). As shown in Figure 2B-2, the tag communicates directly with an intermediate node (e.g., a smartphone). The communication link between the intermediate node and the base station can be established using existing communication systems, such as 5G NR. As shown in Figure 2B-3, the tag's uplink connects to the base station, and its downlink connects to an assisting node. The communication link between the assisting node and the base station can be established using existing communication systems, such as 5G NR. As shown in Figure 2B-4, the tag communicates directly with a user end (UE).

[0070] A-IoT terminals (tags) derive their energy from the surrounding environment, such as radio waves (RF), solar energy, thermal energy, mechanical vibration, wind energy, and so on. In the A-IoT system currently being researched by 3GPP, terminals are primarily categorized into three types: A, B, and C. Type A and B terminals can only communicate by reflecting and modulating received radio waves, a communication method known as backscattering. This means they cannot actively transmit radio signals, and their power consumption ranges from 1 to 10 microwatts (μW). Type A terminals have the lowest transmit power and hardware complexity, roughly comparable to RFID terminals. Type B terminals have slightly more complex hardware, such as signal amplification devices and certain energy storage components, resulting in a longer communication range than type A terminals. Type C terminals have the ability to actively transmit radio waves, with a transmit power of approximately 1 to 10 milliwatts (mW), and can store a certain amount of energy. All three types of terminals can harvest energy from the environment, enabling them to operate continuously for several years or even over 10 years. To conserve energy, type A and B terminals typically remain dormant until the network triggers a communication process. It will only wake up and work when stimulated by the network's wireless signal.

[0071] Tag receivers can be divided into two categories:

[0072] Receiver Type 1: Wideband Receiver. This type of receiver, also known as an RF receiver, uses an RF bandpass filter (BPF) to obtain signals within the bandwidth to be received, then performs envelope detection and subsequent baseband (BB) processing. This architecture has the simplest structure, and its power consumption can be as low as several uW or even lower. However, due to the poor accuracy of the RF bandpass filter, even when the target signal occupies a narrow bandwidth, the receiver often receives signals within a wider bandwidth. Therefore, the reception process introduces more noise and interference, resulting in poor receiver performance, that is, poor sensitivity. Figure 2C is a structural diagram of a wideband receiver. For example, a broadband receiver may include a matching network, a radio frequency bandpass filter (RF BPF), an RF low-noise amplifier (LNA), an RF envelope detector, a BB amplifier (AMP), a BB low-pass filter (LPF), a one-bit or multi-bit analog to digital converter (ADC), and digital BB processing.

[0073] Receiver Type 2: Narrowband Receiver. Examples include IF receivers or zero-IF receivers. During signal reception, in addition to using an RF bandpass filter to obtain signals within the intended reception bandwidth, the RF signal is downconverted and the baseband signal is further filtered using a low-pass filter to eliminate noise and interference. Therefore, this receiver has a narrow reception bandwidth and high reception performance, i.e., high receiver sensitivity. However, this receiver requires a local oscillator (LO). Even the recommended LO consumes 100uW or more, resulting in relatively high power consumption. However, due to its very low absolute power consumption, it is still suitable for use in zero-power devices. Figure 2D shows the structure of an IF receiver. This IF receiver may include a matching network, RF BPF, RF LNA, mixer, LO, IF amplifier, IF envelope detector, back-beam amplifier, back-beam LPF, one or more ADCs, and digital back-beam processing.

[0074] The above-mentioned Type A terminal usually adopts a broadband receiver, the Type C terminal usually adopts a narrowband receiver, and the Type B terminal may adopt one or both types of receivers.

[0075] In 3GPP broadband systems, such as LTE and NR, the primary terminal form factor can be a smart terminal or smart wearable electronic product. These electronic products typically include complete application software (apps), an internet communication protocol stack (such as the Transmission Control Protocol / Internet Protocol (TCP / IP)), and a 3GPP communication module for sending and receiving IP data blocks. For A-IoT systems, the hardware of the tag is unable to run these complex application software, both in terms of cost (which is directly related to complexity and computing power) and energy storage.

[0076] In an RFID system, once a point-to-point communication link is established between a tag and a reader, the reader's main operation on the tag is to read and write the tag's logical memory, while the interpretation of the read and write content is completed by the reader or the application software on the server connected to the reader.

[0077] For AIoT systems, some use cases are similar to RFID, such as completing inventory work. However, AIoT needs to support more use cases, including sensor, tracking, and command use cases. Among them, the sensor use case needs to complete certain measurement tasks and needs to report the measured data to the network in some way. The tracking use case means that the network needs to know the approximate location of the tag in a certain way. When the location accuracy requirements are relatively high, such as when you need to know which corner of the room a tag is in, the tag may need to send a radio signal for positioning purposes. The command use case means that the network needs to send certain content to the tag so that it can further control certain servo mechanisms through the tag, such as air conditioners that control the temperature.

[0078] In these new use cases, for example, if the tag is a communication module on a sensor, the sensor needs to know what measurements the network requires it to make and how to report the results. However, these tasks and results cannot be directly completed at the app layer and must be converted within the communication system.

[0079] FIG3 is a schematic flow chart of a communication method 300 according to an embodiment of the present application. The method can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.

[0080] S310, the first node receives first task information;

[0081] S320: The first node converts the first task information into second task information;

[0082] S330: The first node sends the second task information.

[0083] In an embodiment of the present application, some task information of a sending node needs to be converted before it can be executed by a receiving node. For example, the sending node may include a mobile terminal, a server, etc., and an application software (App) may be installed in the mobile terminal or the server. The receiving node may include some low-power terminals or zero-power terminals with simple functions. The low-power terminals or zero-power terminals are mainly used to perform simple operations such as receiving, sending, reading, writing, comparing, and deleting based on the received task information. The first node may be a conversion node in a communication system. The first node may receive first task information from the sending node and convert the first task information according to the relevant protocol to obtain second task information. The task parameters in the first task information and the second task information may be the same or similar, but the information formats of the two may conform to different protocols. In one case, the second task information may conform to a protocol executable by the receiving node. In another case, the second task information conforms to the protocol of the intermediate node and needs to be converted again by the intermediate node before it conforms to a protocol executable by the receiving node. In some examples, the first task information and the second task information may be information about A-IoT tasks. By converting the task information, the executability of the task information can be improved.

[0084] In one embodiment, the first task information and / or the second task information are used to indicate the task parameters that the target node needs to execute. In an embodiment of the present application, the sending node may be a source node, and the receiving node may be a target node. The first task information sent by the source node, such as the application node, may explicitly or implicitly indicate the task parameters that the target node needs to execute. The first node may convert the first task information from the source node into the second task information. The format of the second task information is different from that of the first task information. For example, the first task information is application layer information, and the second task information is protocol layer information. For another example, the first task information is application layer information, and the second task information is non-access layer information. The second task information may also explicitly or implicitly indicate the task parameters that the target node needs to execute.

[0085] In one embodiment, the task parameters that the target node needs to execute include at least one of the following:

[0086] The content of the task;

[0087] The duration of the task;

[0088] Method for reporting execution results;

[0089] Control parameters of execution results;

[0090] The scope of the task execution.

[0091] In the embodiments of the present application, the content of the task can be diverse and may vary depending on the scenario in which the target node is set. For example, if the target node is a switch control node set on a light, the task content may be turning the light on or off. If the target node is a control node set on a temperature sensor or humidity sensor, the task content may be measuring temperature or humidity. If the target node is an inventory counting node set on a product, the task content may be reporting the product identification.

[0092] In the embodiment of the present application, if the task is triggered immediately, there may be no period. If the task is executed periodically, the period of the task can be set based on the scenario set for the target node, the content of the task, etc. For example, if the target node is a control node set on a temperature sensor, the content of the task is to measure the temperature, and the period of the task is 1 hour, it means that the target node is required to measure and report the ambient temperature once every hour.

[0093] In the embodiments of the present application, the reporting method for execution results can be flexibly configured based on demand. Reporting can be performed immediately after measurement. Reporting can be performed periodically, for example, once a day or once every hour. Reporting can be performed when certain conditions are met, such as when the temperature is greater than 35 degrees Celsius. The control parameters for execution results may include thresholds for result reporting, threshold ranges, etc. The scope of task execution may include the location range of the target node for executing the task, etc.

[0094] In one embodiment, the target node includes a tag node. For example, in an A-IoT system, the target node may be a tag node.

[0095] Figure 4 is a schematic flow chart of a communication method 400 according to another embodiment of the present application. The method 400 may include one or more features of the above-mentioned method. In one embodiment, the first node is a conversion node, and S310 includes: the conversion node receives the first task information from the application node, and the first task information is application layer information. The conversion node can receive the first task information of the application layer from the source node, such as the application node. The first task information can be transmitted directly between the first node and the source node, or the first task information can be transmitted through the Internet or other means.

[0096] In one embodiment, the conversion node may be located on the reader node, or may be independently provided with the reader node.

[0097] In one embodiment, S330 includes: the conversion node sending the second task information to the target node, where the second task information is non-access stratum information obtained by the conversion node by converting the first task information from the application layer information. In this embodiment of the present application, after the conversion node converts the first task information of the application layer into the second task information of the non-access stratum, it can directly send the second task information of the non-access stratum to the target node, or it can send the second task information of the non-access stratum to the target node through another node, such as a reader node (or card reader node). The second task information can be transmitted between the conversion node (or reader node) and the target node via L1 / L2 messaging.

[0098] In one embodiment, the method further comprises:

[0099] S410: The first node receives a first execution result, where the first execution result is a result obtained by the target node executing the task based on the second task information;

[0100] S420: The first node converts the first execution result into a second execution result;

[0101] S430: The first node sends the second execution result.

[0102] In an embodiment of the present application, after the target node receives the second task information of the non-access layer, it can execute the task based on the second task information to obtain a first execution result, and send it to the first node. The first node can receive the first execution result directly from the target node, or receive the first execution result from the target node through a reader node. The first execution result can be transmitted between the conversion node (or reader node) and the target node via L1 / L2 messages. The first node can convert the first execution result into a second execution result according to the protocol. The first execution result and the second task information can conform to the same protocol, and the second execution result and the first task information can conform to the same protocol. Then, the first node can send the second execution result to the source node. The task execution result can be transmitted directly between the first node and the source node, or the task execution result can be transmitted through the Internet or other means.

[0103] In one embodiment, the first node receiving the first execution result includes: the conversion node receiving the first execution result from the target node, where the first execution result is non-access stratum information. In this embodiment of the present application, after the target node executes the second task information of the non-access stratum and obtains the first execution result of the non-access stratum, it can send the first execution result to the conversion node. The conversion node can convert the first execution result of the non-access stratum into the second execution result of the application layer.

[0104] In one embodiment, the first node sending the second execution result includes: the conversion node sending the second execution result to the application node via a communication network, where the second execution result is application layer information obtained by the conversion node by converting the first execution result from non-access stratum information. In this embodiment of the present application, the conversion node may send the second application layer execution result to the application node. The application node may display the second execution result on a display page of the application.

[0105] In one embodiment, application layer information is transmitted between the conversion node and the application node via TCP / IP, and non-access layer information is transmitted between the conversion node and the target node via L1 / L2 messages. For example, messages can be transmitted between the conversion node and the application node via a 3GPP network based on TCP / IP. The application node can send first task information of the application layer to the conversion node via the 3GPP network based on TCP / IP. After the conversion node converts the first task information to obtain second task information of the non-access layer, it can send the second task message to the target node via an L1 / L2 message. After the target node executes the second task information to obtain a first execution result of the non-access layer, it can send the first execution result to the conversion node via an L1 / L2 message. After the conversion node converts the first execution result to obtain a second execution result of the application layer, it can send the second conversion result to the application node via the 3GPP network based on TCP / IP.

[0106] Figure 5 is a schematic flow chart of a communication method 500 according to another embodiment of the present application. The method 500 may include one or more features of the above method. In one embodiment, the first node is a conversion node, and S310 includes: the conversion node receives the first task information from the application node, and the first task information is application layer information. The conversion node can receive the first task information of the application layer from the source node, such as the application node. The first task information can be transmitted directly between the first node and the source node, or the first task information can be transmitted through the Internet or other means.

[0107] In one embodiment, S330 includes: the conversion node sends the second task information to the core network node, the second task information is the protocol layer information obtained by the conversion node converting the first task information from the application layer information, and the core network node converts the second task information from the protocol layer information into non-access layer information and sends the non-access layer information to the target node through the reader node. In an embodiment of the present application, after the conversion node converts the first task information of the application layer into the second task information of the protocol layer, it can send the second task information of the protocol layer to an intermediate node such as a core network node. The core network node can convert the second task information into the third task information of the non-access layer. In addition, the core network node can send the third task information of the non-access layer directly to the target node, or send the third task information of the non-access layer to the target node through other nodes such as a reader node (or called a card reader node). Among them, the third task information can be transmitted between the reader node and the target node through L1 / L2 messages.

[0108] In one embodiment, the method further comprises:

[0109] S510: The first node receives a second execution result, where the second execution result is converted based on the first execution result, and the first execution result is a result obtained by the target node executing the task based on the second task information;

[0110] S520: The first node converts the second execution result into a third execution result;

[0111] S530: The first node sends the third execution result.

[0112] In an embodiment of the present application, the target node may execute the third task information to obtain a first execution result at the non-access layer. The target node may send the first execution result to the reader node via an L1 / L2 message. The reader node may send the first execution result to the core network node via NGAP. The core network node may convert the first execution result into a second execution result at the protocol layer and send the second execution result to the first node, such as a conversion node. After receiving the second execution result, the conversion node may convert it into a third execution result and send it to the application node.

[0113] In one embodiment, the first node receives the second execution result, including:

[0114] The conversion node receives the second execution result from the core network node, where the second execution result is protocol layer information obtained by the core network node converting the first execution result from non-access layer information.

[0115] In one embodiment, the first node sending the third execution result includes:

[0116] The conversion node sends the third execution result to the application node, where the third execution result is application layer information obtained by the conversion node by converting the second execution result from the protocol layer information.

[0117] In an embodiment of the present application, after receiving the second execution result of the protocol layer from the core network node based on XF (X functionality), the conversion node can convert the second execution result into a third execution result of the application layer and then send it to the application node.

[0118] In one embodiment, the conversion node and the core network node exchange information using a reference point based on a service architecture, which is a signaling exchange method between most nodes in the 5G core.

[0119] FIG6 is a schematic flow chart of a communication method 600 according to an embodiment of the present application. The method can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.

[0120] S610: The second node receives second task information, where the second task information is converted based on the first task information.

[0121] S620: The second node converts the second task information into third task information;

[0122] S630: The second node sends the third task information.

[0123] In an embodiment of the present application, the first node may convert the first task information of the application layer into the second task information of the protocol layer and send it to the second node. The second node may convert the second task information into the third task information executable by the target node and send it to the target node.

[0124] In one embodiment, at least one of the first task information, the second task information, and the third task information is used to indicate task parameters that the target node needs to execute. In this embodiment of the present application, the task parameters in the first task information, the second task information, and the third task information can be the same or similar, but the information formats of the three may conform to different protocols. For example, the first task information is application layer information, the second task information is protocol layer information, and the third task information is non-access stratum information.

[0125] In one embodiment, the task parameters that the target node needs to execute include at least one of the following:

[0126] The content of the task;

[0127] The duration of the task;

[0128] Method for reporting execution results;

[0129] Control parameters of execution results;

[0130] The scope of the task execution.

[0131] In one embodiment, the target node includes a tag node.

[0132] In one implementation, the second node is a core network node.

[0133] In one embodiment, the second node receives the second task information, including: the core network node receives the second task information from the conversion node, the second task information is the protocol layer information obtained by the conversion node based on the first task information from the application node, and the first task information is the application layer information.

[0134] In one embodiment, the second node sends the third task information, including: the core network node sends the third task information to the target node through the reader node, and the third task information is non-access layer information.

[0135] In an embodiment of the present application, after receiving the second task information of the protocol layer from the conversion node, the core network node may convert the second task information into third task information of the non-access layer and send it to the target node.

[0136] In one embodiment, the method further comprises:

[0137] The second node receives the first execution result;

[0138] The second node converts the first execution result into a second execution result;

[0139] The second node sends the second execution result.

[0140] In an embodiment of the present application, after the target node executes the third task information to obtain a first execution result at the non-access layer, the target node may send the first execution result directly or through a reader node to the core network node. The core network node may convert the received first execution result into a second execution result at the protocol layer and send the result to the first node, such as a conversion node.

[0141] In one embodiment, the second node is a core network node, and receiving the first execution result by the second node includes: the core network node receiving the first execution result from the target node via the reader node, where the first execution result is non-access stratum information. In this embodiment of the present application, after receiving the first execution result from the target node, the reader node may forward it to the core network node.

[0142] In one embodiment, the second node sending the second execution result includes: the core network node sending the second execution result to a conversion node, where the second execution result is protocol layer information obtained by the core network node converting the first execution result from non-access stratum information; the conversion node converting the second execution result from protocol layer information into application layer information and sending the application layer information to the application node. In this embodiment of the present application, after receiving the first execution result at the non-access stratum layer, the core network node may convert it into a second execution result at the protocol layer and send the second execution result to the conversion node.

[0143] In one embodiment, the conversion node and the core network node exchange information using a reference point based on a service architecture.

[0144] In one embodiment, the core network node and the reader node transmit non-access layer information based on NGAP, and the reader node and the target node transmit non-access layer information through L1 / L2 messages. In an embodiment of the present application, the core network node can send the second task information to the reader node through NGAP. After converting the second task information into the third task information of the non-access layer, the third task information can be sent to the target node through L1 / L2 messages. After the target node executes the third task information, it can obtain the first execution result of the non-access layer and send it directly or indirectly to the core network node. For example, the target node can first send the first execution result to the reader node using L1 / L2 messages. The reader node sends the first execution result to the core network node based on NGAP. The core network node can convert the received first execution result into a second execution result of the protocol layer, and send it to the conversion node based on XF. The conversion node can convert the second execution result into a third execution result of the application layer and send it to the application node.

[0145] For a specific example of the second node executing the communication method 600 in this embodiment, reference may be made to the relevant descriptions about the core network node in the above communication methods 300, 400, and 500, which will not be repeated here for the sake of brevity.

[0146] FIG7 is a schematic block diagram of a first communication device 700 according to an embodiment of the present application. The first communication device 700 may include:

[0147] Receiving unit 701, configured to receive first task information;

[0148] A processing unit 702 is configured to convert the first task information into second task information;

[0149] The sending unit 703 is configured to send the second task information.

[0150] In one embodiment, the first task information and / or the second task information is used to indicate task parameters that the target node needs to execute.

[0151] In one embodiment, the task parameters that the target node needs to execute include at least one of the following:

[0152] The content of the task;

[0153] The duration of the task;

[0154] Method for reporting execution results;

[0155] Control parameters of execution results;

[0156] The scope of the task execution.

[0157] In one embodiment, the target node includes a tag node.

[0158] In one implementation, the first communication device is a conversion node, and the receiving unit 701 is further configured to receive the first task information from an application node, where the first task information is application layer information.

[0159] In one embodiment, the sending unit 703 is further configured to send the second task information to the target node, where the second task information is non-access stratum information obtained by the conversion node converting the first task information from application layer information.

[0160] In one embodiment, the receiving unit 701 is also used to receive a first execution result, which is the result obtained by the target node executing the task based on the second task information; the processing unit 702 is also used to convert the first execution result into a second execution result; and the sending unit is also used to send the second execution result.

[0161] In one implementation, the first communication device is a conversion node, and the receiving unit 701 is further configured to receive the first execution result from the target node, where the first execution result is non-access stratum information.

[0162] In one embodiment, the first communication device is a conversion node, and the sending unit 703 is further used to send the second execution result to the application node through the communication network. The second execution result is application layer information obtained by the conversion node by converting the first execution result from non-access layer information.

[0163] In one embodiment, the conversion node and the application node transmit application layer information via TCP / IP, and the conversion node and the target node transmit non-access layer information via L1 / L2 messages.

[0164] In one embodiment, the conversion node is located on the reader node.

[0165] In one embodiment, the first communication device is a conversion node, and the sending unit 703 is also used to send the second task information to the core network node. The second task information is the protocol layer information obtained by the conversion node by converting the first task information from the application layer information. The core network node converts the second task information from the protocol layer information into non-access layer information and sends the non-access layer information to the target node through the reader node.

[0166] In one embodiment, the receiving unit 701 is also used to receive a second execution result, where the second execution result is obtained based on the conversion of the first execution result, and the first execution result is the result obtained by the target node executing the task based on the second task information; the processing unit 702 is also used to convert the second execution result into a third execution result; and the sending unit 703 is also used to send the third execution result.

[0167] In one embodiment, the first communication device is a conversion node, and the receiving unit 701 is further used to receive the second execution result from the core network node, where the second execution result is protocol layer information obtained by the core network node converting the first execution result from non-access layer information.

[0168] In one embodiment, the first communication device is a conversion node, and the sending unit 703 is further configured to send the third execution result to the application node. The third execution result is application layer information obtained by the conversion node by converting the second execution result from protocol layer information.

[0169] In one embodiment, the conversion node and the core network node exchange information using a reference point based on a service architecture.

[0170] FIG8 is a schematic block diagram of a second communication device 800 according to an embodiment of the present application. The device 800 may include:

[0171] The receiving unit 801 is configured to receive second task information, where the second task information is converted based on the first task information;

[0172] A processing unit 802 is configured to convert the second task information into third task information;

[0173] The sending unit 803 is configured to send the third task information.

[0174] In one embodiment, at least one of the first task information, the second task information, and the third task information is used to indicate task parameters that the target node needs to execute.

[0175] In one embodiment, the task parameters that the target node needs to execute include at least one of the following:

[0176] The content of the task;

[0177] The duration of the task;

[0178] Method for reporting execution results;

[0179] Control parameters of execution results;

[0180] The scope of the task execution.

[0181] In one embodiment, the target node includes a tag node.

[0182] In one embodiment, the second communication device is a core network node, and the receiving unit 801 is also used to receive the second task information from the conversion node. The second task information is protocol layer information obtained by the conversion node based on the first task information from the application node. The first task information is application layer information.

[0183] In one implementation, the second communication device is a core network node, and the sending unit 803 is further configured to send the third task information to the target node through the reader node, where the third task information is non-access layer information.

[0184] In one embodiment, the receiving unit 801 is further configured to receive a first execution result; the processing unit 802 is further configured to convert the first execution result into a second execution result; and the sending unit 803 is further configured to send the second execution result.

[0185] In one embodiment, the second communication device is a core network node, and the receiving unit 801 is further configured to receive the first execution result from the target node through a reader node, where the first execution result is non-access stratum information.

[0186] In one embodiment, the second communication device is a core network node, and the sending unit 803 is also used to send the second execution result to the conversion node. The second execution result is the protocol layer information obtained by the core network node by converting the first execution result from the non-access layer information. The conversion node converts the second execution result from the protocol layer information to application layer information and sends the application layer information to the application node.

[0187] In one embodiment, the conversion node and the core network node exchange information using a reference point based on a service architecture.

[0188] In one embodiment, the core network node and the reader node transmit non-access stratum information based on NGAP, and the reader node and the target node transmit non-access stratum information through L1 / L2 messages.

[0189] The communication devices 700 and 800 of the embodiments of the present application can implement the corresponding functions of the first node and the second node in the aforementioned method embodiments. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the communication devices 700 and 800 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the communication devices 700 and 800 of the application embodiments can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0190] In one application scenario, a task assignment and / or data reporting method can be introduced into the AIoT system, which may include one or more of the following:

[0191] 1. Introduce a bidirectional information conversion logical node (referred to as a conversion node) to convert information between the Internet App and the standard protocol supported by the tag.

[0192] 2. The conversion node can be located between the AIoTApp (application node) and the core network (core network node). The conversion node first sends the converted information to the core network, and then the core network and the tag establish a logical dialogue process.

[0193] 3. Information exchange between the conversion node and the core network is based on reference points under the business architecture.

[0194] 4. The conversion node is located between the core network and the tag. In this case, a dialogue process is established between the conversion node and the tag.

[0195] 5. The conversion node can be located on a reader node such as a card reader. The card reader can be a UE or a base station.

[0196] 6. For inventory services, in the first approach, downlink tasks from the core network can be issued via a protocol between the core network and the card reader, such as NGAP. Upon receiving the task, the card reader triggers the inventory process via an L2 / L1 message. Uplink data can be sent to the core network via NAS layer messages, and then to the third-party app via a conversion node.

[0197] 7. For inventory management, in the second method, after receiving the task from the App layer, the card reader triggers the inventory process through L2 / L1 messages. The uplink data is sent to the card reader through NAS layer messages, and then to the third-party App.

[0198] 8. The task must at least include executable content.

[0199] 9. The task may also include but is not limited to the task cycle, the reporting control parameters of the execution results (such as the cycle, etc.), and the scope of task execution (such as the scope of the card reader, the scope of the tag node, etc.).

[0200] Example 1: Transformer-based approach

[0201] As shown in Figures 9A and 9B, assume that there is an intermediate conversion node between the node where the third-party AIoT app is located and the 3GPP core network used for the AIoT system. The function of this conversion node includes converting application layer information and protocol layer information (XF) between the AIoT app and the 3GPP AIoT core network node.

[0202] In the downlink direction, for example, the AIoT App sends a task to the tag node. This task is first sent to the Transformer node in Figure 9A. This node converts the information of the App layer into information that can be communicated between XF functional nodes. The core network node then converts the information described by the XF protocol into NAS information supported by the tag node and end-to-end communication with the core network. Or the end point of this task is the core network, and then the core network notifies the card reader through the NGAP protocol to perform related operations, such as inventory services.

[0203] After the tag node performs the task according to the received information, if there is information to be reported, it can follow the reverse direction of the above information conversion path and finally convert and transmit the information to the node where the AIoT App is located.

[0204] Example 2: Transformer-based method

[0205] As shown in Figures 10A and 10B, in this solution, the node that directly communicates with the tag node (such as a smartphone or base station) can have a complete AIoT app application software. This node can be a card reader (which can be understood as a near-end conversion node), responsible for internal information conversion between the AIoT app layer and the higher-level protocol (such as NAS) between this node and the tag node. For example, in the downlink direction, the app-layer task is directly converted into NAS information, and the card reader then sends this NAS information to the tag node. After executing the task description, the tag node converts the information to be reported into NAS information and sends it to the card reader. The card reader then converts this information internally and sends it to the node where the remote AIoT app is located via the AIoT app. The task endpoint can also be a card reader. In this case, in the downlink direction, after interpreting the task content and other task parameters, the card reader completes the task through the L2 / L1 protocol. For example, for an inventory task, the card reader triggers the tag to read the information to be counted via an L2 message, which is then sent to the card reader via a NAS layer message. The card reader converts the received information into AIoT app information and communicates with a third-party server.

[0206] Example 3: Task Description

[0207] The tasks involved in Example 1 and Example 2 may include the following parameters:

[0208] (1) Task execution cycle (optional)

[0209] (2) Specific content of the task

[0210] (3) The reporting method and control parameters of the execution results, such as cycle, threshold, etc. (optional)

[0211] (4) Scope of task execution (optional)

[0212] Table 1 below shows an example of a task description. If there is a space before the first semicolon in the task description for Task 1, Task 2, Task 3, and Task 6, it means there is no period parameter and the task is executed once.

[0213] Table 1

[0214] In the two AIoT task delivery methods in the above examples, third-party users of the AIoT system can communicate tasks and report data to each other through the Internet and tag nodes (tags) that cannot directly access the Internet.

[0215] Figure 11 is a schematic structural diagram of a communication device 1100 according to an embodiment of the present application. The communication device 1100 includes a processor 1110, which can call and execute a computer program from a memory to enable the communication device 1100 to implement the method in the embodiment of the present application.

[0216] In one embodiment, the communication device 1100 may further include a memory 1120. The processor 1110 may call and execute a computer program from the memory 1120 to enable the communication device 1100 to implement the method in the embodiment of the present application.

[0217] The memory 1120 may be a separate device independent of the processor 1110 , or may be integrated into the processor 1110 .

[0218] In one embodiment, the communication device 1100 may further include a transceiver 1130 , and the processor 1110 may control the transceiver 1130 to communicate with other devices. Specifically, the transceiver 1130 may send information or data to other devices, or receive information or data sent by other devices.

[0219] The transceiver 1130 may include a transmitter and a receiver. The transceiver 1130 may further include an antenna, and the number of antennas may be one or more.

[0220] In one embodiment, the communication device 1100 may be the first communication device or the second communication device of the embodiment of the present application, and the communication device 1100 may implement the corresponding processes implemented by the first communication device or the second communication device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0221] 12 is a schematic structural diagram of a chip 1200 according to an embodiment of the present application. The chip 1200 includes a processor 1210, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0222] In one embodiment, the chip 1200 may further include a memory 1220. The processor 1210 may call and execute a computer program from the memory 1220 to implement the method executed by the first communication device or the second communication device in the embodiment of the present application.

[0223] The memory 1220 may be a separate device independent of the processor 1210 , or may be integrated into the processor 1210 .

[0224] In one embodiment, the chip 1200 may further include an input interface 1230. The processor 1210 may control the input interface 1230 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0225] In one embodiment, the chip 1200 may further include an output interface 1240. The processor 1210 may control the output interface 1240 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0226] In one embodiment, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0227] In one embodiment, the chip can be applied to the first communication device or the second communication device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the first communication device or the second communication device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0228] The chip used in the first communication device or the second communication device may be the same chip or different chips.

[0229] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0230] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0231] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).

[0232] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0233] FIG13 is a schematic block diagram of a communication system 1300 according to an embodiment of the present application. The communication system 1300 includes a first communication device 1310 and a second communication device 1320 .

[0234] The first communication device 1310 may be a first node, configured to receive first task information; convert the first task information into second task information; and send the second task information.

[0235] In one implementation, the second communication device 1320 may be a second node configured to receive second task information; convert the second task information into third task information; and send the third task information.

[0236] The first communication device 1310 may be used to implement the corresponding functions implemented by the conversion node in the above method, and the second communication device 1320 may be used to implement the corresponding functions implemented by the core network node in the above method.

[0237] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0238] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0239] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0240] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A communication method, comprising: A first node receives first task information; The first node converts the first task information into second task information; The first node sends the second task information.

2. The method according to claim 1, wherein, The first task information and / or the second task information is used to indicate task parameters that a target node needs to execute.

3. The method according to claim 2, wherein, The task parameters that the target node needs to execute include at least one of the following: The content of the task; The period of the task; The reporting method of the execution result; The control parameters of the execution result; The scope of task execution.

4. The method according to claim 2 or 3, wherein, The target node includes a tag node.

5. The method according to any one of claims 2 to 4, wherein, The first node is a conversion node. The first node receives the first task information, including: The conversion node receives the first task information from an application node, and the first task information is application layer information.

6. The method according to claim 5, wherein, The first node sends the second task information, including: The conversion node sends the second task information to the target node, and the second task information is non-access stratum information obtained by the conversion node converting the first task information from application layer information.

7. The method according to claim 5 or 6, wherein, The method further includes: The first node receives a first execution result, and the first execution result is a result obtained by the target node executing a task based on the second task information; The first node converts the first execution result into a second execution result; The first node sends the second execution result.

8. The method according to claim 7, wherein, The first node receives the first execution result, including: The conversion node receives the first execution result from the target node, and the first execution result is non-access stratum information.

9. The method according to claim 8, wherein, The first node sends the second execution result, including: The conversion node sends the second execution result to the application node through a communication network, and the second execution result is application layer information obtained by the conversion node converting the first execution result from non-access stratum information.

10. The method according to claim 5, 6 or 8, wherein, The application layer information is transmitted between the conversion node and the application node through TCP / IP, and the non-access stratum information is transmitted between the conversion node and the target node through L1 / L2 messages.

11. The method according to claim 5, 6, 8, 9 or 10, wherein, The conversion node is located on a reader node.

12. The method according to claim 5, wherein, The first node sends the second task information, including: The conversion node sends the second task information to the core network node. The second task information is protocol layer information obtained by the conversion node from converting the first task information from application layer information. The core network node converts the second task information from protocol layer information into non-access stratum information and sends the non-access stratum information to the target node through the reader node.

13. The method according to claim 12, wherein, the method further includes: The first node receives a second execution result, which is obtained by converting a first execution result, and the first execution result is the result obtained by the target node executing a task based on the second task information; The first node converts the second execution result into a third execution result; The first node sends the third execution result.

14. The method according to claim 13, wherein, the first node receiving the second execution result includes: The conversion node receives the second execution result from the core network node, and the second execution result is protocol layer information obtained by the core network node from converting the first execution result from non-access stratum information.

15. The method according to claim 14, wherein, the first node sending the third execution result includes: The conversion node sends the third execution result to the application node, and the third execution result is application layer information obtained by the conversion node from converting the second execution result from protocol layer information.

16. The method according to any one of claims 13 to 15, wherein, The conversion node and the core network node perform information interaction in a manner based on the reference point under the service architecture.

17. A communication method, including: The second node receives second task information, which is obtained by converting first task information; The second node converts the second task information into third task information; The second node sends the third task information.

18. The method according to claim 17, wherein, At least one of the first task information, the second task information, and the third task information is used to indicate the task parameters that the target node needs to execute.

19. The method according to claim 18, wherein, The task parameters that the target node needs to execute include at least one of the following: The content of the task; The period of the task; The reporting method of the execution result; The control parameters of the execution result; The scope of task execution.

20. The method according to claim 18 or 19, wherein, The target node includes a tag node.

21. The method according to any one of claims 17 to 20, wherein, The second node is a core network node, and the second node receiving the second task information includes: The core network node receives the second task information from the conversion node, and the second task information is protocol layer information obtained by the conversion node from converting the first task information from the application node, and the first task information is application layer information.

22. The method according to claim 21, wherein, the second node sending the third task information includes: The core network node sends the third task information to the target node through the reader node, and the third task information is non-access stratum information.

23. The method according to any one of claims 17 to 22, wherein, the method further includes: the second node receives a first execution result; the second node converts the first execution result into a second execution result; the second node sends the second execution result.

24. The method according to claim 23, wherein, the second node is a core network node, and the second node receives a first execution result, including: the core network node receives the first execution result from the target node through the reader node, and the first execution result is non-access stratum information.

25. The method according to claim 24, wherein, the second node sends the second execution result, including: the core network node sends the second execution result to the conversion node, and the second execution result is protocol layer information obtained by the core network node converting the first execution result from non-access stratum information. The conversion node converts the second execution result from protocol layer information into application layer information and sends the application layer information to the application node.

26. The method according to claim 21, 22 or 25, wherein, information interaction between the conversion node and the core network node is performed in a manner based on a reference point under a service architecture.

27. The method according to claim 22, 24 or 25, wherein, non-access stratum information is transmitted between the core network node and the reader node based on NGAP, and non-access stratum information is transmitted between the reader node and the target node through L1 / L2 messages.

28. A first communication device, comprising: a receiving unit, configured to receive first task information; a processing unit, configured to convert the first task information into second task information; a sending unit, configured to send the second task information.

29. The first communication device according to claim 28, wherein, the first task information and / or the second task information is used to indicate task parameters that the target node needs to execute.

30. The first communication device according to claim 29, wherein, the task parameters that the target node needs to execute include at least one of the following: the content of the task; the period of the task; the reporting method of the execution result; the control parameter of the execution result; the scope of task execution.

31. The first communication device according to claim 29 or 30, wherein, the target node includes a tag node.

32. The first communication device according to any one of claims 29 to 31, wherein, the first communication device is a conversion node, and the receiving unit is further configured to receive the first task information from the application node, and the first task information is application layer information.

33. The first communication device according to claim 32, wherein, the sending unit is further configured to send the second task information to the target node, and the second task information is non-access stratum information obtained by the conversion node converting the first task information from application layer information.

34. The first communication device according to claim 32 or 33, wherein, the receiving unit is further configured to receive a first execution result, which is a result obtained by the target node performing a task based on the second task information; the processing unit is further configured to convert the first execution result into a second execution result; and the sending unit is further configured to send the second execution result.

35. The first communication device according to claim 34, wherein, the receiving unit is further configured to receive the first execution result from the target node, and the first execution result is non-access stratum information.

36. The first communication device according to claim 35, wherein the first communication device is a conversion node, and the sending unit is further configured to send the second execution result to an application node through a communication network, and the second execution result is application layer information obtained by the conversion node converting the first execution result from non-access stratum information.

37. The first communication device according to claim 32, 33 or 35, wherein, application layer information is transmitted between the conversion node and the application node through TCP / IP, and non-access stratum information is transmitted between the conversion node and the target node through L1 / L2 messages.

38. The first communication device according to claim 32, 33, 35, 36 or 37, wherein, the conversion node is located on a reader node.

39. The first communication device according to claim 32, wherein, the sending unit is further configured to send the second task information to a core network node, and the second task information is protocol layer information obtained by the conversion node converting the first task information from application layer information. The core network node converts the second task information from protocol layer information into non-access stratum information and sends the non-access stratum information to the target node through a reader node.

40. The first communication device according to claim 39, wherein, the receiving unit is further configured to receive a second execution result, which is obtained by converting a first execution result, and the first execution result is a result obtained by the target node performing a task based on the second task information; the processing unit is further configured to convert the second execution result into a third execution result; and the sending unit is further configured to send the third execution result.

41. The first communication device according to claim 40, wherein, the first communication device is a conversion node, and the receiving unit is further configured to receive the second execution result from the core network node, and the second execution result is protocol layer information obtained by the core network node converting the first execution result from non-access stratum information.

42. The first communication device according to claim 41, wherein, the first communication device is a conversion node, and the sending unit is further configured to send the third execution result to an application node, and the third execution result is application layer information obtained by the conversion node converting the second execution result from protocol layer information.

43. The first communication device according to any one of claims 40 to 42, wherein, Information interaction is performed between the conversion node and the core network node in a manner based on a reference point under a service architecture.

44. A second communication device, comprising: a receiving unit configured to receive second task information, where the second task information is obtained by converting first task information; a processing unit configured to convert the second task information into third task information; a sending unit configured to send the third task information.

45. The second communication device according to claim 44, wherein at least one of the first task information, the second task information, and the third task information is used to indicate task parameters that a target node needs to execute.

46. The second communication device according to claim 45, wherein the task parameters that the target node needs to execute include at least one of the following: the content of the task; the period of the task; the reporting method of the execution result; the control parameters of the execution result; the scope of task execution.

47. The second communication device according to claim 45 or 46, wherein the target node includes a tag node.

48. The second communication device according to any one of claims 44 to 47, wherein the second communication device is a core network node, and the receiving unit is further configured to receive the second task information from the conversion node, where the second task information is protocol layer information obtained by the conversion node by converting first task information from an application node, and the first task information is application layer information.

49. The second communication device according to claim 48, wherein the second communication device is a core network node, and the sending unit is further configured to send the third task information to the target node through a reader node, where the third task information is non-access stratum information.

50. The second communication device according to any one of claims 44 to 49, wherein the receiving unit is further configured to receive a first execution result; the processing unit is further configured to convert the first execution result into a second execution result; the sending unit is further configured to send the second execution result.

51. The second communication device according to claim 50, wherein the second communication device is a core network node, and the receiving unit is further configured to receive the first execution result from the target node through a reader node, where the first execution result is non-access stratum information.

52. The second communication device according to claim 51, wherein the second communication device is a core network node, and the sending unit is further configured to send the second execution result to the conversion node, where the second execution result is protocol layer information obtained by the core network node by converting the first execution result from non-access stratum information, and the conversion node converts the second execution result from protocol layer information into application layer information and sends the application layer information to the application node.

53. The second communication device according to claim 48, 49 or 52, wherein Information interaction is performed between the conversion node and the core network node in a manner based on a reference point under a service architecture.

54. The second communication device according to claim 49, 51 or 52, wherein Non-access stratum information is transferred between the core network node and the reader node based on NGAP, and non-access stratum information is transferred between the reader node and the target node through L1 / L2 messages.

55. A communication device, comprising: a transceiver, a processor, and a memory, the memory being configured to store a computer program, the transceiver being configured to communicate with other devices, and the processor being configured to call and run the computer program stored in the memory, so that the communication device executes the method according to any one of claims 1 to 27.

56. A chip, comprising: a processor, configured to call and run a computer program from a memory, such that a device installed with the chip executes the method according to any one of claims 1 to 27.

57. A computer-readable storage medium, configured to store a computer program, which, when run by a device, causes the device to execute the method according to any one of claims 1 to 27.

58. A computer program product, comprising computer program instructions that cause a computer to execute the method according to any one of claims 1 to 27.

59. A computer program, which causes a computer to execute the method according to any one of claims 1 to 27.

Images