Communication method and apparatus, device, and storage medium

Abstract

The present application relates to the technical field of communications, and discloses a communication method and apparatus, a device, and a storage medium. In the method, upon receiving an indication of a first message, a reader may stop a related process of a service request on the basis of the indication of the first message, or the reader may stop a related process of the service request on the basis of its own reason; and after stopping the related process of the service request, the reader may instruct, by means of a second message, an A-IoT device to also stop the related process of the service request. In this way, a second device can be prevented from continuously monitoring subsequent signaling / transmission of the service request, thereby saving device energy consumption. When there is a more urgent service demand, it is also convenient for the reader to handle the more urgent service demand. The reader may also not send the second message. If the A-IoT device continuously fails to receive an R2D transmission, the A-IoT device may stop monitoring subsequent R2D transmissions, thereby reducing device energy consumption and also reducing R2D signaling overhead.

Description

A communication method, apparatus, device and storage medium

[0001] The present application claims priority to the Chinese patent application No. 202411370360.0, filed on September 27, 2024, and entitled "A communication method, apparatus, device and storage medium", the whole content of which is incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, and in particular to a communication method, apparatus, device and storage medium. BACKGROUND

[0003] With the wide application of Internet of Things technology, in the future, there will be a large number of Internet of Things devices connected, and for this reason, Ambient Internet of Things (A-IoT) has emerged.

[0004] In an indoor scene, the Ambient Internet of Things can include an application function (AF), a core network (CN), a Reader and a plurality of A-IoT devices. The application function has many service requirements, and after the AF sends the service requirements to the Reader, the Reader and the A-IoT devices interact to complete the service requirements. In some cases, during the process of a service requirement, the interaction between the Reader and the A-IoT devices needs to be stopped, and how to stop the interaction between the Reader and the A-IoT devices is a problem to be solved at present. SUMMARY

[0005] The present application provides a communication method, apparatus, device and storage medium, which can meet the requirements of the AF related to time and signaling overhead. The technical solution is as follows:

[0006] In a first aspect, embodiments of the present application provide a communication method applied to a first device in an environmental Internet of Things, the first device can be a Reader. In the method, the first device can receive a first message, the first message indicating to stop a service request related procedure. After receiving the first message, the first device can further send a second message, the second message indicating to stop the service request related procedure. In this way, the first device can stop the ongoing service request related procedure based on the indication of the first message, and after the first device stops the service request related procedure, the second device can also be indicated to stop the service request related procedure by the second message. In this way, the second device can avoid continuously monitoring the subsequent signaling / transmission of the service request, and the device energy consumption can be saved. When there is a more urgent service demand, the Reader can also perform the more urgent service demand in time.

[0007] Alternatively, after receiving the first message, the first device can also stop the service request related procedure, and not send the second message. After the first device stops the service request related procedure, the second device will not receive the downlink R2D transmission. If the second device continuously does not receive the R2D transmission, the second device can stop monitoring the subsequent R2D transmission, thereby saving the device energy consumption and also saving the R2D signaling overhead.

[0008] In the communication method of the present application, the Reader can also actively stop the service request related procedure of the Reader itself based on its own reasons. In this way, the first device can also send the second message or stop the service request related procedure without receiving the first message.

[0009] In combination with the first aspect, in some implementation manners of the first aspect, the first message comprises at least one of the following contents: an index of the service request, an index of the second device, an indication to stop the service request related procedure, an indication to stop all service request related procedures, and a condition to stop the service request. In this way, the application function or the core network can send the above at least one content to the first device according to the demand, thereby realizing the indication to the first device to stop the service request related procedure.

[0010] In combination with the first aspect, in some implementation manners of the first aspect, the condition to stop the service request comprises a completion progress of the service request and / or a stop time. In this way, when indicating the first device to stop the service request related procedure, the service request to be stopped can also be completed as much as possible.

[0011] In some implementations of the first aspect, the second message includes at least one of the following: an identifier of the first device, an index of the service request, an index of a procedure related to the service request, an index of a second device related to the service request, an indication to stop the procedure related to the service request, an indication to stop all procedures related to the service request. In this way, the first device can send the at least one of the above to the second device according to the needs, so as to instruct the second device to stop the procedure related to the service request. For example, when the first device needs to stop all procedures related to the service request, the first device can send the identifier of the first device to the second device, or send the indication to stop all procedures related to the service request, or send the index of the service request.

[0012] In some implementations of the first aspect, before receiving the first message, the method further includes: sending a third message, the third message requesting to stop at least one procedure related to the service request. When the reader needs to stop the procedure related to the service request based on its own reasons, the reader can actively send the third message to the third device of the upper layer, and then the third device can reply a response message, and the first device can determine whether to stop the requested content based on the response message.

[0013] The third device can reject the request of the first device, and the third device can send a response message indicating that the request of the first device is rejected. The third device can also agree to part of the request or all of the request of the first device. When the third device agrees to the request of the first device, the third device can send a first message to the first device, the first message indicating to stop at least one of the contents requested by the third message.

[0014] In some implementations of the first aspect, before stopping the procedure related to the service request, the method further includes: sending a fourth message, the fourth message indicating to stop listening to subsequent R2D transmissions if no R2D transmission is received within a preset time period. In this way, a preset time period can be pre-configured or pre-defined, so that the second device can stop listening to subsequent R2D transmissions if no R2D transmission is received within the preset time period, thereby saving the energy consumption of the second device.

[0015] In the second aspect, the embodiments of the present application provide a communication method applied to a second device in an environmental Internet of Things (IoT), the second device being an A-IoT device. In the method, the A-IoT device stops listening to subsequent R2D transmissions if no R2D transmission is received within a preset time period. In this way, after the first device stops the procedure related to the service request, the A-IoT device will not receive the downlink R2D transmission, and if the A-IoT device continuously does not receive the R2D transmission, the A-IoT device can stop listening to subsequent R2D transmissions, thereby saving the energy consumption of the device and saving the R2D signaling overhead.

[0016] Alternatively, the A-IoT device can receive a second message, the second message indicating to stop the service request related procedure; after receiving the second message, stop monitoring the R2D transmission of the service request related procedure. In this way, after the first device stops the service request related procedure, the second message can be sent to the A-IoT device, and the A-IoT device can stop the service request related procedure based on the indication of the second message, so that the second device can avoid continuously monitoring the subsequent signaling / transmission of the service request after the first device stops the service request related procedure, thereby saving device energy consumption. When there is a more urgent service requirement, the Reader can also timely perform the more urgent service requirement.

[0017] With reference to the second aspect, in some implementations of the second aspect, the second message includes at least one of the following: an identifier of the first device, an index of the service request, an index of the service request related procedure, an index of the second device related to the service request, an indication to stop the service request related procedure, an indication to stop the service request related procedure.

[0018] With reference to the second aspect, in some implementations of the second aspect, the method further includes: receiving a fourth message, the fourth message indicating to stop monitoring subsequent R2D transmissions if no R2D transmission is received within a preset time period. By pre-configuring the fourth message, the A-IoT device can stop monitoring subsequent R2D transmissions when no R2D transmission is received within a preset time period.

[0019] In a third aspect, the embodiments of the present application provide a communication method applied to a third device in an environmental Internet of Things, the third device being a base station or a core network or an application function. In the method, the third device can receive a third message, the third message requesting to stop at least one service request related procedure. When the Reader needs to stop the service request related procedure based on its own reasons, the Reader can actively send the third message to the third device of the upper layer, and then the third device can reply a response message, and the first device can determine whether to stop the requested content based on the response message. In this way, the third device can perform some operations, and when there is a service request that needs to be completed urgently, or when the third device can solve the problem of the Reader, the Reader can continue to complete the service request.

