Communication method and apparatus

Abstract

Provided in the embodiments of the present application is a communication method. The method is applied to an access network device, and the method comprises: determining first configuration information, wherein the first configuration information is used for indicating a first resource, the first resource is used for communication between a first apparatus and a second apparatus, the first apparatus is an apparatus having a reader-writer function, and the second apparatus is an apparatus having a tag function; and sending the first configuration information to the first apparatus. A resource for communication with a second apparatus serving as a tag is allocated to a first apparatus serving as a reader-writer, so that an intermediate node can obtain a resource for an ambient Internet of Things service with the tag.

Description

A communication method and apparatus

[0001] The present application claims priority to the Chinese patent application No. 202410418584.8, filed on April 8, 2024, and entitled "A communication method and apparatus", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] Embodiments of the present application relate to the field of communication, in particular to a communication method and apparatus. BACKGROUND

[0003] With the development of communication technology, the 3rd generation partnership project (3GPP) defines ambient internet of things (AIoT) technology.

[0004] The communication system of AIoT in AIoT technology includes a reader-writer and a tag. The reader-writer can be implemented by a network device, such as a base station, and the tag can be implemented by an internet of things terminal, such as a passive / semi-passive / active tag. When the network device communicates with the tag through an intermediate node, that is, the intermediate node communicates with the tag as a reader-writer, the intermediate node cannot know which resource is used to communicate with the tag.

[0005] Therefore, how to enable the intermediate node to obtain the resource for communication with the tag becomes a problem to be solved. SUMMARY

[0006] The present application provides a communication method, which can enable the intermediate node to obtain the resource for communication with the tag.

[0007] In a first aspect, a communication method is provided, which is applied to an access network device, and the method comprises: determining first configuration information, wherein the first configuration information is used to indicate a first resource, and the first resource is used for a first device to send information to a second device, wherein the first device is a device with reader-writer function, and the second device is a device with tag function; and sending the first configuration information to the first device.

[0008] In the embodiments of the present application, the access network device configures the resource used for communication between the first device and the second device for the first device, so that the intermediate node of the access network device and the tag can obtain the communication resource, thereby ensuring that the AIoT service is performed between the reader-writer and the tag.

[0009] In combination with the first aspect, in some implementation manners of the first aspect, the method further comprises: receiving first request information from the first device, wherein the first request information is used to request the communication resource between the first device and the second device.

[0010] In some implementations of the first aspect, the first request information includes at least one of the following: a number of resource blocks (RBs) used by the first device to communicate with the second device or a time length used by the first device to communicate with the second device.

[0011] In the embodiments of the present application, the number of RBs used by the first device to communicate with the second device or the time length used by the first device to communicate with the second device is carried in the first request information, so that the access network device can allocate resources for AIoT services for the first device according to the estimated parameters.

[0012] In some implementations of the first aspect, the first request information includes information of a deployment mode requested by the first device, and the deployment mode includes at least one of the following: standalone deployment, in-band deployment, or guard-band deployment.

[0013] In the embodiments of the present application, the information of the deployment mode requested by the first device is carried in the first request information, so that the access network device can allocate resources for the first device according to the request of the first device.

[0014] In some implementations of the first aspect, the first request information includes a frequency band number supported by the first device or a frequency band number requested by the first device.

[0015] The frequency band number supported by the first device or the frequency band number requested by the first device is carried in the first request information, so that the access network device can indicate a suitable frequency band when allocating resources for the first device.

[0016] In some implementations of the first aspect, the method further includes: sending first service request information to the first device, and the first service request information includes first configuration information.

[0017] In the embodiments of the present application, the first configuration information can be sent together with the service request, which is more flexible in scheduling and saves signaling overhead compared with separate sending.

[0018] In some implementations of the first aspect, the first configuration information includes one or more of the following: frequency domain resource configuration information, time domain resource configuration information, or maximum power sent by the first device to the second device.

[0019] In some implementations of the first aspect, the frequency domain resource configuration mode includes at least one of the following: standalone deployment, guard-band deployment, or in-band deployment.

[0020] In a first aspect, in some embodiments of the first aspect, the information of the independently deployed frequency domain resource includes at least one of the following: frequency band or frequency range information, subcarrier spacing information, bandwidth information, frequency point information, RB configuration information; the information of the intra-band deployed frequency domain resource includes at least one of the following: for intra-band deployment: same frequency band or same frequency range indication, frequency band or frequency range information, subcarrier spacing information, bandwidth information, frequency point information, RB configuration information; or for inter-band deployment: frequency band or frequency range information, subcarrier spacing information, bandwidth information, frequency point information, RB configuration information; the information of the guard band deployed frequency domain resource includes at least one of the following: for LTE guard band deployment: LTE frequency band or frequency range information, LTE frequency point information, subcarrier spacing information, bandwidth information, frequency point information, LTE guard band configuration information, RB configuration information; or for NR guard band deployment: for intra-band deployment: same frequency band or same frequency range indication, NR frequency band or frequency range information, NR frequency point information, subcarrier spacing information, bandwidth information, frequency point information, NR guard band configuration information, RB configuration information; for inter-band deployment: NR frequency band or frequency range information, NR frequency point information, subcarrier spacing information, bandwidth information, frequency point information, NR guard band configuration information, RB configuration information.

[0021] With reference to the first aspect, in some implementations of the first aspect, the information of the independently deployed frequency domain resource includes at least one of: frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, start RB on bandwidth part BWP, RB offset on BWP, RB length on BWP, index of RB on BWP, RB position on BWP, maximum power of the first device for transmitting downlink information, start subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB, and position of subcarrier on RB; and the information of the intra-band deployed frequency domain resource includes at least one of: for intra-band deployment: intra-band or intra-band indication, frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, start RB on bandwidth part BWP, RB offset on BWP, RB length on BWP, index of RB on BWP, RB position on BWP, maximum power of the first device for transmitting downlink information, start subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB, and position of subcarrier on RB.or inter-frequency deployment: frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, starting RB on bandwidth part BWP, RB offset on BWP, RB length on BWP, index of RB on BWP, RB position on BWP, maximum power of the first device sending downlink information, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB, and position of subcarrier on RB; information of frequency domain resource of the guard band deployment, including at least one of the following information: LTE guard band deployment: FreqBandIndicatorEUTRA, MultiBandInfoListEUTR, eutraFrequency, ARFCN-ValueEUTRA, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, starting RB of guard band, RB offset of guard band, RB length of guard band, position of RB of guard band, index of RB of guard band, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB, and position of subcarrier on RB;Or NR guard band deployment: same frequency deployment: same frequency band or same frequency range indication, FreqBandIndicatorNR, MultiFrequencyBandListNR, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, Guardband configuration information, starting RB of guard band Guardband, RB offset of Guardband, RB length of Guardband, RB position of Guardband, RB index of Guardband, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB and position of subcarrier on RB, or different frequency deployment: FreqBandIndicatorNR, MultiFrequencyBandListNR, absoluteFrequencyPointA, ARFCN-ValueNR, scs-SpecificCarrierList, locationAndBandwidth, subcarrierSpacing, cyclicPrefix, Guardband configuration information, starting RB of guard band Guardband, RB offset of Guardband, RB length of Guardband, RB position of Guardband, RB index of Guardband, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB and position of subcarrier on RB.

[0022] With reference to the first aspect, in some implementations of the first aspect, the time domain resource of the first resource is a first time domain resource, and the method further includes: receiving second request information from the first device, the second request information being used to request a second time domain resource, wherein a range of the second time domain resource is greater than a range of the first time domain resource or the second time domain resource does not overlap with the first time domain resource.

[0023] In the embodiments of the present application, the first device can determine whether the configured resource is sufficient to complete the service, and can autonomously request additional time length, so as to ensure that the resource allocated to the first device can complete the communication service between the first device and the second device, and improve the reliability of the service.

[0024] With reference to the first aspect, in some implementations of the first aspect, the first resource is used for the first device to send data to the second device; and the method further includes: sending second configuration information to the first device, the second configuration information and the first configuration information being used to indicate a second resource, the second resource being used for the second device to send data to the first device.

[0025] In the embodiments of the present application, the uplink resource and the downlink resource can be configured separately, and the uplink resource used for sending uplink data to the access network device can adopt a default configuration, that is, only an adjustment value is indicated, so that the signaling overhead can be saved.

[0026] With reference to the first aspect, in some implementations of the first aspect, the method further includes: receiving third request information from the first device, the third request information being used to request to release the first resource.

[0027] In a second aspect, a communication method is provided, the method being applied to an access network device or a first device, and the method includes: obtaining first information used for charging of a communication between the first device and a second device; and sending the first information to a core network device. The first information includes one or more of a service type, a number of the second devices in stock, a service / task identifier, a number of the second devices in stock of the first device, a number of times of performing a stock service by the first device, a number of times of performing a reading service by the first device, a number of times of performing a writing service by the first device, a sequence number of an AIoT service, a time of reporting the AIoT service, a position of the first device, frequency domain resources configured for the first device, time domain resources configured for the first device, and maximum downlink transmission power of the first device, wherein the sequence number of the AIoT service is used to identify the AIoT service.

[0028] In the embodiments of the present application, the type of the service and the data amount of the type of the service of the communication between the first device and the second device are sent to the core network device, and the core network device can charge the service between the first device and the second device according to the type of the service and the data amount of the type of the service, so that the charging is more suitable for the service scenario.

[0029] With reference to the second aspect, in some implementations of the second aspect, the first device is a device with a reader / writer function, the second device is a device with a tag function, and the service between the first device and the second device is an environmental AIoT service.

[0030] In a third aspect, a communication method is provided, the method being applied to a first device, and the method includes: receiving first configuration information from an access network device, wherein the first configuration information is used to indicate a first resource, and the first resource is used for communication between the first device and a second device, wherein the first device is a device with a reader / writer function, and the second device is a device with a tag function; and determining the first resource according to the first configuration information.

[0031] In the embodiments of the application, the access network device configures a resource for the first device and the second device to communicate, so that the access network device and the intermediate node of the tag can obtain the communication resource, thereby ensuring that the AIoT service is performed between the reader and the tag.

[0032] With reference to the third aspect, in some implementations of the third aspect, the method further includes: sending first request information to the access network device, the first request information being used to request a communication resource between the first device and the second device.

[0033] With reference to the third aspect, in some implementations of the third aspect, the first request information includes at least one of the following information: a number of resource blocks (RBs) for the first device to communicate with the second device or a time length for the first device to communicate with the second device.

[0034] With reference to the third aspect, in some implementations of the third aspect, the first request information includes information of a deployment mode requested by the first device, and the deployment mode includes at least one of the following: independent deployment, in-band deployment, or guard-band deployment.

[0035] With reference to the third aspect, in some implementations of the third aspect, the first request information includes a frequency band number supported by the first device or a frequency band number requested by the first device.

[0036] With reference to the third aspect, in some implementations of the third aspect, the first configuration information includes one or more of the following: frequency domain resource configuration information, time domain resource configuration information, or maximum power sent by the first device to the second device.

[0037] With reference to the third aspect, in some implementations of the third aspect, the frequency domain resource configuration mode includes at least one of the following: independent deployment, guard-band deployment, or in-band deployment.

[0038] In some implementations of the third aspect, in combination with the third aspect, the information of the independently deployed frequency domain resource includes at least one of the following: frequency band or frequency range information, subcarrier spacing information, bandwidth information, frequency point information, RB configuration information; the information of the intra-band deployed frequency domain resource includes at least one of the following: for intra-band deployment: same frequency band or same frequency range indication, frequency band or frequency range information, subcarrier spacing information, bandwidth information, frequency point information, RB configuration information; or for inter-band deployment: frequency band or frequency range information, subcarrier spacing information, bandwidth information, frequency point information, RB configuration information; the information of the guard band deployed frequency domain resource includes at least one of the following: for LTE guard band deployment: LTE frequency band or frequency range information, LTE frequency point information, subcarrier spacing information, bandwidth information, frequency point information, LTE guard band configuration information, RB configuration information; or for NR guard band deployment: for intra-band deployment: same frequency band or same frequency range indication, NR frequency band or frequency range information, NR frequency point information, subcarrier spacing information, bandwidth information, frequency point information, NR guard band configuration information, RB configuration information; for inter-band deployment: NR frequency band or frequency range information, NR frequency point information, subcarrier spacing information, bandwidth information, frequency point information, NR guard band configuration information, RB configuration information.