[0020] With reference to the third aspect, in some implementations of the third aspect, the third message includes at least one of the following: an index of the service request, an index of the second device related to the service request, an index of the application function AF that stops the service request, a service type corresponding to the service request, a reason for stopping the service request, an indication to stop the service request.

[0021] In a third aspect, in some implementations of the third aspect, the method further includes sending a first message, the first message indicating to stop at least one of the service requests requested by the third message.

[0022] In a fourth aspect, a communication apparatus is provided, which includes means for performing each step of the method according to any implementation of the first aspect, or means for performing each step of the method according to any implementation of the second aspect, or means for performing each step of the method according to any implementation of the third aspect.

[0023] In a fifth aspect, a communication apparatus is provided, which includes a processor and an interface, the interface being configured to send and / or receive a signal, so that the processor performs the method according to any implementation of any of the above aspects.

[0024] In a sixth aspect, a communication device is provided, which includes a processor coupled to a memory, the memory being configured to store a program or instructions, which, when executed by the processor, cause the communication device to perform the method according to any implementation of any of the above aspects.

[0025] In a seventh aspect, a communication system is provided, which includes a first device according to the first aspect, a second device according to the second aspect, and a third device according to the third aspect.

[0026] In an eighth aspect, a computer readable medium is provided, which is configured to store a computer program, which, when executed on a computer, causes the computer to perform the method according to any implementation of any of the above aspects.

[0027] In a ninth aspect, a chip is provided, which includes a processing circuit (or processor), which is configured to perform the method according to any implementation of any of the above aspects.

[0028] In a tenth aspect, a computer program product is provided, which includes a computer program (also referred to as code or instructions), which, when executed, causes a computer to perform the method according to any implementation of any of the above aspects. BRIEF DESCRIPTION OF DRAWINGS

[0029] FIG. 1 shows a structural schematic diagram of a communication system according to an embodiment of the present application;

[0030] FIG. 2 shows a signaling access schematic diagram according to an embodiment of the present application;

[0031] FIG. 3 shows a flow schematic diagram of a communication method according to an embodiment of the present application;

[0032] FIG. 4 shows a flow diagram of another communication method according to an embodiment of the present application;

[0033] FIG. 5 shows a flow diagram of another communication method according to an embodiment of the present application;

[0034] FIG. 6 shows a structure diagram of a communication device according to an embodiment of the present application;

[0035] FIG. 7 shows a structure diagram of another communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0036] The technical solutions in the embodiments of the present application will be described below with reference to the drawings. The network architecture and service scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. It can be known by those skilled in the art that, as the network architecture evolves and new service scenarios appear, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0037] The ordinal numbers “1”, “2”, “3”, “first”, “second”, “third”, and “fourth” in the present application are used to distinguish a plurality of objects, and are not used to limit the order of the plurality of objects. “Multiple” in the present application refers to two or more. The term “and / or” in the present application is merely used to describe the association relationship of the associated objects, and indicates that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character “ / ” in the present application generally represents an “or” relationship between the front and rear associated objects. The term “at least one” in the present application can represent “one” and “two or more”, for example, at least one of A, B and C can represent the following seven cases: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, A and C exist simultaneously, C and B exist simultaneously, and A, B and C exist simultaneously.

[0038] With the wide application of Internet of Things technology, in the future, there will be a large number of Internet of Things devices interconnected and intercommunicated, and the Ambient Internet of Things (A-IoT) emerges as the times require. The Ambient Internet of Things can also be referred to as Ambient IoT.

[0039] A-IoT can also be referred to as passive IoT, which is a new IoT service. In the A-IoT, the A-IoT device (Ambient IoT device) is powered by energy harvesting (e.g., solar, radio waves, motion, vibration, heat, pressure, or other power sources) without a battery or with limited energy storage, and can be powered without a battery or with limited energy storage, without the need for manual battery replacement or charging. The A-IoT device has a peak power consumption of about 1 uW to 100 uW, and has the advantages of smaller size, lower power consumption, and lower complexity. Therefore, A-IoT can be more widely applied, and can achieve hundreds of billions of connections.

[0040] For example, A-IoT can be applied to smart home to monitor ambient temperature, humidity, air quality, and occupancy for intelligent control. For example, A-IoT can be applied to agriculture to track environmental conditions and monitor livestock health. For example, A-IoT can be applied to automated warehousing for warehousing, inventory, warehousing, and inspection, etc.

[0041] First, the structure of the A-IoT communication system suitable for the embodiments of the present application is described below.

[0042] FIG. 1 is a schematic diagram of the structure of an A-IoT communication system suitable for the embodiments of the present application. The A-IoT communication system can include an application function (AF) 110, a core network (CN) 120, a base station 130, and a plurality of A-IoT devices 140. The application function 110 can communicate with the base station 130 through the core network 120. The core network 120 can provide processing functions or transparent transmission functions.

[0043] In topology ①, the base station 130 is close to the A-IoT device 140, and the base station 130 can directly communicate with the plurality of A-IoT devices 140 for bidirectional communication transmission.

[0044] In topology ②, the A-IoT communication system can further include an intermediate node 150. The intermediate node 150 is located between the base station 130 and the A-IoT device 140, and the A-IoT device 140 communicates with the intermediate node 150 bidirectionally. The intermediate node 150 communicates with the base station 130 through an air interface (i.e., a Uu air interface, which can be referred to as Uu). The transmission of the Uu air interface can include uplink transmission and downlink transmission. The intermediate node 150 transmits ambient IoT data and / or signaling between the base station 130 and the A-IoT device 140.

[0045] In the embodiments of the present application, the intermediate node can be a terminal device such as a mobile phone supporting 5G NR, a repeater, etc., and has the capability of environmental Internet of Things.

[0046] In the embodiments of the present application, the reader can be a terminal device, a base station, a micro base station or a router, or other devices with reading / writing functions. The reader (Reader) can include a base station reader (gNB Reader) and a terminal reader (UE Reader). Both the base station 130 and the intermediate node 150 in FIG. 1 can function as the reader Reader.

[0047] It should be understood that in the A-IoT communication system, the A-IoT radio access network (RAN) A-IoT device 140 is connected to the RAN node in a wireless manner. The RAN node is connected to the core network 120 in a wireless or wired manner. The core network device in the core network 120 and the RAN node can be different physical devices respectively, or can be the same physical device integrated with the core network logic function and the radio access network logic function.

[0048] The RAN can include two functional blocks: a reader function (common reader function) and an A-IoT access function (AIoT RAN node function). In topology ①, both functional blocks are in the base station. In topology ②, the reader function is distributed in the UE Reader (intermediate node 150), and the A-IoT access function is distributed in the base station.

[0049] It should be understood that in the A-IoT communication system, one reader can communicate with multiple A-IoT devices 140, and the communication system can include multiple readers. The embodiments of the present application do not limit this.

[0050] It should be understood that the structure of the A-IoT communication system can also have other implementation manners, and the above FIG. 1 is only an exemplary illustration.

[0051] The A-IoT communication system shown in FIG. 1 can support various communication technologies, such as fifth generation (5th generation, 5G) mobile communication technology, new radio (new radio, NR), etc. The 5G mobile communication technology in the embodiments of the present application includes non-standalone (non-standalone, NSA) 5G mobile communication technology or standalone (standalone, SA) 5G mobile communication technology. The technical solutions provided in the present application can also be applied to future communication technologies, such as the sixth generation mobile communication technology, etc. The embodiments of the present application do not limit this.

[0052] The core network device includes, for example, an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), or the like.

[0053] The terminal device can also be referred to as an access terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), or the like. The terminal device can be a mobile phone, a tablet computer, a notebook computer, a palm computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, or a wireless terminal in smart home, or the like. The router can perform 5G communication.

[0054] In the embodiments of the present application, the A-IoT device 140 can be a tag device, a sensor, a controller, or the like. From the power consumption level and the ability to generate signals, the A-IoT device 140 can be divided into the following three categories: the first category has energy storage, Device-to-Reader uplink transmission is backscattering, and has no independent signal generation. The second category has energy storage, Device-to-Reader uplink transmission is backscattering, has no independent signal generation, has a power amplifier, and the stored energy can be used to amplify the reflected signal. The third category has energy storage, has a power amplifier, and has independent signal generation.

[0055] Generally, a service request issued by an application function (AF) is transmitted to a Reader, which sends a paging message to an A-IoT device, and the target A-IoT device replies to the Reader after receiving the paging message. Among them, the A-IoT device sends a message to the Reader, which is an uplink D2R (Device to Reader) transmission, carried on the uplink physical channel PDRCH; the Reader sends a message to the A-IoT device, which is a downlink R2D (Reader to Device) transmission, carried on the downlink physical channel PRDCH.

[0056] In the process of interaction between the Reader and the A-IoT device, the time slot aloha mechanism in time division multiplexing (TDM) is adopted. Under the time slot aloha mechanism, the time provided for the entire channel transmission information is divided into several time slices (referred to as time slots), and only one A-IoT device can send data in each time slot. After receiving the instruction of the Reader, the A-IoT device waits for a time slot in which it can send uplink signaling, and sends uplink signaling after waiting for the time slot belonging to it, thereby completing the service request. In each round of inventory, if there is a device that has not been successfully inventoried, it can perform inventory in a new round; until all devices complete inventory, the process ends.

[0057] As shown in FIG. 2, when the Reader performs a service request, it can send one or more paging messages to the A-IoT device, such as A-IoT paging and Subsequent A-IoT paging. One or more processes can be performed after a paging message, such as a paging round, which can represent a process. There are multiple access opportunities in a process, which can be described as an access round. The Reader can send signaling such as R2D Round Trigger and R2D Trigger to let the A-IoT device start accessing the Reader. The A-IoT device can find an access opportunity in a time slot to communicate with the Reader. Among them, the A-IoT paging can carry a service request index and a process index. Different processes can be performed after the A-IoT paging and the Subsequent A-IoT paging. When receiving a stop indication carrying a service request index, the processes in the A-IoT paging and the Subsequent A-IoT paging are stopped. When receiving a stop indication carrying a process index, the corresponding process can be stopped according to the index.

[0058] In the process of service, if there is a more urgent service requirement, the ongoing service process needs to be stopped to proceed with the more urgent service requirement. If the ongoing service process has exceeded the time limit given by the AF, or the UE reader stops the service, an end-to-end stop process is needed to avoid the A-IoT device continuously listening to the subsequent signaling (such as rep and paging rep) and save device energy consumption. How to stop the interaction between the Reader and the A-IoT device is a problem to be solved at present.

[0059] To this end, an embodiment of the present application proposes a communication method. The AF / CN can issue a first message. After receiving the first message, the Reader can stop the service request related process according to the indication of the first message. Further, the Reader can send a second message to the A-IoT device to indicate the A-IoT device to stop the service request related process. In this way, after the Reader stops the service request related process, the A-IoT device also stops the service request related process, which can avoid the A-IoT device continuously listening to the subsequent signaling / transport of the ongoing service request to save device energy consumption. When there is a more urgent service requirement, the ongoing service request related process can also be stopped so that the Reader can proceed with the more urgent service process. If the A-IoT device can handle multiple processes in parallel, it can also avoid the A-IoT device continuously listening to the subsequent signaling / transport of the stopped service request to save device energy consumption.

[0060] If the ongoing service request has exceeded the time limit given by the AF, the AF / CN can issue a first message. After receiving the first message, the Reader can stop the service request related process according to the indication of the first message. Further, the Reader can send a second message to the A-IoT device to indicate the A-IoT device to stop the service request related process.

[0061] Alternatively, after receiving the first message, the Reader can stop the service request related process, and the A-IoT device can stop listening to the R2D transport when it continuously fails to receive the R2D transport. In this way, the A-IoT device is prevented from continuously listening to the subsequent signaling / transport to save device energy consumption.

[0062] The Reader can autonomously stop the service request related process for some reason. At this time, the Reader can send a second message to the A-IoT device to indicate the A-IoT device to stop the service request related process, which can avoid the A-IoT device continuously listening to the subsequent signaling / transport to save device energy consumption. The Reader can also send a stop request to a third device to stop the service request or continue to complete the service request under the indication of the third device.

[0063] The service request can be an inventory request, for example, in an automated warehouse scenario, the AF can inventory the inventory of goods in the warehouse. The service request can also be a positioning request, for example, the AF can determine which shelf the goods are on. The service request can also be a control request, for example, the AF can read temperature data for a period of time, or the AF can command the Device to turn on or off, etc. Alternatively, the service request can also be read, write, activate, deactivate, etc.

[0064] When the A-IoT device receives the service request, a response result can be returned, for example, when the service request is an inventory request, the response result can include an identity document (ID) of the A-IoT device, the device ID can be used to uniquely identify the A-IoT device. Specifically, the ID can be an electronic product code (EPC), or the ID can be a CN, Radio Access Network (RAN) assigned identity.

[0065] Wherein, the request index is used to indicate that the message containing this request index is related to the service request corresponding to the index. Different service requests correspond to different request indexes. Specifically, for different types of services, their request indexes are different, for example, when the service request is an inventory request, the request index can be inventory1; when the service request is a positioning request, the request index can be positioning1. For different requests under the same type of service, their request indexes are also different, for example, when there are multiple inventory requests, the request indexes can be inventory1, inventory2, inventory3, etc.

[0066] When the Reader receives the service request, the Reader and the A-IoT device perform signaling interaction to complete the service request, and the A-IoT device continuously listens to the signaling of the Reader.

[0067] It should be understood that the communication system includes multiple Readers, one Reader can receive multiple service requests, one service request can be split into one or more processes, and one Reader can interact with multiple A-IoT devices. One A-IoT device can process at least one process, and can process multiple processes in parallel. The following describes one Reader and one A-IoT device controlled by the Reader. Wherein, the Reader is a first device. The A-IoT device is a second device. It should be understood that the second device can also be other Internet of Things devices.

[0068] The communication method provided by the embodiments of the present application is described in detail below with reference to the accompanying drawings. FIG. 3 shows a flowchart of a communication method. In the method, the Reader performs corresponding response after receiving the stop indication.

[0069] In S301, the AF sends a service request to the core network CN, and the service request includes a service request related index. Correspondingly, the CN receives the service request.

[0070] For example, the service request can be an inventory request, and the request index can be inventoryl. In the following description, the inventory is taken as an example, but it should be understood that the first request in the embodiments of the present application is not limited to inventory, but can also be positioning, command, etc.

[0071] In S302, the CN sends a service request related command to the Reader, and the service request related command includes the service request related index. Correspondingly, the Reader receives the service request related command.

[0072] After receiving the service request of the AF, the CN can transparently transmit the service request to the Reader. Alternatively, after receiving the service request of the AF, the CN can analyze and process the service request, then generate a service request related command, and send it to the Reader.

[0073] In S303, the Reader sends an R2D transmission to the A-IoT device, and receives a reply of the A-IoT device.

[0074] After receiving the service request related command, the Reader can send a request related instruction to the A-IoT device according to the request index, and receive a reply of the A-IoT device. The Reader can send an A-IoT paging instruction corresponding to the inventory request to the Device, and the response result of the Device to the inventory request can be the Device ID. Then the Reader sends the result to the CN, and the CN sends it to the AF.

[0075] The R2D transmission can also be described as downlink transmission, downlink trigger signaling, etc., for example, it can include rep and paging rep, and the signaling shown in FIG. 2, etc.