[0039] In some implementations of the third aspect, in combination with the third aspect, the information of the independently deployed frequency domain resource includes at least one of: frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, a starting RB on a bandwidth part (BWP), an RB offset on the BWP, an RB length on the BWP, an index of an RB on the BWP, a location of the RB on the BWP, a maximum power of the first device for transmitting downlink information, a starting subcarrier on an RB, a subcarrier offset on the RB, a subcarrier length on the RB, an index of a subcarrier on the RB, and a location of the subcarrier on the RB; and the information of the intra-band deployed frequency domain resource includes at least one of: a same frequency deployment: a same frequency band or a same frequency range indication, frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, a starting RB on a bandwidth part (BWP), an RB offset on the BWP, an RB length on the BWP, an index of an RB on the BWP, a location of the RB on the BWP, a maximum power of the first device for transmitting downlink information, a starting subcarrier on an RB, a subcarrier offset on the RB, a subcarrier length on the RB, an index of a subcarrier on the RB, and a location of the subcarrier on the RB.or inter-frequency deployment: frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, starting RB on bandwidth part BWP, RB offset on BWP, RB length on BWP, index of RB on BWP, RB position on BWP, maximum power of the first device sending downlink information, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB, and position of subcarrier on RB; information of frequency domain resource of the guard band deployment, including at least one of the following information: LTE guard band deployment: FreqBandIndicatorEUTRA, MultiBandInfoListEUTR, eutraFrequency, ARFCN-ValueEUTRA, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, starting RB of guard band, RB offset of guard band, RB length of guard band, position of RB of guard band, index of RB of guard band, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB, and position of subcarrier on RB;or NR guard band deployment: same frequency band or same frequency band indication, FreqBandIndicatorNR, MultiFrequencyBandListNR, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, subcarrierSpacing, cyclicPrefix, Guardband configuration information, starting RB of guard band Guardband, RB offset of Guardband, RB length of Guardband, RB position of Guardband, RB index of Guardband, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB, and position of subcarrier on RB, or different frequency deployment: FreqBandIndicatorNR, MultiFrequencyBandListNR, absoluteFrequencyPointA, ARFCN-ValueNR, scs-SpecificCarrierList, locationAndBandwidth, subcarrierSpacing, cyclicPrefix, Guardband configuration information, starting RB of guard band Guardband, RB offset of Guardband, RB length of Guardband, RB position of Guardband, RB index of Guardband, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB, and position of subcarrier on RB.

[0040] With reference to the third aspect, in some implementations of the third aspect, a time domain resource of the first resource is a first time domain resource, and the method further includes: sending, to the access network device, second request information, the second request information being used to request a second time domain resource, wherein a range of the second time domain resource is greater than a range of the first time domain resource or the second time domain resource does not overlap with the first time domain resource.

[0041] With reference to the third aspect, in some implementations of the third aspect, the first resource is used for the first device to send data to the second device, and the method further includes: receiving second configuration information from the access network device, the second configuration information and the first configuration information being used to indicate a second resource, the second resource being used for the second device to send data to the first device.

[0042] With reference to the third aspect, in some implementations of the third aspect, the method further includes: sending, to the access network device, third request information, the third request information being used to request to release the first resource.

[0043] In a fourth aspect, a communication method is provided. The method includes: receiving first information from an access network device or a first device, the first information including one or more of a service type, a number of inventoried second devices, a service / task identifier, a number of inventoried second devices of the first device, a number of times the first device performs an inventory service, a number of times the first device performs a read service, a number of times the first device performs a write service, a sequence number of an AIoT service, a time of reporting the AIoT service, a location of the first device, frequency domain resources configured for the first device, time domain resources configured for the first device, and a maximum power of downlink transmission of the first device, wherein the sequence number of the AIoT service is used to identify the AIoT service, and determining charging information for communication between the first device and a second device based on the first information.

[0044] With reference to the fourth aspect, in some implementations of the fourth aspect, the first device is a device with a reader / writer function, the second device is a device with a tag function, and the service for communication between the first device and the second device is an environmental Internet of Things (AIoT) service.

[0045] In a fifth aspect, a communication method is provided. The method includes: obtaining, by a first device or an access network device, first information for charging for communication between the first device and a second device, wherein the first information includes one or more of a service type, a number of inventoried second devices, a service / task identifier, a number of inventoried second devices of the first device, a number of times the first device performs an inventory service, a number of times the first device performs a read service, a number of times the first device performs a write service, a sequence number of an AIoT service, a time of reporting the AIoT service, a location of the first device, frequency domain resources configured for the first device, time domain resources configured for the first device, and a maximum power of downlink transmission of the first device, wherein the sequence number of the AIoT service is used to identify the AIoT service; sending, by the first device or the access network device, the first information to a core network device; receiving, by the core network device, the first information from the access network device or the first device; and determining, by the core network device, charging information for communication between the first device and the second device based on the first information.

[0046] In a sixth aspect, a communication system is provided. The system includes: a core network device and a first device and / or an access network device, the first device and / or the access network device being configured to perform the method of any implementation of the second aspect, and the core network device being configured to perform the method of any implementation of the fourth aspect.

[0047] In a seventh aspect, a communication apparatus is provided, which comprises at least one processing circuitry configured to perform the method in any of the implementation forms of the first aspect to the fifth aspect.

[0048] In an implementation form, the apparatus is a communication device, such as a terminal device, or an access network device, or a device of a bearer core network element.

[0049] In another implementation form, the apparatus is a chip, chip system or circuitry for use in a communication device.

[0050] The communication apparatus can comprise a transceiver circuitry, which can be a transceiver when the apparatus is a communication device, or an interface circuitry or input / output circuitry when the apparatus is a chip, chip system or circuitry for use in a communication device.

[0051] Optionally, the at least one processing circuitry can be configured to execute computer programs or instructions stored in a memory to perform the method in any of the implementation forms of the first aspect or the second aspect. The memory can be located inside the communication apparatus, or outside the communication apparatus.

[0052] Optionally, the communication apparatus further comprises the memory.

[0053] In an eighth aspect, a processing circuitry (or processor) is provided, which is configured to perform the method in any of the implementation forms of the first aspect to the fifth aspect.

[0054] For the sending and obtaining / receiving operations involved in the processing circuitry (or processor), if not specially stated, or if not contrary to the actual role or inherent logic in the related description, it can be understood as the processing circuitry output and input operations, or the sending and receiving operations performed by the radio frequency circuitry and the antenna, which are not limited in the present application.

[0055] In a ninth aspect, a computer readable storage medium is provided, which stores program codes for execution by a device, and the program codes comprise instructions for performing the method in any of the implementation forms of the first aspect to the fourth aspect.

[0056] In a tenth aspect, a computer program product containing instructions which, when the computer program product is run on a computer, cause the computer to perform the method in any of the implementation forms of the first aspect to the fourth aspect.

[0057] In an eleventh aspect, a chip is provided, which includes a processing circuit and a communication interface. The processing circuit reads instructions stored on a memory through the communication interface, and executes the method provided in any of the implementation manners of any of the first aspect to the fourth aspect.

[0058] Optionally, as an implementation manner, the chip further includes a memory, and the memory stores a computer program or instructions. The processing circuit is configured to execute the computer program or instructions stored on the memory, and when the computer program or instructions are executed, the processing circuit is configured to execute the method provided in any of the implementation manners of any of the first aspect to the fourth aspect.

[0059] In a twelfth aspect, a communication system is provided, which includes the communication device described above, such as the communication device executing the method provided in any of the implementation manners of any of the first aspect to the fourth aspect. BRIEF DESCRIPTION OF DRAWINGS

[0060] FIG. 1 shows a schematic diagram of a network structure of an O-RAN.

[0061] FIG. 2 shows a function division of network elements and a protocol layer structure of an O-RAN device.

[0062] FIG. 3 shows a schematic diagram of a communication system suitable for use with the present application.

[0063] FIG. 4 shows a schematic diagram of another communication system suitable for use with the present application.

[0064] FIG. 5 shows a schematic diagram of another communication system suitable for use with the present application.

[0065] FIG. 6 shows a schematic diagram of another communication system suitable for use with the present application.

[0066] FIG. 7 is a schematic diagram of a communication method provided by an embodiment of the present application.

[0067] FIG. 8 is a schematic diagram of a communication method provided by another embodiment of the present application.

[0068] FIG. 9 is a schematic diagram of a resource configuration manner provided by an embodiment of the present application.

[0069] FIG. 10 is a schematic diagram of a resource configuration manner provided by another embodiment of the present application.

[0070] FIG. 11 is a schematic diagram of a resource configuration manner provided by another embodiment of the present application.

[0071] FIG. 12 is a schematic diagram of a flow of a communication method provided by another embodiment of the present application.

[0072] FIG. 13 is a schematic diagram of a communication device provided by an embodiment of the present application.

[0073] FIG. 14 is a schematic diagram of a communication device according to another embodiment of the present application. DETAILED DESCRIPTION

[0074] The terminology used in the following embodiments is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include both singular and plural forms, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It will be understood that the terms "and / or," "at least one of," and "one or more of" used herein in the disclosure refer to and encompass any one of or any combination of any number of the listed items. It will be further understood that terms, such as "first" and / or "second," etc., are used herein merely to define one element from another without necessarily requiring or implying any actual relationship or order between such elements. The terms "first" and / or "second," etc., are used herein merely to define one element from another without necessarily requiring or implying any actual relationship or order between such elements. The terms "comprises," "comprising," "attached," "connected," and "accessing" as used herein are used in the sense of "including," where the recited steps can be some or all of the inclusive steps or options and other steps can also be present.

[0075] The technical solutions provided by the embodiments of the present application can be applied to various communication systems, for example, can be an internet of things (IoT), a narrow band internet of things (NB-IoT), can be a 4th generation (4G) communication system (for example, long term evolution (LTE)), can also be a 5th generation (5G) communication system (for example, 5G new radio (NR)), can also be a mixed architecture of LTE and NR, can also be a 6G or a new communication system in future communication development, etc. The communication system can also include a machine to machine (M2M) network, machine type communication (MTC), or other networks. For example, the method provided by the embodiments of the present application can be applied to a communication system supporting ambient IoT (AIoT) or IoT technology.

[0076] The AIoT communication system in the embodiments of the present application can include a network device and a first type of terminal device. The first type of terminal device can be a device with a tag function, which can be an active, passive or semi-active tag. The AIoT architecture can include tags, readers and servers. The reader performs non-contact bidirectional data communication through wireless radio frequency, reads and writes electronic tags or tags through wireless radio frequency, so as to achieve the purpose of identifying targets and exchanging data. The main services include inventory, positioning, sensing, command, etc. Some examples of AIoT services are given. Inventory service: the inventory service can also be called the inventory operation, which can obtain the identification information of the tag, for example, the reader can obtain the identification information of the tag through the query, acknowledgment (ACK) and other commands. In order to facilitate the inventory of the tag, the tag includes S0-S3 a total of 4 session identifiers, each session identifier corresponds to two inventory states: A and B. The inventory state is indicated by the inventory flag (sessInventoried flag). When the reader selects a tag, the select command sent to it will carry a session identifier, and the tag will store the session identifier. When the reader performs the inventory service on the tag, the query command sent to it will include the session identifier, at this time the tag can flip the inventory state corresponding to the session identifier from A to B. If the reader sends the query command again to perform the inventory service, since the inventory state in the tag is B, the tag will not respond to the reader, thereby avoiding the same tag being inventoried multiple times in a round of inventory cycle. Read service: the read service can read the electronic product code (EPC) of the tag, the tag identifier (TID), the content stored in the reserved area of the tag or the content stored in the user storage area, etc. Write service: the write service can perform write operation on the storage area of the tag. Kill service: the kill service can make the tag never work. Lock service: the lock service can lock the information of the tag, which can prevent the read service or the write service on the tag. Alternatively, the lock service can also lock the storage area, which can prevent or allow the read service or the write service on the storage area. The above is only an example, the tag and the reader can also perform other services or operations, which will not be illustrated one by one here.The following briefly lists several application scenarios of AIoT: warehouse / transportation / materials: passive Internet of Things tags are embedded or attached to goods, and the goods are stored in warehouses, shopping malls, etc. During the logistics process, the goods-related information is automatically collected by the reader. The management personnel can quickly query the goods information in the system, reduce the risk of loss or theft, improve the goods handover speed, improve the accuracy, and prevent channeling and counterfeiting; fixed asset management: places such as libraries, art galleries, and museums that have a large number of assets or valuable items need complete management programs or strict protection measures. When the storage information of books or valuable items changes abnormally, the administrator will be reminded in the system in the first time, so as to handle the relevant situation; other scenarios, such as industrial manufacturing, identity recognition, environmental monitoring, etc.