[0076] In S304, the AF sends a first message to the CN, and the first message indicates to stop the service request related process. Correspondingly, the CN receives the first message.

[0077] The reader can execute one or more service requests, when the reader executes one service request (e.g. inventory A), the service request is the service request (inventory A). When the reader executes multiple service requests, e.g. inventory A, inventory B, inventory C, inventory D, the service request can be part of the multiple service requests, e.g. inventory A, inventory B; or all of the multiple service requests.

[0078] Stopping the service request related procedure can also be described as stopping the service request related operation, stopping the service request. Stopping can also be described as terminating.

[0079] S305, the CN sends a first message to the Reader, the first message indicating to stop the service request related procedure. Correspondingly, the Reader receives the first message.

[0080] The CN can transmit the first message to the Reader as received. Or the CN can parse the first message and then send it to the Reader.

[0081] The first message can include at least one of the following: index of the service request, index of the second device, indication to stop the service request related procedure, indication to stop all service request related procedures, condition to stop the service request.

[0082] In an implementation, the first message can include the index of the service request, and after the Reader receives the first message, the Reader can stop all procedures of the service request corresponding to the index. For example, the first message can include the index of inventory A and the index of inventory B, and the first message indicates to stop the inventory A related procedure and the inventory B related procedure, and after the Reader receives the first message, the Reader can stop the inventory A related procedure and the inventory B related procedure.

[0083] In another implementation, the first message can include the index of the A-IoT device, and the first message indicates to stop the service request related procedure performed by the A-IoT device, and after the Reader receives the first message, the Reader can stop the subsequent procedure of the A-IoT device. For example, the AF can obtain the index of the A-IoT device that provides services for it, and the first message can include the index of A-IoT device 1 and the index of A-IoT device 2, and after the Reader receives the first message, the Reader can stop the subsequent procedure of A-IoT device 1 and the subsequent procedure of A-IoT device 2. For example, A-IoT device 1 performs procedure 1, procedure 2, and procedure 3 in order, and when it receives the stop indication at the step of executing procedure 1, it stops the subsequent steps of procedure 1, procedure 2, and procedure 3. Wherein, the index of the A-IoT device can be the ID of the A-IoT device, the AS ID, or a random number RN, etc.

[0084] In some other implementations, the first message can comprise an indication of stopping the processes related to the service requests, for example, the indication can be represented by a specific field. For example, when stopping one or more service requests, a specific field "10001" can be included in the first message, each bit of the field corresponds to an index of a service request, the relationship between the predefined bit position and the service request is defined, and the value of the bit indicates whether to stop the service request, so that the first service request and the fifth service request can be indicated in sequence. In this way, after the Reader receives the first message, it can know to stop the service request corresponding to the first bit and the service request corresponding to the fifth bit, and know the specific information of the service request corresponding to the first bit and the specific information of the service request corresponding to the fifth bit.

[0085] In some other implementations, the first message can comprise an indication of stopping the processes related to all service requests, for example, the indication can be represented by a specific field, the specific field can be "all", can be "1", and the present application does not limit it. In this way, after the Reader receives the first message, it can know to stop the processes related to all service requests. This implementation can save signaling overhead.

[0086] In some other implementations, the first message can comprise an index of a service request and a stop indication. For example, the index of the service request can be represented as {index 1, index 2, index 3, index 4}, and the stop indication can be, for example, a field "1111", each bit of the field corresponds to an index of a service request, and the bit order is the arrangement order of the index of the service request. In this way, each bit can be used to indicate to stop the process related to the corresponding service request. For example, the stop indication can also be "1101", so that the process related to the service request of the third bit continues, and the processes related to the service requests of the other bits are stopped. For example, the stop indication can also be "1", indicating to stop the processes related to the service requests recorded in the list.

[0087] In another implementation, the first message can comprise an index of a second device and a stop indication. The indication can be represented by a specific field, so that all the processes related to the service requests performed by the second device can be explicitly indicated by the field.

[0088] In another implementation, the first message can comprise a service request related index, a second device related index and a stop indication. In this way, the service request related procedure can be instructed to stop, and the second device related procedure can be instructed to stop. For example, the service request index and the second device index are respectively represented. For example, the service request index can be represented as {index 1, index 2, index 3, index 4}, and the index 1 in the first message can be associated with {A-IoT device 1, A-IoT device 2}, and the stop indication can be, for example, "1111", in this way, the service request corresponding to the index 1 can be stopped.

[0089] In the above implementation, the Reader performs the stop procedure after receiving the first message. In other implementations, the first message can comprise a condition for stopping the service request. That is, the first message instructs to stop the service request related procedure, and instructs to stop the service request related procedure when the condition for stopping the service request is met. Thus, after receiving the first message, the Reader can stop the service request related procedure instructed by the first message when the condition for stopping the service request is met. The condition for stopping the service request can comprise at least one of the following: completion progress of the service request, time for stopping the service request.

[0090] For example, the condition for stopping the service request can comprise the time for stopping the service request, and the first message instructs to stop the service request related procedure and instructs to stop the service request related procedure after a given time range. Thus, after receiving the first message, the Reader can stop the service request related procedure instructed by the first message after the given time range. The time for stopping the service request can be an absolute time, and the first message can comprise a first time, for example, the first time is 10 o'clock in the morning, and the Reader can stop the service request related procedure at 10 o'clock after receiving the first message at 8 o'clock in the morning. The time for stopping the service request can also be a relative time, and the first message can comprise a first duration, for example, the first duration is 5 minutes, and the Reader can stop the service request related procedure after 5 minutes after receiving the first message. In this way, when the AF has a more urgent service demand, the stop time of the ongoing service request can be set according to the execution time of the more urgent service demand.

[0091] Exemplarily, the condition of stopping the service request can comprise a completion progress of the service request. The completion progress can be a preconfigured ratio. When the ongoing service request has completed the preconfigured ratio, the Reader can stop the subsequent procedure of the ongoing service request. The preconfigured ratio can be 80%, 90%, etc., which is not limited in the application. For example, the Reader is conducting inventory A, a total of 50 need to be inventoried, the preconfigured ratio is 80%, after the Reader receives the first message, the ongoing inventory service can be continued, and when 40 have been inventoried, the inventory service can be stopped.

[0092] Exemplarily, the condition of stopping the service request can comprise a completion progress of the service request and a time of stopping the service request. After the Reader receives the first message, the ongoing inventory service can be continued. When the time of stopping the service request has not arrived and the preconfigured ratio of the service request has been completed, the subsequent procedure of the ongoing service request can be stopped. When the time of stopping the service request has arrived and the preconfigured ratio of the service request has not been completed, the subsequent procedure of the ongoing service request can also be stopped.

[0093] S306, the Reader sends a second message to the A-IoT device. The second message indicates to stop the procedure related to the service request. Correspondingly, the A-IoT device receives the first message.

[0094] After the Reader receives the first message, the Reader sends the second message to the A-IoT device, and the A-IoT device responds according to the instruction of the Reader. The second message is sent to the A-IoT device in the form of broadcast.

[0095] The Reader can broadcast the second message to the A-IoT device according to its own situation. The second message comprises at least one of the following contents: an identifier of the first device, an index of the service request, an index of the procedure related to the service request, an index of the A-IoT device related to the service request, an indication of stopping the procedure related to the service request, and an indication of stopping all procedures related to the service request.

[0096] For example, if the Reader receives the index of the service request, the Reader can send the index of the service request to the A-IoT device. For another example, one service request can correspond to one flow, or can correspond to multiple flows. Correspondingly, one index of the service request can correspond to the index of one flow, or can correspond to the index of multiple flows. If the Reader receives the index of the service request, the Reader can obtain the index of the flow related to the service request according to the index of the service request, and send the index of the flow related to the service request to the A-IoT device. For another example, if the Reader receives the index of the service request, the Reader can obtain the index of the A-IoT device performing the service request according to the index of the service request, and send the index of the A-IoT device to the A-IoT device. For another example, if the Reader receives the index of the A-IoT device, the Reader can send the index of the A-IoT device to the A-IoT device. For another example, if the Reader receives the indication of stopping the service request, the Reader can send the index of the service request, or the index of the flow related to the service request, or the index of the A-IoT device, or the indication of stopping the service request to the A-IoT device.

[0097] If the Reader receives the index of all service requests, or the Reader receives the indication of stopping all service requests, the Reader can send the index of the service request, or the index of the flow related to the service request, or the index of the A-IoT device, or the identification of the Reader, or the indication of stopping all flows related to the service request to the A-IoT device.

[0098] In an implementation manner, the second message can include the identification of the first device (i.e., the identification of the Reader), or can include the indication of stopping all flows related to the first device, or can include the indication of stopping all flows related to the service request. Alternatively, the second message can include the identification of the first device and the indication of stopping all flows related to the first device. Alternatively, the second message can include the identification of the first device and the indication of stopping all flows related to the service request. After the A-IoT device receives the second message, the A-IoT device can obtain the identification of the Reader, and stop all flows related to the Reader when the A-IoT device itself is performing / going to perform the flow related to the Reader. That is, the A-IoT device stops listening to all R2D transmissions of the Reader in the future.

[0099] In another implementation, the second message can comprise an indication to stop the service request related procedure. Alternatively, the second message can comprise an index of the service request and an indication to stop the service request related procedure. After receiving the second message, the A-IoT device stops all the procedures related to the service request if it is performing / going to perform the procedure.

[0100] In another implementation, the second message can comprise an index of the service request. After receiving the first message, the A-IoT device can obtain the index of the service request, and stop all the procedures related to the service request if it is performing / going to perform the procedure. That is, the A-IoT device stops listening to all the subsequent R2D transmissions of the service request.

[0101] In another implementation, the second message can comprise an index of the service request related procedure. Alternatively, the second message can comprise an index of the service request related procedure and an indication to stop the procedure. After receiving the second message, the A-IoT device checks whether it is performing the procedure corresponding to the index, and stops the procedure corresponding to the index if it is performing the procedure. For example, the second message can comprise an index of procedure 1 and an index of procedure 2. After receiving the second message, the A-IoT device finds that it is performing procedure 1, and stops the subsequent steps of procedure 1. The A-IoT device finds that it is going to perform procedure 2, and stops procedure 2.

[0102] In another implementation, the second message can comprise an index of the A-IoT device related to the service request. Alternatively, the second message can comprise an index of the A-IoT device related to the service request and an indication to stop the A-IoT device from performing the service request. After receiving the second message, the A-IoT device determines whether the second message comprises the index of the A-IoT device, and stops listening to the subsequent R2D transmissions if the second message comprises the index of the A-IoT device. For example, the second message can comprise an index of device 1 and an index of device 2. After the reader broadcasts the second message, device 1 can receive the second message, parse the index of device 1 from the second message, and stop listening to the subsequent R2D transmissions. Device 2 can receive the second message, parse the index of device 2 from the second message, and also stop listening to the subsequent R2D transmissions.

[0103] S307, after receiving the second message, the A-IoT device stops listening to the subsequent R2D transmissions.

[0104] After receiving the second message, the A-IoT device considers that the service request related procedure is completed, and stops listening to the subsequent R2D transmissions. In this way, the reader can instruct the A-IoT device to stop listening to the R2D transmissions through the explicit indication message, avoid the A-IoT device from continuously listening to the subsequent R2D transmissions, and save the energy consumption of the device.

[0105] In some cases, after the Reader sends the third message, the A-IoT device may not receive the third message due to insufficient power of the A-IoT device or the like. In order to avoid that the A-IoT device does not receive the third message in time, the embodiment of the present application provides another communication method, as shown in FIG. 4, which includes S401-S407.

[0106] S401, the AF sends a service request to a core network CN, and the service request includes a service request related index. Correspondingly, the CN receives the service request.

[0107] S402, the CN sends a service request related command to the Reader, and the service request related command includes the service request related index. Correspondingly, the Reader receives the service request related command.

[0108] S403, the Reader sends an R2D transmission to the A-IoT device, and receives a reply of the A-IoT device.

[0109] S404, the AF sends a first message to the CN, and the first message indicates to stop a service request related process. Correspondingly, the CN receives the first message.

[0110] S405, the CN sends the first message to the Reader, and the first message indicates to stop the service request related process. Correspondingly, the Reader receives the first message.

[0111] The steps S401-S405 can refer to the aforementioned steps S301-S305, and will not be described here.

[0112] S406, the Reader stops the service request related process.

[0113] After receiving the second message, the Reader stops one or more service request related processes, for example, the Reader can stop sending the R2D transmission. In this way, the Reader itself stops the service request related process, or stops all processes, such as stopping the A-IoT paging, round trigger, slot trigger and the like shown in FIG. 2. After the Reader stops sending the R2D transmission, the A-IoT device cannot receive the R2D transmission.

[0114] S407, if the A-IoT device does not receive the R2D transmission within a preset time period, the A-IoT device stops listening to subsequent R2D transmissions.

[0115] When performing a certain service request, the A-IoT device performs the procedure in the service request, continuously monitors the R2D transmission of the procedure in the service request, and if no R2D transmission is received within a preset time period, the A-IoT device can consider that the procedure related to the service request is completed, and then stop monitoring the subsequent R2D transmission.

[0116] In some implementations, the preset time period can be a time period specified by a protocol, and the A-IoT device and the reader follow the protocol to interact. The A-IoT device following the protocol can realize that when no R2D transmission is received within the preset time period, the subsequent R2D transmission is stopped.

[0117] In other implementations, the preset time period can be determined by a preconfigured time period. As shown in FIG. 2, when the Reader sends the R2D transmission (such as A-IoT paging, round trigger, slot trigger, etc.) to the A-IoT device, the reader can send configuration information to the A-IoT device, that is, the fourth message. The fourth message indicates that if no R2D transmission is received within the preset time period, the subsequent R2D transmission is stopped.

[0118] For example, the preset time period can be a relative time, for example, the fourth message sent by the Reader to the A-IoT device includes a timer, and the preset time period is the time period from the start of the timer to the end of the timer. For example, the timer can start timing from receiving an R2D message, that is, the A-IoT device runs the timer after receiving an R2D message, and if no next R2D message is received until the timer expires, the A-IoT device considers that the procedure related to the service request is completed, and then stops monitoring the subsequent R2D transmission.

[0119] For another example, the timer can start timing from sending the last D2R message of a certain procedure. That is, the A-IoT device runs the timer after sending the last D2R message, and if no next R2D message is received until the timer expires, the A-IoT device considers that the procedure related to the service request is completed, and then stops monitoring the subsequent R2D transmission.

[0120] For example, the preset time period can also be an absolute time, for example, the Reader sends a time point to the A-IoT device, for example, 10 o'clock, and if the A-IoT device does not receive an R2D message before 10 o'clock, the A-IoT device considers that the procedure related to the service request is completed, and then stops monitoring the subsequent R2D transmission.

[0121] In some implementations, the preset time period can be a time length, for example, 10 minutes, that is, if the A-IoT device does not receive the next R2D message within 10 minutes after receiving the R2D message, the A-IoT device considers that the service request related process ends, and then stops listening to the subsequent R2D transmission.

[0122] In the embodiment shown in FIG. 4, in the scenario of stopping the entire process, the signaling overhead between the Reader and the A-IoT device can be saved, and the situation that the A-IoT device does not receive the second message after the Reader sends the second message can be avoided.