[0077] When the present application is applied in an AIoT or IoT system, the reader and the tag device can be implemented based on the infrastructure in the cellular network. In other words, the reader and the tag can be devices in the cellular network. For example, the functions of the reader can be implemented by an access network device, such as a base station. The tag can be implemented by a terminal device in the cellular network, such as an extremely low-power, extremely low-complexity Internet of Things terminal. Non-contact data communication can be performed between the access network device and the terminal device, so as to read information from the terminal device and / or write information to be stored into the terminal device. It can be understood that, in the present application, the access network device can have the functions of the reader; the terminal device has the functions of the tag, or the terminal device can be a terminal device in the AIoT or IoT system.

[0078] The tag in the embodiments of the present application is an electronic tag or a radio frequency identification (RFID) tag. The tag can also be referred to as an AIoT terminal device or an AIoT device. In the present application, the tag can also be regarded as a kind of terminal device. The tag is a micro wireless transceiver device, mainly including a built-in tag device antenna, a coupling element, and a chip. The chip of the tag has a storage space that can support the reader to read or write tag data. After the tag receives the radio frequency signal sent by the reader through the antenna, the coupling element can be used to realize the coupling of the radio frequency signal, so as to provide energy to the chip of the tag in the coupling channel, and feed back the data stored in the chip to the reader through the antenna. In one classification manner, the types of tags can be divided into passive tags, semi-passive tags, and active tags. Among them, passive tags and semi-passive tags can use a backscatter-based communication mode, and active tags use a communication mode of actively generating a carrier wave.

[0079] In another classification, the tags can be divided into the following three types of devices:

[0080] Device A: no energy storage, cannot generate signals independently, uses backscatter to transmit signals;

[0081] Device B: has energy storage, but cannot generate signals independently, uses backscatter to transmit signals, and the stored energy can amplify the reflected signals;

[0082] Device C: has energy storage, can generate signals independently, and has active RF elements for transmission.

[0083] The tags use low-precision, low-power mid-low frequency ring oscillators or completely receive downlink signals without local oscillators. When the tag is working, the energy and carrier of the communication come from the reader, and the communication is based on the reflected carrier.

[0084] When the tag is passive, semi-active or semi-passive, it can receive or send data by obtaining energy. The way to obtain energy can be through radio frequency, radio, solar energy, light energy, wind energy, water energy, thermal energy, kinetic energy, etc. The application does not limit the way to obtain energy for passive, semi-active or semi-passive tags. It can be understood that when the terminal is a passive tag, the tag itself does not have or rely on a battery or other power supply device, but obtains energy from the environment for functions such as data sensing, transmission and distributed computing. When the tag is a semi-active terminal, the tag can have a built-in battery, but the battery is used to power the internal circuit and is not used to actively transmit signals. When the tag is a semi-passive tag, the tag can have a built-in capacitor; the capacitor can store the energy obtained by the tag; for example, the tag can obtain energy by obtaining solar energy and store it in the capacitor.

[0085] The reader / writer in the embodiments of the present application refers to a device that reads (and sometimes writes) tag information, and can also be understood as a device that communicates with a tag. The present application does not limit the name of the reader / writer, and the reader / writer can also be named as a reader or other names, that is, the terms of the reader / writer and the reader can be exchanged, and the reader has the functions involved in the reader / writer in the present application, such as the functions of performing the operations (such as obtaining tag information, inventory operation, read operation, write operation, invalidation operation, or message interaction operation with a tag, etc.) on a terminal (such as a tag) as described in the present application, the functions of obtaining charging-related information and / or charging information, and the function of sending charging information, etc. In a possible implementation manner, the reader can send instructions from a server or an application function to a tag, or the reader can send messages from a tag to a server or an application function. In a possible implementation manner, the reader can obtain the information stored in a specified tag according to the instructions issued by the server. For example, if it is an inventory operation (or can be referred to as an inventory operation), the reader obtains the identification information of the tag, which can be a unique identifier of the tag or a temporary identifier of the tag. For example, if it is a read operation, the reader reads the data in the storage area of the tag. Optionally, in some cases where the information stored in the tag needs to be rewritten, the reader also has the function of writing, for example, if it is a write operation, the reader writes data into the storage area of the tag. In addition, the reader can also perform an invalidation operation on the tag. After the invalidation operation is performed, the tag is invalidated and cannot be executed to obtain tag information, inventory operation, read operation, message interaction operation with a tag, or write operation, etc. In a possible implementation manner, the tag is invalidated and cannot be executed to obtain tag information, which can be understood as that after the tag is invalidated, the reader cannot obtain the tag information of the invalidated tag. In another possible implementation manner, the tag is invalidated and cannot be executed to perform message interaction operation with a tag, which can be understood as that after the tag is invalidated, the reader cannot perform message interaction with the invalidated tag. It can also be understood as a device that communicates with a tag, and the reader / writer can be a terminal device, an access network device, or a device with reading and writing functions, for example, a headend, a pico radio unit (PRU), a transmission reception point (TRP), etc. a node that sends a signal, or a device with reading and writing functions. It can also be an integrated access and backhaul (IAB) node or a smart repeater or a relay node, etc.

[0086] Some concepts of a communication system suitable for the embodiments of the present application will be described below in conjunction with FIG. 1 and FIG. 2.

[0087] In an embodiment of the present application, the access network device can be a device in a wireless network, and the access network device can also be referred to as a network device or a wireless access network device. For example, the access network device can be a radio access network (RAN) node that accesses a terminal device to a wireless network, and can also be referred to as a network device. The access network device includes but is not limited to: a base station, an evolved NodeB (eNodeB), a TRP, a next generation NodeB (gNB) in a 5th generation (5G) mobile communication system, an access network device in an open radio access network (O-RAN), a next generation base station in a 6th generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system, etc.; or can be a module or unit that completes part of the function of the base station, for example, can be a central unit (CU), a distributed unit (DU), a central unit control plane (CU-CP) module, or a central unit user plane (CU-UP) module, wherein the CU-CP is responsible for the control plane function, mainly including the radio resource control (RRC) and the packet data convergence protocol (PDCP) corresponding to the control plane (PDCP-C). The PDCP-C is mainly responsible for the encryption and decryption of the control plane data, integrity protection, data transmission, etc. The CU-UP is responsible for the user plane function, mainly including the service data adaptation protocol (SDAP) and the PDCP corresponding to the user plane (PDCP-U). The SDAP is mainly responsible for processing the data of the core network and mapping the flow to the bearer. The PDCP-U is mainly responsible for the encryption and decryption of the data plane, integrity protection, header compression, sequence number maintenance, data transmission, etc. The CU-CP and the CU-UP are connected through an E1 interface. The CU-CP represents the gNB connected to the core network through an NG interface, and connected to the DU through an F1 control plane (F1-C). The CU-UP is connected to the DU through an F1 user plane (F1-U). Of course, there is also a possible implementation that the PDCP-C is also in the CU-UP. The access network device can be a macro base station, a micro base station or an indoor station, and can also be a relay node or a donor node, etc.The specific technology and specific device form adopted by the access network device in the present application are not limited.

[0088] The access network device can also include an active antenna unit (AAU). The CU implements part of the functions of the gNB, and the DU implements part of the functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implements the functions of the RRC layer. The DU is responsible for processing physical layer protocols and real-time services, and implements the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. In some deployments, the CU can also be divided into a centralized unit control plane (CU-CP) node and a centralized unit user plane (CU-UP) node. Among them, the CU-CP is responsible for the control plane function, and the CU-UP is responsible for the user plane function.

[0089] The present application is also applicable to the O-RAN architecture. As shown in FIG. 1, the O-RAN system can include an access network device, a terminal device, and a core network device. The ORAN system can include other components in addition to the components shown in the figure. As shown, the access network device communicates with the core network (CN) device through a backhaul link and communicates with the user equipment through an air interface. For example, the baseband unit (BBU) in the access network device can communicate with the core network through the backhaul link, and the radio unit (RU) in the access network device can communicate with at least one UE through the air interface. The BBU communicates with at least one RU through a fronthaul link, and the BBU and the RU can be co-located or not co-located. The BBU includes at least one of at least one control unit and at least one distributed unit, which can communicate through at least one midhaul link. Among them, in the ORAN system, the CU can also be referred to as an open CU (O-CU), and the DU can also be referred to as an open DU (O-DU).

[0090] As shown in FIG. 2, a diagram of network element function division and protocol layer structure of an O-RAN device is shown. In some examples, the CU is a logical node that carries the RRC layer, SDAP layer, PDCP layer and other control functions of the access network device. The CU is connected to network nodes such as core network through some interfaces, which can be E2 interface and the like. Optionally, the CU can have part of the functions of the core network. The CU (e.g. PDCP layer and higher layer) is connected to the DU (e.g. RLC layer and lower layer) through some interfaces, which can be F1 interface and the like. In some examples, these interfaces (e.g. F1 interface) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g. interface management, system information management, UE context management, RRC message transmission, etc.). F1AP is the application protocol of F1 interface, which defines the signaling procedures of F1 in some examples. The F1 interface supports control plane F1-C and user plane F1-U. In some examples, the CU-CP can interact with the network element in the core network for implementing control plane functions. The network element in the core network for implementing control plane functions can be an access and mobility function network element, such as the access and mobility management (AMF) in the 5G system. The AMF network element is responsible for mobility management in the mobile network, such as location update of terminal devices, registration network of terminal devices, handover of terminal devices, etc. The CU-UP is a logical node that carries the SDAP layer and the PDCP-U (user plane part of PDCP) layer, and is used to implement the user plane function of the CU. The CU-UP can interact with the network element in the core network for implementing user plane functions. The network element in the core network for implementing user plane functions, for example, the user plane function (UPF) in the 5G system, is responsible for forwarding and receiving data in the terminal device. The above configuration of CU and DU is only an example, and the CU and DU can be configured to have functions as needed. For example, the CU or DU can be configured to have more protocol layer functions, or the CU or DU can be configured to have part of the processing functions of the protocol layer. For example, part of the functions of the RLC layer and the functions of the protocol layer above the RLC layer are arranged in the CU, and the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are arranged in the DU. For another example, the functions of the CU or DU can be divided according to the service type or other system requirements, for example, according to the delay requirement, the functions that need to meet the delay requirement are arranged in the DU, and the functions that do not need to meet the delay requirement are arranged in the CU.