[0123] In the above, the Reader can end the service request related process indicated after receiving the stop indication of the AF or the CN or the base station. In some implementations, the Reader can actively stop or request to stop the service request related process according to its own situation. FIG. 5 shows another communication method provided by the embodiments of the present application, as shown in FIG. 5, which includes S501-S507.

[0124] S501, the AF sends a service request to the core network CN, and the service request includes a service request related index. Correspondingly, the CN receives the service request.

[0125] S502, the CN sends a service request related command to the Reader, and the service request related command includes the service request related index. Correspondingly, the Reader receives the service request related command.

[0126] S503, the Reader sends an R2D transmission to the A-IoT device and receives a reply of the A-IoT device.

[0127] The steps S501-S503 can refer to the aforementioned steps S301-S303, and will not be described here.

[0128] S504, the Reader sends a third message to a third device, and the third message requests to stop at least one service request related process. Correspondingly, the third device receives the third message.

[0129] S505, the third device sends a first message to the Reader, and the first message indicates to stop at least one of the contents requested by the third message. Correspondingly, the Reader receives the first message.

[0130] When the reader needs to stop the service request for some reason, the reader can actively send a third message to the third device to request to stop the service request related process. The third device can be a base station, a CN, or an AF. When the third device is a base station, the reader can be a UE reader, for example, the intermediate node in the topology 2. When the third device is a CN or an AF, the reader can be a base station reader. FIG. 5 only exemplarily shows an example in which the third device is a CN.

[0131] After receiving the third message, the third device can determine whether to accept the request of the reader. If the third device accepts the request of the reader, the third device can reply to the reader with a first message, which can include an acknowledgement message, to instruct the reader to stop all service request related processes requested by the third message.

[0132] After receiving the third message, the third device can also reject the request of the reader, and the third device can reply to the reader with a rejection message to instruct the reader to continue the service request related process.

[0133] After receiving the third message, the third device can also agree to part of the request of the third message, and the third device can send a first message to the reader, which can include part of the content included in the third message, to instruct the reader to stop part of the service request requested by the third message. In this way, the reader can determine to stop the service request based on the instruction of the third device, and then send a second message to the A-IoT device.

[0134] The third message can include at least one of the following: an index of the service request, an index of the A-IoT device related to the service request, an index of the application function AF that stops the service request, a service type corresponding to the service request, a reason for stopping the service request, an instruction to stop the service request, and an instruction to stop all service requests.

[0135] In some implementations, if the reader wants to stop a service request related process, the third message can include an index of the service request to request to stop all processes of the service request corresponding to the index. For example, the third message can include an index of inventory 1, an index of inventory 2, and an index of inventory 3, and the reader requests to stop the processes of the three services. Exemplarily, after receiving the third message, the third device can reply to the index of inventory 2 to instruct the reader to stop the process related to inventory 2. Exemplarily, after receiving the third message, the third device can reply to the index of inventory 1, the index of inventory 2, and the index of inventory 3 to instruct the reader to stop the processes of the three services.

[0136] In some implementations, the third message can include an indication to stop all service requests. For example, the third message can include a field "q-all" indicating that the associated process requests to stop all service requests. For example, the third device can reply "q-all" or "ok" or other indication message to indicate that the Reader can stop all service requests associated processes after receiving the third message.

[0137] In some implementations, the third message can include an indication to stop service requests. For example, the indication can be represented by a specific field. For example, when the Reader requests to stop one or more service requests, the Reader can send a second message to the third device including a specific field "10001", which can represent a request to stop the first service request and the fifth service request in sequence. For example, the third device can agree to stop the first service request after receiving the third message, and the third device can reply the first message including the indication to stop service requests, for example, the first message can include "10000".

[0138] In some implementations, the third message can include an index of service requests and an indication to stop service requests. For example, the index of service requests can be represented as {index 1, index 2, index 3, index 4}, and the indication can be a field "1111". For example, the third device can agree to the request of the first device after receiving the third message, and the third device can reply the first message including {index 1, index 2, index 3, index 4} and the stop indication field "1111".

[0139] In some implementations, the third message can include an index of A-IoT devices associated with service requests. Alternatively, the third message can include an index of A-IoT devices associated with service requests and an indication to stop service requests corresponding to the A-IoT devices. During the interaction between the Reader and the A-IoT devices, when a certain A-IoT device is not found for multiple times, the third message can no longer attempt to call the A-IoT device, and can send the index of the A-IoT device to the third device to request to stop the process associated with the A-IoT device. For example, the third device can reply the first message including the index of the A-IoT device when the third device agrees to the request of the first device after receiving the third message.

[0140] In some implementations, the third message can comprise an index of the application function AF requesting to stop the service. Alternatively, the third message can comprise an index of the application function AF requesting to stop the service and an indication of the service request corresponding to the application function AF, which can be represented by a field. For example, the third message can comprise {AF index 1, AF index 2} to request to stop the service request of the application function AF 1 and the service request of the application function AF 2. After receiving the third message, the third device can agree to stop the service request of the application function AF 1 and the service request of the application function AF 2, and if the service request of the application function AF 1 / AF 2 is received again, the third device can re-sign up with other Readers. For example, after receiving the third message, the third device can reply to the first message to continue the service of the application function AF 1, and the first message can comprise the index 1 of the AF 1.

[0141] In some implementations, the third message can comprise a service type corresponding to the service request. Alternatively, the third message can comprise a service type corresponding to the service request and an indication of the service request corresponding to the service type. The Reader can stop a certain type of service, for example, the Reader can request to stop the process related to the inventory service, and the Reader can send the service type of the inventory service.

[0142] Optionally, in the above various implementations, the third message can further comprise a reason for requesting to stop the service request. The reason for requesting to stop the service request can comprise any one of the following: the first device is disconnected, the first device is switched to a connection, the first device has energy saving needs, the load condition of the first device, and the temperature of the first device is greater than a preset temperature threshold.

[0143] For the UE reader, the Reader can no longer provide the service due to mobility, power, temperature, or service load, etc. For the base station reader, the Reader can no longer provide the service due to energy saving, temperature, or service load, etc. When sending the third message, the Reader can carry the reason for requesting to stop the service request in the third message, so that after receiving the third message, the third device can know the reason why the Reader can no longer provide the service, and then determine whether to accept the request of the Reader, and can also perform some other operations based on the reason for requesting to stop the service request.

[0144] In particular, the reason for the stop service request can be that the first device is disconnected or the first device switches connection. When the Reader is a UE Reader, since the UE Reader has mobility, it can be disconnected from the base station or switch connection during movement. During disconnection or switching connection, the Reader cannot provide services, so the Reader requests a stop service request. In one example, the third message can include an indication of a stop all service request and a first device disconnection, i.e., the Reader requests a stop all service request, and the reason is that the first device is disconnected. After the third device receives the third message, it can reply with an acknowledgement message.

[0145] The reason for the stop service request can be that the Reader has energy saving needs, such as the power of the UE Reader being less than a preset threshold, or the base station reader needing to save power consumption, so the Reader needs to stop some services to achieve the purpose of energy saving. The Reader can send a third message to the third device. After the third device receives the third message, it can reply according to the needs of each service. In one example, the third message can include the Reader having energy saving needs and the index of the service request, such as {index 1, index 2, index 3, index 4}. After the third device receives the third message, it finds that the service request corresponding to index 1 is urgently needed to be completed, the service request corresponding to index 1 needs to be continued, and the service requests corresponding to index 2, index 3, and index 4 can be stopped. Then, the third device can send a first message to the Reader, and the first message includes the index of the service request {index 2, index 3, index 4}, and can also include a stop indication. Alternatively, the third device finds that the service requests corresponding to index 1, index 2, index 3, and index 4 can all be stopped after receiving the third message. Then, the third device can send a first message to the Reader, and the first message includes the index of the service request {index 1, index 2, index 3, index 4}.