[0091] The DU and the RU can or can not be co-located. The DU and the RU exchange control-plane and user-plane information via lower-layer split control user synchronous-plane (LLS-CUS) interface over a fronthaul link. The LLS-CUS can include LLS-C interface and LLS-U interface that provide control-plane (C-Plane) and user-plane (U-Plane), respectively. In some examples, the control-plane refers to real-time control between the DU and the RU. The DU and the RU have LLS-M interface of the fronthaul link to exchange management information, and the management-plane (M-Plane) refers to non-real-time management operation between the DU and the RU. The DU and the RU can cooperate to jointly implement the functionality of the PHY layer. One DU can be connected to one or more RUs. The functionality of the DU and the RU can be configured in multiple ways according to design. For example, the DU is configured to implement baseband functionality, and the RU is configured to implement intermediate radio frequency functionality. For another example, the DU is configured to implement high-layer functionality in the PHY layer, and the RU is configured to implement low-layer functionality in the PHY layer or implement the low-layer functionality and radio frequency functionality. The high-layer functionality in the PHY layer can include a portion of the functionality of the PHY layer that is closer to the MAC layer, and the low-layer functionality in the PHY layer can include another portion of the functionality of the PHY layer that is closer to the intermediate radio frequency side.

[0092] The terminal device involved in the embodiments of the present application can be a wireless terminal device capable of receiving network device scheduling and indication information. The terminal device can also be referred to as a terminal device, a user equipment, a terminal, a mobile station (MS), a mobile terminal (MT), etc. The terminal device can be a device including a wireless communication function (providing voice / data connectivity to a user). For example, a handheld device with wireless connection function, or a vehicle-mounted device, a vehicle-mounted module, etc. At present, some examples of terminal devices are: 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 vehicle networking, a wireless terminal in self driving, a wireless terminal in remote medical surgery, 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, a device-to-device (D2D) terminal device, a vehicle-to-everything (V2X) communication terminal device, a smart vehicle, a telematics box (T-box), a machine-to-machine / machine type communication terminal device, an Internet of Things terminal device, etc. For example, the terminal device can be a vehicle-mounted device, a whole vehicle device, a vehicle-mounted module, a vehicle, an on board unit (OBU), a roadside unit (RSU), a T-box, a chip or a system on chip (SOC), etc. The above-mentioned chip or SOC can be installed in a vehicle, an OBU, an RSU or a T-box. The wireless terminal in industrial control can be a camera, a robot, etc. The wireless terminal in smart home can be a television, an air conditioner, a sweeping machine, a sound box, a set-top box, etc.The terminal device can also be a V2X device, for example, a smart car or an intelligent car, a digital car, an unmanned car or a driverless car or a pilotless car or an automobile, a self-driving car or an autonomous car, a pure EV or a Battery EV, a hybrid electric vehicle (HEV), a range extended EV (REEV), a plug-in HEV (PHEV), a new energy vehicle, a road site unit (RSU). The terminal device can also be a device in device to device (D2D) communication, for example, an electricity meter, a water meter, etc. It can also be a relay node or an intermediate node.

[0093] The core network device in the embodiments of the present application can be a general term of various functional entities used by the network side to manage users, data transmission and base station configuration, including AMF, UPF, session management function (SMF), tag management function (TMF), charging trigger function (CTF), charging trigger function / accounting data forwarding (CTF / ADF) and charging function (CHF), etc.

[0094] Among them, the CHF is responsible for generating a call detail record (CDR) or a bill, which can also be called a charging data report (CDR), and transmitting it to a charging gateway function (CGF), and finally creating a CDR file by the CGF and forwarding it to a charging accounting domain related processing device; at the same time, the CHF is the quota control node of online charging, which performs the rate processing of online charging for various services of the user, and completes the real-time settlement of the user's cost.

[0095] The above functions can be network elements in a hardware device, or software functions running on a dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). The above functions can be divided into one or more services, and further, services independent of the network functions can also exist. In this application, an instance of the above function, or an instance of a service included in the above function, or an instance of a service independent of the network function can be referred to as a service instance.

[0096] In the above embodiments, the AMF, SMF, UPF, TMF, etc. can be understood as network elements in the core network for implementing different functions, which can be combined into network slices as needed, for example. These core network network elements can be independent devices or can be integrated into the same device to implement different functions, which is not limited in this application. It should be noted that the above "network element" can also be referred to as an entity, device, apparatus, or module, etc., which is not particularly limited in this application.

[0097] It should also be understood that the above naming is only used to distinguish different functions and does not represent that these network elements are independent physical devices. The specific form of the network element is not limited in this application, for example, they can be integrated in the same physical device or can be different physical devices. In actual deployment, network elements or devices can be combined. For example, an access and mobility management network element can be combined with a session management network element; a session management network element can be combined with a user plane network element. When two network elements are combined, the interaction between the two network elements provided in the embodiments of this application becomes an internal operation of the combined network element or can be omitted. In addition, the above naming is only used to distinguish different functions and should not constitute any limitation on this application. This application does not exclude the possibility of using other names in 5G networks and future other networks. For example, in a 6G network, part or all of the above network elements can use the terms in 5G or other names, etc. A unified description is made here and will not be repeated below.

[0098] In addition, the names of the messages (or signaling) transmitted between the above network elements are only examples and do not constitute any limitation on the functions of the messages themselves.

[0099] The following describes an example of a communication system suitable for this application with reference to FIGS. 3 to 6.

[0100] FIG. 3 shows a schematic diagram of a communication system suitable for this application. As shown in FIG. 3, the communication system includes an access network device and a tag. The tag can be a separate device, or the tag can be integrated with a terminal device, i.e., the tag is part of the terminal device. In this communication system, the access network device can have the function of a reader in an RFID system, and the access network device can communicate with the tag as a reader. The communication interface between the access network device and the tag is a uu interface, i.e., air interface communication.

[0101] FIG. 4 shows a schematic diagram of another communication system suitable for use in the present application. As shown in FIG. 4, the communication system includes a terminal device and a tag. The tag can be a standalone device, or the tag can be integrated with the terminal device. In the communication system, the terminal device can have the function of a reader / writer in an RFID system, i.e., the terminal device can communicate with the tag as a reader / writer, and the terminal device and the tag can communicate through a sidelink.

[0102] FIG. 5 shows a schematic diagram of another communication system suitable for use in the present application. As shown in FIG. 5, the communication system includes an access network device, an IAB node, and a tag. The communication system can also include other devices, such as a terminal device. In the communication system, the access network device can have the function of a reader / writer in an RFID system, the IAB node can act as a relay node between the access network device and the tag, the tag transmits information to the IAB node, and the IAB node forwards the information to the access network device through a uu interface. The tag can be connected to the IAB node through the uu interface, and the IAB node can be connected to the base station through the uu interface.

[0103] In the present application, the communication system including the access network device, the terminal device, and the tag can also be a system with a split architecture. In the communication system, as shown in FIG. 6, the access network device and the terminal device can directly communicate with each other. The access network device can also have the function of a reader / writer in an RFID system, there is an uplink connection between the tag and the access network device, and there is a downlink connection between the tag and the terminal device. The terminal device can transmit information to the tag, and the tag can forward the information to the access network device. Alternatively, there is a downlink connection between the tag and the access network device, and there is an uplink connection between the tag and the terminal device. The access network device can transmit information to the tag, and the tag can forward the information to the terminal device. The energy required by the tag to transmit information can be provided by an energy signal, which can come from the access network device, the terminal device, or other devices. The energy signal can also be referred to as an excitation signal.

[0104] In a system of a split architecture, in one implementation, a terminal device can send data to a tag. The terminal device or an access network device provides a carrier signal, the tag generates or sends an uplink signal according to the carrier signal, and sends the uplink signal to the access network device. The uplink signal can include data sent by the tag to the access network device. The data can be data of the tag itself or data received from the terminal device. In another implementation, the access network device can send data to the tag. The terminal device or the access network device provides a carrier signal, the tag generates a downlink signal according to the carrier signal, and sends the downlink signal to the terminal device. The downlink signal can include data sent by the tag to the terminal device. The data can be data of the tag itself or data received from the access network device.

[0105] There is also a direct connection architecture, in which the tag and the access network device can directly transmit data. When the tag sends an uplink signal to the access network device, the carrier signal used to generate the uplink signal is provided by the terminal device.

[0106] In the above communication system, in a scenario where the access network device communicates with the tag through an intermediate node, such as a relay, an IAB, a terminal device, etc., the intermediate node communicates with the tag to perform AIoT business. In the current solution, there is no introduction on how to configure resources dedicated to AIoT business for the intermediate node.

[0107] The present application provides a communication method, which can allocate resources for the intermediate node performing AIoT business to communicate with the tag.

[0108] Please refer to FIG. 7 and FIG. 8.

[0109] FIG. 7 is a schematic diagram of a communication method according to an embodiment of the present application. FIG. 8 is a schematic diagram of a communication method according to another embodiment of the present application.

[0110] As shown in FIG. 7, the communication method can allocate resources for the intermediate node performing AIoT business.

[0111] S310, the access network device sends first configuration information to the first device, and correspondingly, the first device receives the first configuration information from the access network device.

[0112] The first configuration information can be determined by the access network device, and is used to indicate the first resource. The first resource is used for the first device to send information to the second device.

[0113] The first device can be a device with a reader / writer function, such as a relay, an IAB node, a terminal device, etc.

[0114] The second device can have a tag function, can be a terminal device with a tag function, or can be a terminal device in an AIoT or IoT system.

[0115] After the first device receives the first configuration information from the access network device, the first device can determine the first resource according to the first configuration information, so as to obtain a communication resource between the first device and the second device.

[0116] In the embodiments of the present application, the access network device configures the first device with a resource used for communication between the first device and the second device, so that the intermediate node of the access network device and the tag can obtain a communication resource dedicated to AIoT, thereby ensuring AIoT services between the reader / writer and the tag.

[0117] The process in which the access network device sends the first configuration information to the first device to allocate a resource to the first device can be performed in two ways.

[0118] In the first way, as shown in FIG. 7, the first device sends first request information to the access network device, and the access network device receives the first request information from the first device. The first request information is used to request a communication resource for the first device to send information to the second device.

[0119] In some possible embodiments, the access network device sends second service request information to the first device, and the first device receives the second service request information. The second service request information can be used to request the first service.

[0120] The first service includes one or more of the following: paging service, positioning service, location reporting service, inventory service, sensing service, command service, reading service, writing service, and deactivation service.

[0121] Optionally, the core network device sends first service request information to the access network device, and the access network device receives the first service request information. The second service request information can include the first service request information. The first service request information can also be sent by the core network device and transmitted to the first device through the access network device, for example, the first service request information is carried by a NAS message.

[0122] The core network element that can be involved can be a TMF or AMF or an ambient IoT management function (AIoTMF), or other network element, which is not limited in the application. For example, if the core network element involved is a TMF network element, it can be understood that the TMF network element assumes (part of) the function of the AMF network element, and the TMF network element can send a service request to the AMF network element after receiving the AIoT service request. If the core network element is an AMF network element, the AMF network element can directly receive the service request from the server.

[0123] Optionally, S301, the server sends the first service request information to the core network device, that is, the first service request information sent by the core network device to the access network device can come from the server.

[0124] In some possible embodiments, when the first device is a direct APP, the first service request information can be sent to the terminal device through the APP, and the first service request information is transmitted to the first device through the access network device.

[0125] In some possible embodiments, the first request information can include at least one of the following information: the number of resource blocks (RBs) for communication between the first device and the second device or the duration of communication between the first device and the second device.

[0126] The number of RBs for communication between the first device and the second device can be the number of RBs for AIoT service between the first device and the second device, and the duration of communication between the first device and the second device can be the duration of AIoT service between the first device and the second device.