[0146] The reason for the stop service request can be that the temperature of the Reader is greater than a preset temperature threshold. In one example, the third message can include that the temperature of the Reader is greater than a preset temperature threshold and the service type corresponding to the service request, such as {inventory, positioning}, i.e., the Reader requests to stop all inventory service requests and all positioning service requests. After the third device receives the third message, it finds that inventory A in the inventory service request can be stopped, so the third device can send a first message to the Reader, and the first message can include the index of inventory A, i.e., an indication of the related process of the stop service request inventory A.

[0147] The reason for stopping the service request can be a load condition of the Reader. The load condition can be a large load. In an example, the third message can include the load condition of the Reader and a service type corresponding to the service request, such as {inventory, positioning}. After receiving the third message, the third device finds that more resources can be allocated for the inventory service and the positioning service can be stopped. Then, the third device can send the first message to the Reader, and the first message can include one or more indexes of the positioning service requests, i.e., indicating to stop the related processes corresponding to the positioning service requests. In addition, the third device can also send resource information and information indicating to continue the inventory service request to the Reader, so that the Reader can continue the inventory service request.

[0148] It should be noted that S504 and S505 are optional steps. In some implementations, during the process of the Reader providing services, it is found that the Reader itself has the aforementioned reason for stopping the service request, such as insufficient power or excessively high temperature, etc. The Reader can directly send the second information to the A-IoT device, or stop some related processes of the service request, i.e., S506 is executed after S503.

[0149] In some other implementations, during the process of the Reader providing services, it is found that the Reader itself has the aforementioned reason for stopping the service request, such as excessively large load, etc. The Reader can send the third message to the third device, and then without waiting for the reply of the third device, the Reader can send the second message to the A-IoT device, or stop some related processes of the service request, i.e., S504 is executed after S503, and S506 is executed after S504.

[0150] In some other implementations, the Reader sends the third message to the third device, and then waits for the first message in reply of the third device. After receiving the first message, the Reader sends the second message to the A-IoT device.

[0151] S506, the Reader sends the second message to the A-IoT device. The second message indicates to stop the related processes of the service request. Correspondingly, the A-IoT device receives the second message.

[0152] S507, after receiving the second message, the A-IoT device stops listening to subsequent R2D transmissions.

[0153] S503-S504 can refer to the content of S306-S307 described above. For brevity, details are not repeated here.

[0154] In some other implementations, after step S503 / S504 / S505, the Reader itself can stop the service request related procedure, and then stop listening to the subsequent R2D transmission if the A-IoT device does not receive the R2D transmission within a preset time period. Here, the foregoing content of S406-S407 can be referred to, and details are not described herein for brevity.

[0155] In summary, the embodiments of the present application provide a communication method. When there is a more urgent service requirement, the AF can issue a first message. After the Reader receives the first message, the Reader can stop the service request related procedure according to the indication of the first message. Further, the Reader can send a second message to the A-IoT device to instruct the A-IoT device to stop the service request related procedure. In this way, when there is a more urgent service requirement, the ongoing service request related procedure can be stopped, so that the Reader can perform the procedure of the more urgent service. If the A-IoT device can process multiple procedures in parallel, the A-IoT device can also avoid continuously listening to the subsequent signaling / transmission of the ongoing service request, thereby saving device energy consumption.

[0156] If the ongoing service request has exceeded the time limit given by the AF, the AF can issue a first message. After the Reader receives the first message, the Reader can stop the service request related procedure according to the indication of the first message. Further, the Reader can send a second message to the A-IoT device to instruct the A-IoT device to stop the service request related procedure. Alternatively, the Reader can stop the service request related procedure, and the A-IoT device can stop listening to the R2D transmission when the A-IoT device continuously does not receive the R2D transmission. In this way, the A-IoT device can avoid continuously listening to the subsequent signaling / transmission, thereby saving device energy consumption.

[0157] The Reader can autonomously stop the service request related procedure for some reason. At this time, the Reader can send a second message to the A-IoT device to instruct the A-IoT device to stop the service request related procedure, thereby avoiding the A-IoT device continuously listening to the subsequent signaling / transmission, thereby saving device energy consumption. The Reader can also send a stop request to a third device, and stop the service request or continue to complete the service request under the instruction of the third device.

[0158] It should be understood that, in various embodiments of the present application, the terms and / or descriptions of different embodiments can be consistent and can be referred to each other if there is no special description and logical conflict. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0159] The communication method provided by the embodiments of the present application is described above in combination with FIG. 1 to FIG. 5. The communication apparatus for executing the above communication method is described below.

[0160] Referring to FIG. 6, FIG. 6 is a schematic diagram of the communication apparatus provided by the present application. As shown in FIG. 6, the communication apparatus 600 can include a communication unit 610, and optionally further include a processing unit 620. The communication unit 610 can implement corresponding communication functions, which can be internal communication of the communication apparatus 600 or communication between the communication apparatus 600 and other apparatuses; the processing unit 620 can implement corresponding processing functions. The communication unit 610 can also be referred to as a communication interface or a transceiver unit. Optionally, the communication apparatus 600 can further include a storage unit, which can be used to store instructions and / or data, and the processing unit 620 can read the instructions and / or data in the storage unit, so that the communication apparatus 600 implements the foregoing method embodiments.

[0161] In a possible design, the communication apparatus 600 can be the first device in the above method embodiments, and can also be a module or a chip applied to the first device. The communication apparatus 600 can be used to execute the steps or processes performed by the first device in the above embodiments.

[0162] Specifically, the communication unit 610 is configured to: receive a first message, the first message indicating to stop a service request related process; and / or, send a second message, or stop the service request related process, the second message indicating to stop the service request related process.

[0163] In a possible design, the communication apparatus 600 can be the second device in the above method embodiments, and can also be a module or a chip applied to the second device. The communication apparatus 600 can be used to execute the steps or processes performed by the second device in the above embodiments.

[0164] Specifically, the communication unit 610 is configured to: stop listening to subsequent R2D transmissions if no R2D transmission is received within a preset time period.

[0165] Alternatively, the communication unit 610 is further configured to: receive a second message, the second message indicating to stop a service request related process; and stop listening to R2D transmissions of the service request related process after receiving the second message.

[0166] In a possible design, the communication apparatus 600 can be the third device in the above method embodiments, and can also be a module or a chip applied to the third device. The communication apparatus 600 can be used to execute the steps or processes performed by the third device in the above embodiments.

[0167] Specifically, the communication unit 610 is configured to receive a third message, the third message requesting to stop a procedure related to the at least one service request.

[0168] As to the steps or procedures performed by the units in the communication apparatus 600, reference can be made to the above method embodiments, and thus no further description is provided herein.

[0169] It should be understood that the units in the communication apparatus 600 can be implemented by hardware, or by software, or by a combination of hardware and software. For example, the units can be application specific integrated circuits (ASIC), electronic circuits, processors (shared, dedicated or group) and memory for executing software or firmware programs, integrated logic circuit(s), and / or other supported components to provide the described functionality. For example, the communication unit 610 can be replaced by a transceiver circuit (which can include a receiver circuit and a transmitter circuit), and the processing unit 620 can be replaced by a processor or processing circuit.

[0170] Referring to FIG. 7, FIG. 7 is a schematic diagram of a communication apparatus 700 according to an embodiment of the present application. The communication apparatus 700 can be a communication device, or a chip, chip system, or processor, etc. supporting the communication device to implement the above method. The communication device can be a terminal device, or a network device. The apparatus can be used to implement the method described in the above method embodiments, and reference can be made to the above method embodiments for details.

[0171] The communication apparatus 700 includes one or more processors 701, which can also be referred to as processing units, and can implement certain control functions. The processor 701 can be a general purpose processor or a dedicated processor, etc.

[0172] In an alternative design, the processor 701 can also store instructions and / or data, which can be executed by the processor 701, so that the communication apparatus 700 implements the method described in the above method embodiments.

[0173] Optionally, the communication apparatus 700 can include one or more memories 702, which can store instructions executable by the processor 701, so that the communication apparatus 700 implements the method described in the above method embodiments. Optionally, the memory 702 can also store data. Optionally, the processor 701 can also store instructions and / or data. The processor 701 and the memory 702 can be separately arranged, or integrated together.

[0174] In another alternative design, the communication device 700 can include a communication interface 703 for implementing the receiving and transmitting functions. For example, the communication interface 703 can be a transceiver circuit, an interface, an interface circuit, or a transceiver, etc. The transceiver circuit, the interface, the interface circuit, or the transceiver for implementing the receiving and transmitting functions can be separate or integrated together. The transceiver circuit, the interface, the interface circuit, or the transceiver described above can be used for reading and writing of codes / data, or the transceiver circuit, the interface, the interface circuit, or the transceiver described above can be used for transmission or transfer of signals.

[0175] Those skilled in the art can understand that, for the convenience of description, FIG. 7 only shows one memory and one processor. In actual devices, there can be multiple processors and memories. The memory can also be referred to as a storage medium or a storage device, etc., and the embodiments of the present application do not limit this.

[0176] It should be understood that, in a possible design, the steps in the method embodiments provided in the present application can be completed by integrated logic circuits of hardware in the processor or instructions in the form of software. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being completed by a hardware processor, or being completed by a combination of hardware and software modules in the processor. The software modules can be located in random access memories, flash memories, read-only memories, programmable read-only memories, electrically erasable programmable memories, registers, or other mature storage media in the art. The storage medium is located in the memory, and the processor reads information in the memory and combines hardware to complete the steps of the above method. To avoid repetition, they will not be described in detail here.

[0177] It should be noted that the processor in the embodiments of the present application can be an integrated circuit chip with a signal processing capability. In the implementation process, the steps of the above method embodiments can be completed by integrated logic circuits of hardware in the processor or instructions in the form of software.

[0178] In the embodiments of the present application, the processor can be a CPU, and the processor can also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being completed by a hardware decoding processor, or being completed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memories, flash memories, read-only memories, programmable read-only memories, electrically erasable programmable memories, registers, or other mature storage media in the art. The storage medium is located in the memory, and the processor reads information in the memory and combines hardware to complete the steps of the above method.

[0179] It should be understood that, in the embodiments of the present application, the memory can include read-only memory and random access memory, and provide instructions and data to the processor. The memory can also include non-volatile random access memory. The memory can be volatile memory or non-volatile memory, or can include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically EPROM (electrically EPROM, EEPROM) or flash memory. The volatile memory can be random access memory (random access memory, RAM) used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data date SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

[0180] The embodiments of the present application provide a communication network, including at least one application function entity, at least one network device and at least one read-write device, the application entity is used for executing the steps executed by the application function in the method embodiments, the network device is used for executing the steps executed by the core network in the method embodiments, and the read-write device is used for executing the steps executed by the reader in the method embodiments.

[0181] The embodiments of the present application provide a computer storage medium, the computer readable medium stores a computer program (also can be called code, or instruction), when the computer program runs on the computer, the computer executes the method of the embodiments of the present application.

[0182] The embodiments of the present application provide a computer program product containing instructions, the computer program product includes: a computer program (also can be called code, or instruction), when the computer program is executed, the computer executes the method of the embodiments of the present application.

[0183] The above-described embodiments can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, the above-described embodiments 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 or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions according to the embodiments of the present application are wholly or partially generated. 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 one website, computer, server, or data center to another website, computer, server, or data center through a wired (for example, infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium accessible by a computer or a data storage device such as a server, data center, etc. containing one or more available medium collections. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state disk.

[0184] Those skilled in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be realized in electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0185] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device, and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be described here.

[0186] In several embodiments provided in the present application, it should be understood that the disclosed system, device, and method can be implemented in other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices, or units, and can be electrical, mechanical, or other forms.

[0187] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0188] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present alone, or two or more units can be integrated in one unit.

[0189] If the functions are realized in the form of software functional units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the part of the present application that essentially contributes to the prior art or the part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0190] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method characterized by comprising: A first device applied to an environmental Internet of Things, the method comprising: receiving a first message indicating to stop a service request related process; and / or, sending a second message indicating to stop the service request related process, or stopping the service request related process.

2. The method of claim 1, wherein, The first message comprises at least one of the following: an index of the service request, an index of a second device, an indication to stop the service request related process, an indication to stop all service request related processes, a condition to stop the service request.

3. The method of claim 2, wherein, The condition to stop the service request comprises a completion progress and / or a stop time of the service request.

4. The method according to any one of claims 1 to 3, characterized in that, The second message comprises at least one of the following: an identifier of the first device, an index of the service request, an index of the service request related process, an index of a second device related to the service request, an indication to stop the service request related process, an indication to stop all service request related processes.

5. The method according to any one of claims 1 to 4, characterized in that, Before receiving the first message, the method further comprises: sending a third message requesting to stop at least one service request related process.

6. The method of claim 5, wherein, The third message comprises at least one of the following: an index of the service request, an index of a second device related to the service request, an index of an application function (AF) to stop the service request, a service type corresponding to the service request, a reason to stop the service request, an indication to stop all service requests.

7. The method of claim 6, wherein, The reason to stop the service request comprises at least one of the following: the first device is disconnected, the first device performs handover, the first device has energy saving demand, a load condition of the first device, a temperature of the first device is greater than a preset temperature threshold.

8. The method according to any one of claims 5 to 7, characterized in that, The first message indicates to stop at least one of the contents requested by the third message.

9. The method according to any one of claims 1 to 8, characterized in that, Before stopping the service request related process, the method further comprises: sending a fourth message indicating to stop listening to subsequent R2D transmissions if no R2D transmission is received within a preset time period.

10. A communication method characterized by comprising: A second device applied to an environmental Internet of Things, the method comprising: stopping listening to subsequent R2D transmissions if no R2D transmission is received within a preset time period; or, receiving a second message indicating to stop a service request related process; after receiving the second message, stopping listening to R2D transmissions of the service request related process.

11. The method of claim 10, wherein, The second message comprises at least one of the following: an identifier of a first device, an index of the service request, an index of the service request related process, an index of a second device related to the service request, an indication to stop the service request related process, an indication to stop all service request related processes.

12. The method according to claim 10 or 11, characterized in that, The method further comprises: receiving a fourth message indicating to stop listening to subsequent R2D transmissions if no R2D transmission is received within a preset time period.

13. A communication method characterized by comprising: A third device applied to an environmental Internet of Things, the method comprising: receiving a third message requesting to stop at least one service request related process.

14. The method of claim 13, wherein, The third message comprises at least one of the following: an index of the service request, an index of a second device related to the service request, an index of an application function (AF) that stops the service request, a service type corresponding to the service request, a reason for stopping the service request, an indication of stopping all service requests.

15. The method according to claim 13 or 14, characterized in that, The method further comprises: sending a first message indicating to stop at least one of the contents requested by the third message.

16. A communication device, characterized by comprises: a processor coupled with a memory, the memory being used to store programs or instructions, the programs or instructions being executed by the processor to make the communication device perform the method of any one of claims 1-9, or the method of any one of claims 10-12, or the method of any one of claims 13-15.

17. A communications device, characterized by comprises a processor and an interface used to send and / or receive signals, so that the processor performs the method of any one of claims 1-9, or the method of any one of claims 10-12, or the method of any one of claims 13-15.

Images