[0127] The time unit of the duration can be a frame or a subframe or a superframe, such as xx frames (or subframes or superframes); can also be a time slot, such as xx time slots; or can be an absolute time unit, such as xx minutes, xx seconds, xx milliseconds, etc. Alternatively, the duration can also be represented by time information (such as x o'clock x minutes x seconds), etc., which is not limited in the application.

[0128] For example, the number of second devices in communication with the first device can refer to the estimated number of second devices inventoried through inventorying services. The method for estimating the number of second devices is not limited in the embodiments of the application, for example, the estimated number of second devices can be obtained by sensing the reference signal.

[0129] The method for obtaining the number of resource blocks (RBs) for communication between the first device and the second device or estimating the duration of communication between the first device and the second device is not limited in the embodiments of the application, for example, the number of resource blocks (RBs) for communication between the first device and the second device can be estimated according to the estimated number of second devices inventoried through inventorying services, or the duration of communication between the first device and the second device can be estimated according to the type of service.

[0130] In the embodiments of the present application, the access network device can allocate resources for AIoT services for the first device according to the estimated parameters by carrying the number of resource blocks (RBs) for communication between the first device and the second device or the duration of communication between the first device and the second device in the first request information.

[0131] In some possible embodiments, the first request information can include information of a deployment mode supported by the first device, and the deployment mode includes at least one of the following: standalone deployment (Standalone), in-band deployment (In-band), or guard band deployment (Guard band).

[0132] The resources requested by the first request information are for the second device, and the deployment mode is also for deployment of the second device.

[0133] The access network device can allocate resources for AIoT services for the first device according to the capability of the first device by carrying the information of the deployment mode supported by the first device in the first request information.

[0134] In some possible embodiments, the first request information can include information of a deployment mode indicated or requested by the first device, and the deployment mode includes at least one of the following: standalone deployment, in-band deployment, or guard band deployment.

[0135] In the embodiments of the present application, the access network device can allocate resources for the first device according to the request of the first device by carrying the information of the requested deployment mode of the first device in the first request information.

[0136] In some possible embodiments, the first request information can include a frequency band number supported by the first device or a frequency band number requested by the first device.

[0137] The access network device can indicate a suitable frequency band when allocating resources for the first device by carrying the frequency band number supported by the first device or the frequency band number requested by the first device in the first request information.

[0138] Optionally, the core network device sends first service request information to the access network device, and the access network device receives the first service request information from the core network device, as shown in FIG. 8.

[0139] Optionally, the second service request information can include the first service request information. That is, the access network device can directly transmit the first service request information sent by the core network device to the first device, and then separately send the first configuration information; or the access network device can simultaneously carry the service request information and the first configuration information in the second service request information.

[0140] The type of the message carrying the first service request information is not limited, for example, in the NR system, the message carrying the first service request information can be an N2 message.

[0141] Optionally, the server sends the first service request information to the core network device, that is, the first service request information sent by the core network device to the access network device can come from the server.

[0142] In the embodiment of the application, the first configuration information can be sent together with the first service request information, which is more flexible in scheduling and saves signaling overhead compared with separate sending.

[0143] In a possible embodiment, the first configuration information can include one or more of the following: frequency domain resource configuration information, time domain resource configuration information, or maximum power sent by the first device to the second device.

[0144] In a possible embodiment, the frequency domain resource configuration mode includes at least one of the following: independent deployment, guard band deployment, or intra-band deployment.

[0145] The resource configured in the first configuration information is configured for the second device, and the frequency domain resource configuration mode is also deployed for the second device.

[0146] For example, as shown in FIG. 9, the configured frequency domain resource can be indicated by independent deployment (Standalone), for example, the information of the independent deployment frequency domain resource includes one or more of the following fields to indicate the frequency domain resource for AIoT service:

[0147] One or more of frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, or multiBandInfoList indicates a list containing a frequency band to which the carrier belongs, in the embodiment of the application, the field can indicate a list containing a frequency band to which the frequency of the carrier belongs.

[0148] One or more of absoluteFrequencyPointA or ARFCN-ValueNR indicates the absolute frequency position of the reference resource block, and its lowest subcarrier is also called point A, in the embodiment of the application, the field can indicate the absolute frequency position of the frequency of the carrier.

[0149] The scs-SpecificCarrierList indicates a carrier set of different numerologies. The carrier set is defined relative to point A. In the embodiments of the present application, the field can configure one specific carrier (scs-SpecificCarrier) for each numerology used in the bandwidth part (BWP) corresponding to the carrier.

[0150] The locationAndBandwidth indicates the frequency domain location and bandwidth corresponding to the BWP. In the embodiments of the present application, the field can indicate the frequency domain location and bandwidth corresponding to the BWP corresponding to the carrier.

[0151] The subcarrierSpacing indicates the subcarrier spacing.

[0152] The cyclicPrefix indicates whether the BWP uses an extended cyclic prefix, etc.

[0153] The BWP configuration information can be one or more of the locationAndBandwidth, the subcarrierSpacing, or the cyclicPrefix.

[0154] Optionally, in addition to the above fields, the information of the frequency domain resource indicated by the independently deployed manner can also include RB configuration information, and the RB configuration information can include at least one of the following: a starting RB on the bandwidth part BWP, an RB offset on the BWP, an RB length on the BWP, an index of the RB on the BWP, an RB position on the BWP, a maximum power of the first device sending downlink information, a starting subcarrier on the RB, a subcarrier offset on the RB, a subcarrier length on the RB, an index of the subcarrier on the RB, and a position of the subcarrier on the RB. The shaded part in FIG. 9 is a schematic of one or more RBs configured on the BWP for AIoT service.

[0155] For example, as shown in FIG. 10, the configured frequency domain resource can be indicated by in-band deployment, for example, the frequency domain resource can be configured by intra band and / or inter band. For intra band, one or more fields / indication information listed in the above-mentioned standalone mode and the same frequency band indication can be used for configuration, which will not be described herein. Alternatively, the BWP for AIoT service can be configured by BWP configuration information; the RB for AIoT service can also be configured by RB configuration information; for inter band, one or more frequency bands for AIoT service can be indicated by frequencyBandList, and then one or more fields / indication information listed in the above-mentioned standalone mode can be combined, which will not be described herein. Alternatively, the BWP and / or RB for AIoT service can be configured in the indicated frequency band by combining the BWP and / or RB configuration information. For example, the shaded part in (a) of FIG. 10 represents the BWP for AIoT service configured in frequency band A, the shaded part in (b) of FIG. 10 represents one or more RBs for AIoT service configured in frequency band A, the shaded part in (c) of FIG. 10 represents the BWP for AIoT service configured in frequency band A and frequency band B, and the shaded part in (d) of FIG. 10 represents one or more RBs for AIoT service respectively configured in frequency band A and frequency band B. In addition, it is also feasible to respectively configure the BWP and / or one or more RBs for AIoT service in multiple frequency bands. For example, the BWP is configured in frequency band A, and one or more RBs for AIoT service are configured in frequency band B.

[0156] Alternatively, in addition to the above fields, the information of the frequency domain resource of the first resource indicated by in-band deployment can include RB configuration information, and the RB configuration information can include at least one of the following: the starting RB on the bandwidth part BWP, the RB offset on the BWP, the RB length on the BWP, the index of the RB on the BWP, the position of the RB on the BWP, the maximum power of the first device sending downlink information, the starting subcarrier on the RB, the subcarrier offset on the RB, the subcarrier length on the RB, the index of the subcarrier on the RB, and the position of the subcarrier on the RB.

[0157] For example, as shown in FIG. 11, the configured frequency domain resource can be indicated by guard band, for example, one or more fields / information listed in the above-mentioned standalone mode can be used for configuration, which will not be described herein. For another example, the frequency domain resource can be configured by LTE guard band or NR guard band. For example, for LTE guard band, the specified frequency band can be indicated by FreqBandIndicatorEUTRA, the frequency point information can be obtained by eutraFrequency, the bandwidth configuration information can be obtained by locationAndBandwidth, and the starting RB and / or the RB length of the guard band can be indicated by guard band configuration information. The frequency domain resource for AIoT service can be configured by one or more of the above configuration information. For example, for the same frequency band deployment of NR guard band, i.e., the NR guard band and the current terminal device work in the same frequency band, the same frequency band can be indicated by the same frequency band indication, the specified frequency band can be indicated by FreqBandIndicatorNR, the frequency point information can be obtained by ARFCN-ValueNR, the bandwidth configuration information can be obtained by locationAndBandwidth, and the starting RB or RB offset of the guard band and / or the RB length of the guard band can be indicated by guard band configuration information. For the different frequency band deployment of NR guard band, i.e., the NR guard band and the current terminal device work in different frequency bands, the specified frequency band can be indicated by FreqBandIndicatorNR, the frequency point information can be obtained by ARFCN-ValueNR, the bandwidth configuration information can be obtained by locationAndBandwidth, and the starting RB and / or the RB length of the guard band can be indicated by guard band configuration information, for example, the shadow part in FIG. 11 represents one or more RBs configured for AIoT service in the first guard band.

[0158] Optionally, in addition to the above fields, the information of the frequency domain resource of the first resource indicated by the way of deploying the guard band can include RB configuration information, and the RB configuration information can include at least one of the following: a starting RB of the guard band, an RB offset of the guard band, an RB length of the guard band, a position of the RB of the guard band, an RB index of the guard band, a starting subcarrier on the RB, a subcarrier offset on the RB, a subcarrier length on the RB, an index of the subcarrier on the RB, and a position of the subcarrier on the RB.

[0159] The above embodiments enumerate the fields, and any other fields used to implement the functions of the above example fields also belong to the scope disclosed by the embodiments of the present application.

[0160] Optionally, S320, the first device sends second request information to the access network device, and correspondingly, the access network device receives the second request information from the first device.

[0161] The second request information is used to request a time domain resource. The requested time domain resource can be an increased time domain resource, or a separately requested time domain resource.

[0162] For example, the time domain resource of the first resource is T1, the requested time domain resource can be a separately configured T2, or an additional increase t based on T1, that is, the final obtained time domain resource is T1+t.

[0163] The first device can determine that the first resource is insufficient to complete the AIoT service with the second device, at which time the first device can request an additional time length from the access network device through the second request information.

[0164] In the embodiments of the present application, the first device can determine whether the configured resource is sufficient to complete the service and can autonomously request an additional time length, ensuring that the resource allocated to the first device can complete the communication service between the first device and the second device, and improving the reliability of the service.

[0165] The first device sends third request information, and correspondingly, the access network device receives the third request information.

[0166] The third request information can be used to request a second resource, and the second resource is used for the second device to send information to the first device, that is, the third request information can be used to request an uplink resource.

[0167] As a possible embodiment, the first request information in the above embodiments can also request an uplink resource for the second device at the same time, that is, the uplink and downlink resources can be requested at the same time, that is, the first request information includes the third request information.

[0168] The resource configuration manner in the above embodiments can also be simultaneously applicable to configuring uplink resources for the second device, that is, the uplink and downlink resources can be configured separately.

[0169] Optionally, when the uplink and downlink operating frequency bands are consistent, a default (delta) configuration can be performed. S330, the access network device sends second configuration information to the first device, and correspondingly, the first device receives the second configuration information.

[0170] As a possible embodiment, the second configuration information and the first configuration information are used to indicate third resources, wherein the third resources are used for the second device to send information to the first device. That is, the third resources are uplink resources of the second device, and the uplink resources can be indicated in a default configuration manner.

[0171] As another possible embodiment, the second configuration information can separately indicate the third resources, that is, the uplink resources are independently configured.

[0172] Optionally, the second configuration information and the first configuration information can be sent simultaneously or in different messages.

[0173] Optionally, the first configuration information includes the second configuration information.

[0174] Optionally, the second configuration information can include one or more of frequency adjustment information, time domain adjustment information, or maximum transmission power adjustment information of the first device sending uplink data to the access network.

[0175] The frequency adjustment information can be a frequency adjustment value (or frequency change value / offset value), which indicates that the frequency is adjusted (or decreased) by the adjustment value, wherein the adjustment value can be greater than 0 or less than 0. The frequency adjustment value unit can be Hertz (Hz) / kilohertz (kHz) / band / carrier / BWP / RB / subcarrier, etc. For example, the number of RBs of the first resource is N, and the RB adjustment value is n, then the number of RBs of the third resource can be N+n or N-n.

[0176] The time domain adjustment information can be a time domain adjustment value (or time domain change value / offset value), which indicates that the time domain is adjusted (or decreased) by the adjustment value, wherein the adjustment value can be greater than 0 or less than 0. The time domain adjustment value unit can be frame / subframe / hyperframe / slot, or in absolute time units such as xx minutes, xx seconds, xx milliseconds, etc. For example, the time length of the first resource is T slots, and the slot adjustment value is t, then the time length of the third resource can be T+t slots or T-t slots.

[0177] The first device sends the maximum transmission power adjustment information of the uplink data to the access network, which can be a power adjustment value (or a power change value / offset value). The power adjustment value indicates that the power is adjusted up (or down) by the adjustment value, wherein the adjustment value can be greater than 0 or less than 0. The unit of the power adjustment value can be dBm, etc. For example, the maximum transmission power of the first device for sending downlink data is P, and the power adjustment value is p. The maximum transmission power of the first device for sending uplink data to the access network can be P+p or P-p.

[0178] In the embodiments of the present application, the uplink and downlink resources can be configured separately. The uplink resource for sending uplink data to the access network device can use the default configuration, i.e., only the adjustment value is indicated, thereby saving signaling overhead.

[0179] The authentication process of the first device is described below.

[0180] In some embodiments, the first device sends fourth request information and / or capability information of the first device to the access network device in S303, wherein the fourth request information is used to request whether the first device can be authenticated as a reader / writer; and the capability information of the first device is the capability of the first device as a reader / writer supported by the first device.

[0181] Optionally, the first device can send user capability information (UECapabilityInformation) to the access network device, wherein the user capability information includes the capability information of the first device and / or the fourth request information.

[0182] Optionally, the capability information of the first device and / or the fourth request information can be included in the NAS message in the RRC setup completion message. For example, the NAS message can be a registration request message or a timing advance (TA) update message.

[0183] Optionally, the capability information of the first device and / or the fourth request information can be included in the NAS message in the RRC re-establishment completion message / RRC resume completion message.

[0184] Optionally, the capability information of the first device and / or the fourth request information can be included in other RRC messages sent by the terminal device to the access network device, such as user assistance information (UEAssistanceInformation) and the like.

[0185] Optionally, the capability information of the first device and / or the fourth request information can be carried by different RRC messages.

[0186] Optionally, the fourth request information can be encrypted by using an encryption method negotiated between the first device and the access network device.

[0187] The access network device can send the fourth request information and / or the capability information of the first device to the core network device.

[0188] For example, the access network device can send the NAS message received in the RRC setup complete message to the core network device, where the NAS message includes the fourth request information and / or the capability information of the terminal device. Alternatively, the NAS message received in the RRC setup complete message can be sent through an initial user (initial UE) message.

[0189] The core network device can authenticate the terminal device according to the fourth request information and / or the capability information of the first device.

[0190] The fourth request information can include one or more of the following: first device identification information, key information, indication information of an encryption algorithm, a random number, or a parameter calculated based on a key algorithm. After receiving the fourth request information, the core network device can perform a symmetric encryption calculation, and then compare the calculated parameter with the parameter calculated based on the key in the first request information. If the two parameters are consistent, the authentication is passed; otherwise, the authentication fails.

[0191] If the core network device receives the capability information of the first device at the same time / after receiving the fourth request information, the core network device can also authenticate the first device in combination with the capability information of the first device.

[0192] In S304, the core network device sends response information to the access network device, and correspondingly, the access network device receives the response information. The response information indicates that the first device can pass the verification as a reader-writer.

[0193] After the core network device authenticates the first device, the core network device can send response information to the access network device. After the first device receives the first response information, the first device forwards the first response information to the first device.

[0194] Alternatively, the core network device can decode the response information to learn whether the first device passes or fails the verification as a reader-writer.

[0195] Alternatively, the core network device can send a response message to the access network device, where the response message includes a NAS message containing the response information. After receiving the NAS message, the access network device forwards the NAS message to the first device.

[0196] Alternatively, the response message also includes first indication information. The access network device can decode the first indication information to learn whether the first device passes or fails the verification as a reader-writer. Alternatively, the first indication information can not be included in the response message, but can be included in other messages / information and sent by the core network device to the access network device.

[0197] Optionally, after determining the AIoT service resource, S311, the terminal device and the tag perform the AIoT service.

[0198] By way of example and without limitation, the following illustrates a process of inventory service between a first device and a tag (second device) performing an AIoT service.

[0199] Step 1: The first device sends a paging or selection message for selecting or paging at least one tag.

[0200] The paging or selection message includes mask information. If the mask information included by a tag matches the mask information included in the paging or selection message, it indicates that the tag is selected or paged.

[0201] The paging or selection message can also include session information and / or action information. After receiving the paging message, the tag first determines whether the mask matches, and then sets the flag according to the flag position setting rule of the action information, for example, sets the flag to A.

[0202] Step 2: The first device sends a query message. The query message is used to initialize an inventory cycle.

[0203] In an implementation manner, the query message includes a value of a parameter Q, which is used to determine the total number of time slots 2Q included in the inventory cycle indicated by the reader. For example, Q = 4, and the total number of time slots included in the inventory cycle is 24 = 16.

[0204] For each selected or paged tag, the index range of the time slot allocated by the access network device can be calculated according to the value of Q as [0, 2^Q-1]. The tag generates a random number between [0, 2^Q-1] according to the value of Q, and uses the random number as the initial value of the counter. For example, Q = 4, and the tag generates a random number between [0, 15]. For example, the tag generates a random number of 10, and the initial value of the counter is 10.

[0205] Each time the tag receives a repeated query (QueryRep) message, the value of the counter is decremented by one. When the value of the counter is equal to 0, the tag can send a 16-bit random number (RN16), which can be used to trigger a random access process and can be used as a random access request message. The first time slot after the query message is time slot 0. If the tag generates a random number of 0, the tag can immediately send the RN16 after receiving the query message.

[0206] Suppose the first tag is selected or paged, and the counter of the first tag is 0 after receiving the query message. Then, the first tag can perform step 2.

[0207] Step 3: the first tag sends a first random access request message.

[0208] For example, the first random access request message can be RN16 generated by the first tag. Here, RN16 is taken as an example, and the tag can also send random numbers of other lengths, such as 8-bit random numbers.

[0209] Step 4: the first device performs collision detection (for example, only one tag is allowed to access in each time slot, in fact, it can not be limited, such as frequency division multiplexing, or the first device can realize the solution of multiple overlapping uplink signals, then multiple tags can also be allowed to access), if more than one tag sends the first random access request message (for example, RN16) in the same time slot, it is judged that collision occurs, if only one tag sends RN16, a competition resolution success message (for example, ACK confirmation message) is fed back, and the received RN is carried.

[0210] The ACK message can also be called a random access response message or a conflict resolution message.

[0211] The first tag receives the competition resolution success message including the RN16 belonging to itself, which indicates that the competition resolution is successful.

[0212] Step 5: the first tag receiving the competition resolution success message (for example, ACK confirmation message) sends a first uplink message.

[0213] The first uplink message can include at least one of the EPC, TID of the first tag, the sensing information of the first tag, the storage area information of the first tag, the positioning data or the corresponding message, which is not limited by the present application.

[0214] The first tag can send multiple uplink messages, which are taken as an example in the present application, and the number of uplink messages sent by the first tag is not limited. For example, the first device receives uplink data, and can also send other downlink data, and the tag receiving other downlink data feeds back corresponding uplink data.

[0215] When the service between the first device and the first tag is completed (the first device has no other downlink data transmission, and the first tag also has no other uplink data transmission), the first device can send ACK / feedback to confirm the successful transmission of data / service completion, and trigger the next access time slot, that is, send QueryRep, or directly send QueryRep to confirm the successful transmission of data / service completion, and also trigger the next access time slot.

[0216] Optionally, after the service between the first device and the first tag is completed, the first tag can also flip the flag bit corresponding to the session indicated by the session information, such as from state A to state B.

[0217] If the data transmission fails / service completion fails, a NACK is sent, triggering the tag to retransmit the uplink data, and if the maximum number of retransmissions is not successful, the first device can send an indication (such as a first indication) to the tag to wait for the next round of inventory (continue to listen to Query or select / paging).

[0218] Optionally, the uplink data sent by the tag can be carried by a non-access stratum (NAS) message, and the terminal device acting as a relay node transmits the NAS message to the core network device through the access network device.

[0219] Optionally, when the service between the first device and the second device is completed, the first device sends a communication end indication to the access network device, and the communication end indication is used to instruct the access network device to release the first resource.

[0220] If the first device requests other resources, the access network device can also release the other resources (such as the second resource) through the communication end indication.

[0221] Optionally, when the service between the first device and the second device is completed, the access network device can initiate the release of the first resource by itself.

[0222] FIG. 12 is a flow diagram of a communication method provided by another embodiment of the present application.

[0223] As shown in FIG. 12, in the scenario of communication between the reader and the tag, the amount of data transmitted by the tag is small, and the current scheme using the amount of data as the charging standard is no longer suitable. The communication method provided by an embodiment of the present application can make the charging mode more suitable for the scenario of communication between the reader and the tag.

[0224] The method comprises:

[0225] In scenario 1, the first device sends first information to the core network device, and correspondingly, the core network device receives the first information, S710a.

[0226] In scenario 2, the access network device sends the first information to the core network device, and correspondingly, the core network device receives the first information, S710b.

[0227] The first information is used for charging the communication between the first device and the second device. The first information can be sent when the first device and / or the access network device meets the charging reporting condition, can be periodically reported, or can be event triggered (for example, when the service is completed).

[0228] The first information can include one or more of a service type, a data volume of the service type, a number of the second devices in inventory, a service / task identifier, a number of the second devices in inventory of the first device, a number of times of performing inventory service by the first device, a number of times of performing reading service by the first device, a number of times of performing writing service by the first device, a sequence number of the AIoT service, a time of reporting the AIoT service, a location of the first device, a frequency domain resource configured for the first device, a time domain resource configured for the first device, and a maximum power of downlink transmission of the first device, wherein the sequence number of the AIoT service is used to identify the AIoT service.

[0229] For example, under the inventory service, after the first device receives uplink data (e.g., device ID) from the second device, the first information can include a service type (e.g., inventory) and a length of the device ID. Under the command service, for example, reading service, the first information can include a service type (e.g., reading) and a data volume of reading.

[0230] For example, taking the inventory service as an example to illustrate the sequence number of the AIoT service, for example, periodic inventory service, the sequence number of the AIoT service can identify that the inventory service is the nth inventory service.

[0231] The examples of the service type in the above embodiments are only exemplary, and the embodiments of the present application can use other ways to indicate the service type in the first information, for example, using a combination of binary numbers to represent different services, which is not limited in the embodiments of the present application.

[0232] The embodiments of the present application do not limit the form of the first information, for example, using usage information report.

[0233] For example, the core network element receiving the first information can be, for example, a CTF-ADF network element, and the CTF-ADF sends a charging data request message to a charging management network element CHF after receiving the first information. The CHF can generate a CDR after receiving the charging data request message, and sends a charging data response message to the CTF-ADF network element to complete charging.

[0234] S720, the core network device determines charging information for communication between the first device and the second device according to the first information.

[0235] Optionally, the first device sends first information to the access network device, and correspondingly, the access network device receives the first information. The access network device can obtain the type of the service communicated between the first device and the second device and the data volume of the type of the service, for example, the access network device decodes the uplink data sent by the first device or the second device, and for another example, in a scenario perceived by the access network device (i.e., the access network device and the first device can interact through RRC or L2 layer), the first device can send the first information to the access network device through RRC or L2 layer, and the charging content reported by the access network device can include the size of the resource.

[0236] The L2 layer can include a MAC layer, a PDCP layer, and an SDAP layer.

[0237] In the embodiments of the present application, the type of the service communicated between the first device and the second device and the data volume of the type of the service are sent to the core network device, and the core network device can charge the service communicated between the first device and the second device according to the type of the service and the data volume of the type of the service, so that the charging is more suitable for the service scenario.

[0238] The first device can be a device with a reader function, the second device can be a device with a tag function, and the service communicated between the first device and the second device can be an environmental AIoT service.

[0239] Optionally, in S301, the core network device sends first service request information to the access network device, and correspondingly, the access network device receives the first service request information.

[0240] Optionally, the first service request information sent by the core network device to the access network device includes a task identifier, and the task identifier is used for the service communicated between the first device and the second device.

[0241] Optionally, the first service request information sent by the core network device can be transmitted to the first device through the access network device, for example, sent to the first device through a NAS message.

[0242] Optionally, the first device sends the task identifier to the core network device.

[0243] The first device can report the content of the service and the task identifier to the core network device after the service communicated with the second device is completed, so as to inform the core network device of the content of the service.

[0244] Optionally, the first device sends a first identity and / or a second identity to the core network device, wherein the first identity is used to identify an operator, and the second identity is used to identify a user of the second device. For example, the first identity can include a public land mobile network identity (PLMN ID). The PLMN ID is a combination of a mobile country code (MCC) and a mobile network code (MNC), and is a unique identity assigned to each operator; and the second identity can be an owner identity (owner ID), which is used to identify a user of the second device (tag).

[0245] Optionally, the first device can send one or more of the following to the core network device: frequency domain resources configured for the first device, time domain resources configured for the first device, and maximum power for downlink transmission of the first device.

[0246] Optionally, the server sends the first service request information to the core network device, i.e., the first service request information sent by the core network device to the access network device can come from the server.

[0247] Optionally, the report message can further include one or more of the following: resources configured for the terminal device, frequency domain resources configured for the terminal device, time domain resources configured for the terminal device, and maximum power for downlink transmission of the terminal device.

[0248] In some embodiments, an authentication / authorization process for the first device is further included. The process can refer to S303-S304 in the above embodiments, and will not be described in detail here.

[0249] FIG. 13 is a schematic diagram of a communication device according to an embodiment of the present application.

[0250] As shown in FIG. 13, the communication device 1000 can include a transceiver unit 1010 and a processing unit 1020. The transceiver unit 1010 can be configured to implement corresponding communication functions. The transceiver unit 1010 can also be referred to as a communication interface or a communication unit. The processing unit 1020 can be configured to determine resources and generate information. Optionally, the transceiver unit 1010 can include a receiving unit and a sending unit, wherein the receiving unit is configured to implement a receiving function, and the sending unit is configured to implement a sending function.

[0251] Optionally, the communication device 1000 can further include a storage unit, which can be configured to store instructions and / or data. The processing unit 1020 can read the instructions and / or data in the storage unit, so that the device implements the foregoing method embodiments.

[0252] As a design, the communication apparatus 1000 is configured to perform the steps or procedures performed by the first device, the access network device or the core network device in the above method embodiments, the transceiver unit 1010 is configured to perform the operations related to transceiving in the above method embodiments, for example, the terminal device transmits the first request information through the transceiver unit 1010, the access network device transmits the first configuration information through the transceiver unit 1010, etc.; the processing unit 1020 is configured to perform the operations related to determining the resource and generating the information in the above method embodiments, for example, the first device determines the first resource according to the first configuration information through the processing unit 1020.

[0253] It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, will not be repeated here.

[0254] It should also be understood that the communication apparatus 1000 herein is embodied in the form of functional units. The term "unit" herein can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (for example, a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combination of logical circuit and / or other suitable components supporting the described functions. In an optional example, those skilled in the art can understand that the communication apparatus 1000 can be embodied as the device (such as the first device, the access network device or the core network device) in the above embodiments, and can be configured to perform the corresponding procedures and / or steps of each method embodiment corresponding to the device, and for the sake of brevity, will not be repeated here.

[0255] The communication apparatus 1000 of each scheme described above has the function of implementing the corresponding steps performed by the device (such as the first device, the access network device or the core network device) in the above method. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (for example, the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units such as the determining unit can be replaced by a processor, which respectively performs the transceiving operations and related determining operations in each method embodiment.

[0256] In addition, the transceiver unit 1010 described above can also be a transceiver circuit (for example, which can include a receiving circuit and a transmitting circuit), and the processing unit 1020 can be a processing circuit.

[0257] It should be noted that the communication apparatus 1000 in FIG. 13 can be a chip or a chip system, for example, a system on chip (SoC). The transceiver unit can be an input / output circuit, a communication interface; the determining unit can be a processor or a microprocessor integrated on the chip or an integrated circuit. Here, no limitation is made.

[0258] FIG. 14 is a schematic diagram of a communication apparatus according to another embodiment of the present application.

[0259] As shown in FIG. 14, the communication apparatus 2000 can include a processor 2010.

[0260] Optionally, as shown in FIG. 14, the apparatus 2000 further includes a transceiver 2020 configured to receive and / or send signals. For example, the processor 2010 is configured to control the transceiver 2020 to receive and / or send signals. Optionally, the transceiver 2020 can include a receiver configured to receive signals and a transmitter configured to send signals.

[0261] The processor 2010 can be coupled to a memory 2030 configured to store computer programs or instructions and / or data. The processor 2010 is configured to execute the computer programs or instructions stored in the memory 2030 or read the data stored in the memory 2030 to perform the methods in the above method embodiments.

[0262] Optionally, the processor 2010 is one or more.

[0263] Optionally, the memory 2030 is one or more.

[0264] Optionally, the memory 2030 is integrated with the processor 2010 or is separately arranged.

[0265] For example, the processor 2010 can have the functions of the processing unit 1020 shown in FIG. 13, the memory 2030 can have the functions of a storage unit, and the transceiver 2020 can have the functions of the transceiver unit 1010 shown in FIG. 13.

[0266] As an example, the apparatus 2000 is configured to implement the operations performed by the apparatus (e.g., the first apparatus, the access network device, or the core network device) in the above method embodiments.

[0267] For example, the processor 2010 is configured to execute the computer programs or instructions stored in the memory 2030 to implement the related operations of the apparatus (e.g., the first apparatus, the access network device, or the core network device) in the above method embodiments.

[0268] It should be appreciated that the processor referenced in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic components, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0269] It should also be understood that the memory referenced in the embodiments of the present application can be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically EPROM (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM). For example, the RAM can be used as an external cache. As an example but not limitation, the RAM includes the following various forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM) and direct rambus RAM (DR RAM).

[0270] It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, the memory (storage module) can be integrated in the processor.

[0271] The apparatus in FIG. 14 can be a device in the foregoing embodiments, or a chip or chip system, such as a system on chip (SoC). The transceiver can be an input / output circuit or a communication interface, and the processor can be a processor or microprocessor integrated on the chip or an integrated circuit. The foregoing is not limited.

[0272] It should be further noted that the memory described herein is intended to include, but is not limited to, these and any other suitable type of memory.

[0273] When the apparatus is the chip system, it can (or also be referred to as a processing system) include a logic circuit and an input / output interface.

[0274] The logic circuit can be a processing circuit in the chip system. The logic circuit can be coupled to a storage unit to invoke instructions in the storage unit, so that the chip system can implement the methods and functions of the embodiments of the present application. The input / output interface can be an input / output circuit in the chip system, which outputs information processed by the chip system or inputs data or signaling information to be processed by the chip system.

[0275] The embodiments of the present application also provide a computer readable storage medium having stored thereon computer program instructions for implementing the method executed by the apparatus (such as the first apparatus, the access network device or the core network device) in each of the foregoing method embodiments.

[0276] For example, the computer program instructions are executed by a computer to enable the computer to implement the method executed by the apparatus (such as the first apparatus, the access network device or the core network device) in each of the foregoing method embodiments.

[0277] The embodiments of the present application also provide a computer program product containing program instructions, which are executed by a computer to implement the method executed by the apparatus (such as the first apparatus, the access network device or the core network device) in each of the foregoing method embodiments.

[0278] The embodiments of the present application also provide a communication system, which includes the first apparatus and / or the access network device and / or the core network device in the foregoing embodiments.

[0279] The explanations and beneficial effects of the related contents in any of the foregoing apparatuses can refer to the corresponding method embodiments provided above, and will not be repeated here.

[0280] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed 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.

[0281] 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 repeated here.

[0282] 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 interface, device or unit, and can be electrical, mechanical or other forms.

[0283] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0284] In addition, each functional unit in each embodiment of the present application can be integrated into a certain unit, or each unit can exist physically, or two or more units can be integrated into one unit.

[0285] If the functions are implemented in the form of software function 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 essentially or the parts that contribute to the field or the parts 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 methods described in the various embodiments 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 media that can store program codes.

[0286] 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 in that: The method is applied to an access network device, and the method includes: Determining first configuration information, wherein the first configuration information is used to indicate a first resource, and the first resource is used for a first device to send information to a second device, wherein the first device is a device having a reader / writer function, and the second device is a device having a tag function; Send the first configuration information to the first device.

2. The method according to claim 1, characterized in that The method further includes receiving first request information from the first device, wherein the first request information is used to request the first device for communication resources to send information to the second device.

3. The method according to claim 2, characterized in that The first request information includes at least one of the following information: The number of resource blocks (RBs) used for communication between the first device and the second device or the duration of communication between the first device and the second device.

4. The method according to claim 2 or 3, characterized in that The first request information includes information about a deployment mode requested by the first device, where the deployment mode includes at least one of the following: Deployment can be standalone, in-band, or in protection band.

5. The method according to any one of claims 2 to 4, characterized in that The first request information includes a frequency band number supported by the first device or a frequency band number requested by the first device.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: A first service request message is sent to the first device, where the first service request message includes the first configuration information.

7. The method according to any one of claims 1 to 6, characterized in that The first configuration information includes: One or more of frequency domain resource configuration information, time domain resource configuration information, or maximum power sent by the first device to the second device.

8. The method according to claim 7, characterized in that The frequency domain resource configuration method includes at least one of the following: independent deployment, guard band deployment or in-band deployment.

9. The method according to claim 8, characterized in that Information about independently deployed frequency domain resources, including at least one of the following: Frequency band or frequency segment information, subcarrier spacing information, bandwidth information, frequency point information, RB configuration information; Information about frequency domain resources deployed in-band, including at least one of the following: Co-frequency deployment mode: Co-frequency band or co-band indication, frequency band or frequency band information, subcarrier spacing information, bandwidth information, frequency point information, RB configuration information; or Inter-frequency deployment mode: frequency band or frequency segment information, subcarrier spacing information, bandwidth information, frequency point information, RB configuration information; Information about frequency domain resources deployed in the guard band includes at least one of the following: LTE guard band deployment: LTE frequency band or frequency band information, LTE frequency information, subcarrier spacing information, bandwidth information, frequency information, LTE guard band configuration information, RB configuration information; or NR guard band deployment: Co-band deployment: Co-band or co-band indication, NR band or band information, NR frequency information, subcarrier spacing information, bandwidth information, frequency information, NR guardband configuration information, RB configuration information; Inter-band deployment: NR frequency band or frequency band information, NR frequency information, subcarrier spacing information, bandwidth information, frequency information, NR guardband configuration information, and RB configuration information.

10. The method according to claim 9, characterized in that The information of the independently deployed frequency domain resources includes at least one of the following information: frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, scs-SpecificCarrierList, locationAndBandwidth, subcarrierSpacing, cyclicPrefix, starting RB on the bandwidth part BWP, RB offset on the BWP, RB length on the BWP, index of the RB on the BWP, RB position on the BWP, maximum power for the first apparatus to send downlink information, starting subcarrier on the RB, subcarrier offset on the RB, subcarrier length on the RB, index of the subcarrier on the RB, and position of the subcarrier on the RB; The information of the frequency domain resources deployed in the in-band includes at least one of the following information: Co-frequency deployment: co-band or co-band indication, frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, starting RB on bandwidth part BWP, RB offset on BWP, RB length on BWP, index of RB on BWP, RB position on BWP, maximum power for sending downlink information by the first device, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB, and position of subcarrier on RB; or Inter-frequency deployment: frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, starting RB on the bandwidth part BWP, RB offset on the BWP, RB length on the BWP, index of the RB on the BWP, RB position on the BWP, maximum power for sending downlink information by the first device, starting subcarrier on the RB, subcarrier offset on the RB, subcarrier length on the RB, index of the subcarrier on the RB, and position of the subcarrier on the RB; The information about the frequency domain resources deployed in the guard band includes at least one of the following information: LTE guard band deployment: FreqBandIndicatorEUTRA, MultiBandInfoListEUTR, eutraFrequency, ARFCN-ValueEUTRA, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, starting RB of guardband, RB offset of guardband, RB length of guardband, position of RB of guardband, RB index of guardband, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB and position of subcarrier on RB; or NR guard band deployment: Co-frequency deployment: Co-band or co-band indication, FreqBandIndicatorNR, MultiFrequencyBandListNR, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, Guardband configuration information, Guardband starting RB, Guardband RB offset, Guardband RB length, Guardband RB position, Guardband RB index, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, subcarrier index on RB and subcarrier position on RB, or Hetero-frequency deployment: FreqBandIndicatorNR, MultiFrequencyBandListNR, absoluteFrequencyPointA, ARFCN-ValueNR, scs-SpecificCarrierList, locationAndBandwidth, subcarrierSpacing, cyclicPrefix, Guardband configuration information, starting RB of guardband, RB offset of guardband, RB length of guardband, position of RB of guardband, RB index of guardband, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB and position of subcarrier on RB.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: Second request information is received from the first device, where the second request information is used to request time domain resources.

12. The method according to any one of claims 2 to 5, characterized in that The method further includes: receiving third request information from the first device, the third request information being used to request a second resource, the second resource being used by the second device to send information to the first device; or The first request information includes the third request information.

13. The method according to any one of claims 1 to 12, characterized in that The method further includes: sending second configuration information to the first device, where the second configuration information and the first configuration information are used to indicate a third resource, wherein the third resource is used for the second device to send information to the first device; or, The second configuration information is used to indicate the third resource, or The first configuration information includes the second configuration information.

14. A communication method, characterized in that: The method is applied to an access network device or a first apparatus, and the method includes: Acquire first information used for billing of communication between the first device and the second device; The first information is sent to the core network device, where the first information includes: service type, data volume of the service type, number of second devices inventoried, a first identifier, a second identifier, a service / task identifier, number of the second devices inventoried by the first device, number of times the first device performs inventory services, number of times the first device performs read services, number of times the first device performs write services, serial number of the AIoT service, time of reporting the AIoT service, location of the first device, frequency domain resources configured for the first device, time domain resources configured for the first device, and one or more of the maximum downlink power sent by the first device, wherein the first identifier is used to identify the operator, the second identifier is used to identify the user of the second device, and the serial number of the AIoT service is used to identify the AIoT service.

15. The method according to claim 14, characterized in that The first device is a device with a reader / writer function, the second device is a device with a tag function, and the service communicated between the first device and the second device is an AIoT service.

16. A communication method, characterized in that: The method is applied to a first device, and includes: Receiving first configuration information from an access network device, wherein the first configuration information is used to indicate a first resource, and the first resource is used for communication between the first device and a second device, wherein the first device is a device having a reader / writer function, and the second device is a device having a tag function; The first resource is determined according to the first configuration information.

17. The method according to claim 16, characterized in that The method further comprises: First request information is sent to the access network device, where the first request information is used to request communication resources between the first device and the second device.

18. The method according to claim 17, characterized in that The first request information includes at least one of the following information: The number of resource blocks (RBs) used for communication between the first device and the second device or the duration of communication between the first device and the second device.

19. The method according to claim 17 or 18, characterized in that The first request information includes information about a deployment mode requested by the first device, where the deployment mode includes at least one of the following: Deployment can be standalone, in-band, or in protection band.

20. The method according to any one of claims 17 to 19, characterized in that The first request information includes a frequency band number supported by the first device or a frequency band number requested by the first device.

21. The method according to any one of claims 16 to 20, characterized in that The first configuration information includes at least one of the following information: Frequency domain resource configuration information, time domain resource configuration information, or the maximum power sent by the first device to the second device.

22. The method according to claim 21, characterized in that The frequency domain resource configuration method includes at least one of the following: independent deployment, guard band deployment or in-band deployment.

23. The method according to claim 22, characterized in that Information about independently deployed frequency domain resources, including at least one of the following: Frequency band or frequency segment information, subcarrier spacing information, bandwidth information, frequency point information, RB configuration information; Information about frequency domain resources deployed in-band, including at least one of the following: Co-frequency deployment mode: Co-frequency band or co-band indication, frequency band or frequency band information, subcarrier spacing information, bandwidth information, frequency point information, RB configuration information; or Inter-frequency deployment mode: frequency band or frequency segment information, subcarrier spacing information, bandwidth information, frequency point information, RB configuration information; Information about frequency domain resources deployed in the guard band includes at least one of the following: LTE guard band deployment: LTE frequency band or frequency band information, LTE frequency information, subcarrier spacing information, bandwidth information, frequency information, LTE guard band configuration information, RB configuration information; or NR guard band deployment: Co-band deployment: Co-band or co-band indication, NR band or band information, NR frequency information, subcarrier spacing information, bandwidth information, frequency information, NR guardband configuration information, RB configuration information; Inter-band deployment: NR frequency band or frequency band information, NR frequency information, subcarrier spacing information, bandwidth information, frequency information, NR guardband configuration information, and RB configuration information.

24. The method according to claim 23, wherein The information of the independently deployed frequency domain resources includes at least one of the following information: frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, scs-SpecificCarrierList, locationAndBandwidth, subcarrierSpacing, cyclicPrefix, starting RB on the bandwidth part BWP, RB offset on the BWP, RB length on the BWP, index of the RB on the BWP, RB position on the BWP, maximum power for the first apparatus to send downlink information, starting subcarrier on the RB, subcarrier offset on the RB, subcarrier length on the RB, index of the subcarrier on the RB, and position of the subcarrier on the RB; The information of the frequency domain resources deployed in the in-band includes at least one of the following information: Co-frequency deployment: co-band or co-band indication, frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, starting RB on bandwidth part BWP, RB offset on BWP, RB length on BWP, index of RB on BWP, RB position on BWP, maximum power for sending downlink information by the first device, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB, and position of subcarrier on RB; or Inter-frequency deployment: frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, starting RB on the bandwidth part BWP, RB offset on the BWP, RB length on the BWP, index of the RB on the BWP, RB position on the BWP, maximum power for sending downlink information by the first device, starting subcarrier on the RB, subcarrier offset on the RB, subcarrier length on the RB, index of the subcarrier on the RB, and position of the subcarrier on the RB; The information about the frequency domain resources deployed in the guard band includes at least one of the following information: LTE guard band deployment: FreqBandIndicatorEUTRA, MultiBandInfoListEUTR, eutraFrequency, ARFCN-ValueEUTRA, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, starting RB of guardband, RB offset of guardband, RB length of guardband, position of RB of guardband, RB index of guardband, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB and position of subcarrier on RB; or NR guard band deployment: Co-frequency deployment: Co-band or co-band indication, FreqBandIndicatorNR, MultiFrequencyBandListNR, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, Guardband configuration information, Guardband starting RB, Guardband RB offset, Guardband RB length, Guardband RB position, Guardband RB index, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, subcarrier index on RB and subcarrier position on RB, or Hetero-frequency deployment: FreqBandIndicatorNR, MultiFrequencyBandListNR, absoluteFrequencyPointA, ARFCN-ValueNR, scs-SpecificCarrierList, locationAndBandwidth, subcarrierSpacing, cyclicPrefix, Guardband configuration information, starting RB of guardband, RB offset of guardband, RB length of guardband, position of RB of guardband, RB index of guardband, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, index of subcarrier on RB and position of subcarrier on RB.

25. The method according to any one of claims 16 to 24, characterized in that The method further comprises: Sending second request information to the access network device, where the second request information is used to request time domain resources.

26. The method according to any one of claims 17 to 20, characterized in that The method further includes: sending a third request message to the access network device, wherein the third request message is used to request a second resource, and the second resource is used by the second device to send information to the first device; or The first request information includes the third request information.

27. The method according to any one of claims 16 to 26, characterized in that The method further comprises: receiving second configuration information from the access network device, where the second configuration information and the first configuration information are used to indicate a third resource, wherein the third resource is used for the second device to send information to the first device; or The second configuration information is used to indicate the third resource, or The first configuration information includes the second configuration information.

28. A communication method, characterized in that: The method comprises: receiving first information for billing from an access network device or a first apparatus; The first information includes: a service type, a data volume of the service type, a number of second devices inventoried, a first identifier, a second identifier, a service / task identifier, a number of the second devices inventoried by the first device, a number of times the first device performs an inventory service, a number of times the first device performs a read service, a number of times the first device performs a write service, a serial number of the AIoT service, a time of reporting the AIoT service, a location of the first device, a frequency domain resource configured for the first device, a time domain resource configured for the first device, and one or more of a maximum downlink power transmitted by the first device, wherein the first identifier is used to identify the operator, the second identifier is used to identify the user of the second device, and the serial number of the AIoT service is used to identify the AIoT service; Billing information for communication between the first device and the second device is determined based on the first information.

29. The method according to claim 28, characterized in that The first device is a device with a reader / writer function, the second device is a device with a tag function, and the service communicated between the first device and the second device is an AIoT service.

30. A communication method, characterized in that: The method comprises: A first device or an access network device obtains first information for billing of communication between the first device and the second device, wherein the first information includes: a service type, a data volume of the service type, a number of second devices inventoried, a first identifier, a second identifier, a service / task identifier, a number of second devices inventoried by the first device, a number of times the first device performs an inventory service, a number of times the first device performs a read service, a number of times the first device performs a write service, a serial number of the AIoT service, a time of reporting the AIoT service, a location of the first device, a frequency domain resource configured for the first device, a time domain resource configured for the first device, and one or more of a maximum downlink power transmitted by the first device, wherein the first identifier is used to identify an operator, the second identifier is used to identify a user of the second device, and the serial number of the AIoT service is used to identify the AIoT service; The first device or the access network device sends the first information to the core network device; The core network device receives the first information from the access network device or the first apparatus; The core network device determines billing information for communication between the first device and the second device based on the first information.

31. A communication system, characterized in that: The system comprises: core network equipment and the first device and / or access network equipment, The first device and / or the access network device is used to obtain first information for billing for communication between the first device and the second device, and to send the first information to the core network device, wherein the first information includes: service type, data volume of the service type, number of second devices inventoried, first identifier, second identifier, service / task identifier, number of second devices inventoried by the first device, number of times the first device performs inventory services, number of times the first device reads services, number of times the first device performs write services, serial number of the AIoT service, time of reporting the AIoT service, location of the first device, frequency domain resources configured for the first device, time domain resources configured for the first device, and one or more of the maximum downlink power of the first device, wherein the first identifier is used to identify the operator, the second identifier is used to identify the user of the second device, and the serial number of the AIoT service is used to identify the AIoT service; The core network device is used to receive the first information from the access network device and / or the first apparatus, and determine charging information for communication between the first apparatus and the second apparatus based on the first information.

32. A communication device, characterized in that: The device comprises: processor, The processor is configured to execute the method of any one of claims 1 to 13, or the method of claim 14 or 15, or the method of any one of claims 16 to 27, or the method of claim 28 or 29.

33. A computer-readable storage medium, characterized in that The computer-readable storage medium stores program instructions, which are used to be read by a processor to execute the method according to any one of claims 1 to 13, or the method according to claim 14 or 15, or the method according to any one of claims 16 to 27, or the method according to claim 28 or 29.

34. A computer program product, characterized in that When the computer program product is run on a computer, the computer is caused to perform the method according to any one of claims 1 to 13, or the method according to claim 14 or 15, or the method according to any one of claims 16 to 27, or the method according to claim 28 or 29.

Images