Method and device for transmitting uplink service scheduling information

Abstract

The invention provides a method and a device for transmitting uplink service scheduling information, and relates to the technical field of communication. The method comprises the following steps: acquiring uplink service scheduling information of an artificial intelligence Internet of Things (A-IoT) service; generating a downlink message according to the uplink service scheduling information; and sending the downlink message to a terminal device through the PRDCH. Some embodiments of the invention are used for reducing the power consumption of terminal equipment in an A-IoT communication scene.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and more specifically, to a method and device for transmitting uplink service scheduling information. Background Art

[0002] Passive Internet of Things (PIoT) is a battery-free IoT technology that uses a reader to power passive terminal devices to achieve communication. As PIoT technology continues to evolve, Ambient IoT (A-IoT) has been proposed in related technologies.

[0003] In traditional communication scenarios, network-side devices send downlink service data and uplink service scheduling information to terminal devices through different downlink channels. Correspondingly, terminal devices detect downlink service data and uplink service scheduling information sent by network-side devices on different downlink channels. In A-IoT communication scenarios, terminal devices are generally powered by the induced current generated by the downlink signal sent by network-side devices. Therefore, A-IoT communication scenarios have very strict requirements on the power consumption of terminal devices. However, when terminal devices detect downlink service data and uplink service scheduling information sent by network-side devices on different downlink channels, the power consumption of terminal devices will increase, which will lead to a significant decrease in the battery life of terminal devices and affect the normal working time and stability of terminal devices. Summary of the invention

[0004] The exemplary embodiments of the present application provide a method and apparatus for transmitting uplink service scheduling information, which are used to reduce the power consumption of terminal devices in A-IoT communication scenarios.

[0005] Some embodiments of the present application provide the following technical solutions:

[0006] In a first aspect, some embodiments of the present application provide a method for transmitting uplink service scheduling information, including:

[0007] Obtaining uplink service scheduling information of the A-IoT service;

[0008] Generate a downlink message according to the uplink service scheduling information;

[0009] The downlink message is sent to the terminal device via PRDCH.

[0010] In a second aspect, some embodiments of the present application provide a device for transmitting uplink service scheduling information, including:

[0011] An acquisition unit, configured to acquire uplink service scheduling information of the A-IoT service;

[0012] A generating unit, configured to generate a downlink message according to the uplink service scheduling information;

[0013] A sending unit is used to send the downlink message to the terminal device via PRDCH.

[0014] In a third aspect, some embodiments of the present application provide an electronic device, comprising: a memory and a processor, wherein the memory stores a computer program, and the processor is configured to implement the method for transmitting uplink service scheduling information described in the first aspect when executing the computer program.

[0015] In a fourth aspect, some embodiments of the present application provide a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a computing device, the computing device implements the method for transmitting uplink service scheduling information described in the first aspect.

[0016] In a fifth aspect, some embodiments of the present application provide a chip, comprising a processor and a memory, wherein the memory is used to store programs or instructions that can be run on the processor, and the processor is used to execute the programs or instructions to enable the method for transmitting uplink service scheduling information described in the first aspect.

[0017] In a sixth aspect, some embodiments of the present application provide a computer program product, which, when executed on a computer, enables the computer to implement the method for transmitting uplink service scheduling information described in the first aspect.

[0018] It can be seen from the above technical solution that the method for transmitting the uplink service scheduling information provided in the above embodiment first obtains the uplink service scheduling information of the A-IoT service, then generates a downlink message according to the uplink service scheduling information, and sends the downlink message to the terminal device through the physical reader device channel. Since the method for transmitting the uplink service scheduling information provided in the embodiment of the present application can send the downlink message generated according to the uplink service scheduling information to the terminal device through PRDCH, and PRDCH is a channel for the network side device to transmit downlink service data to the terminal device, the terminal device only needs to detect the uplink service scheduling information and downlink service data on PRDCH, and there is no need to detect the uplink service scheduling information and downlink service data on different channels respectively, so the embodiment of the present application can reduce the power consumption of the terminal device in the A-IoT communication scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the implementation methods of some embodiments of the present application or related technologies, the following is a brief introduction to the drawings required for use in the description of the embodiments or related technologies. Obviously, the drawings described below are some embodiments of the present application, and a person skilled in the art can also obtain other drawings based on these drawings.

[0020] Figure 1 A topological schematic diagram of a communication system provided by some embodiments is shown;

[0021] Figure 2 A topological schematic diagram of a communication system provided by some other embodiments is shown;

[0022] Figure 3 A flowchart showing the steps of a method for transmitting uplink service scheduling information in some embodiments;

[0023] Figure 4 A schematic diagram of the data structure of MAC-CE provided by some embodiments is shown;

[0024] Figure 5 A schematic diagram of the data structure of a MAC subheader provided by some embodiments is shown;

[0025] Figure 6 A flowchart showing the steps of a method for transmitting uplink service scheduling information in other embodiments;

[0026] Figure 7 A schematic diagram showing the structure of a downlink message in some embodiments is shown;

[0027] Figure 8 A schematic diagram showing the structure of downlink messages in other embodiments is shown;

[0028] Fig. 9 A flowchart showing the steps of a method for transmitting uplink service scheduling information in other embodiments;

[0029] Fig.10 A schematic diagram showing the structure of downlink messages in other embodiments is shown;

[0030] Fig.11 A schematic diagram showing the structure of downlink messages in other embodiments is shown;

[0031] Fig.12 A flowchart showing the steps of a method for transmitting uplink service scheduling information in other embodiments;

[0032] Fig.13 A schematic diagram showing the structure of downlink messages in other embodiments is shown;

[0033] Fig.14A schematic diagram showing the structure of downlink messages in other embodiments is shown;

[0034] Fig.15 The figure shows a schematic diagram of the structure of the network side device in some embodiments of the present application. DETAILED DESCRIPTION

[0035] It should be noted that the brief description of the terms in this application is only for the convenience of understanding the implementation methods described below. In order to make the purpose and implementation methods of this application clearer, the exemplary implementation methods of this application will be clearly and completely described below in conjunction with the drawings in the exemplary embodiments of this application. Obviously, the described exemplary embodiments are only part of the embodiments of this application, not all of the embodiments.

[0036] It is not intended to limit the embodiments of the present application. Unless otherwise specified, these terms should be understood according to their ordinary and customary meanings.

[0037] The terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device comprising a list of components is not necessarily limited to all the components expressly listed but may include other components not expressly listed or inherent to such product or device.

[0038] References to "some implementations", "some embodiments", etc. in the specification indicate that the described implementations or embodiments may include specific features, structures, or characteristics, but not every embodiment may include the specific features, structures, or characteristics. In addition, such phrases do not necessarily refer to the same implementation. In addition, when a specific feature, structure, or characteristic is described in connection with an embodiment, it is considered to be within the knowledge of those skilled in the art to implement such feature, structure, or characteristic in connection with other implementations (whether or not explicitly described herein).

[0039] The following first describes the communication system provided in the embodiments of the present application.

[0040] Figure 1 A topological diagram of a communication system provided in some embodiments of the present application. Figure 1 As shown, the communication system includes: a network side device 11 and a terminal device 12. An A-IoT uplink and an A-IoT downlink are established between the network side device 11 and the terminal device 12. The terminal device 12 can send uplink A-IoT information to the network side device 11 through the A-IoT uplink, and receive A-IoT downlink information sent by the network side device 11 through the A-IoT downlink. Correspondingly, the network side device 11 can receive uplink A-IoT information sent by the terminal device 12 through the A-IoT uplink, and can also send A-IoT downlink information to the terminal device 12 through the A-IoT downlink.

[0041] In some embodiments, a New Radio (NR) uplink and an NR downlink are also established between the network side device 11 and the terminal device 12. The terminal device 12 can send uplink NR information to the network side device through the NR uplink, and receive NR downlink information sent by the network side device through the NR downlink. Correspondingly, the network side device 11 can receive uplink NR information sent by the terminal device 12 through the NR uplink, and can also send NR downlink information to the terminal device 12 through the NR downlink.

[0042] The terminal device 12 can be any device that supports providing voice and / or other business data connectivity to users. For example, the terminal device can be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network, as well as personal communication service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDA) and other devices. The wireless terminal can also be a mobile device, UE terminal, access terminal, wireless communication device, terminal unit, terminal station, mobile station (Mobile Station), mobile station (Mobile), remote station (Remote Station), remote station, remote terminal (Remote Terminal), subscriber unit (Subscriber Unit), subscriber station (Subscriber Station), user agent (User Agent), etc. As an example, Figure 1 The terminal device 12 is taken as an example, which is an A-IoT device and a tag Tag; the network side device 11 includes but is not limited to a reader (Reader), a base station (Base Station, BS), an access point device (Node B, NB), a node, etc.

[0043] In other embodiments, the communication system includes: an intermediate node and / or an auxiliary node. An A-IoT uplink and an A-IoT uplink and downlink are established between the network side device and the terminal device through the intermediate node and / or the auxiliary node. The terminal device sends uplink A-IoT information to the network side device through the intermediate node and / or the auxiliary node, and receives A-IoT downlink information sent by the network side device through the intermediate node and / or the auxiliary node. Correspondingly, the network side device can receive uplink A-IoT information sent by the terminal device through the intermediate node and / or the auxiliary node, and send A-IoT downlink information to the terminal device through the intermediate node and / or the auxiliary node.

[0044] In other embodiments, reference Figure 2 As shown, the communication system includes: a first network side device 21, a second network side device 22 and a terminal device 23. An A-IoT uplink is established between the first network side device 21 and the terminal device 23; an A-IoT downlink is established between the second network side device 22 and the terminal device 23. The terminal device 12 can send uplink A-IoT information to the first network side device 21 through the A-IoT uplink, and correspondingly, the first network side device 21 can receive the uplink A-IoT information sent by the terminal device 23 through the A-IoT uplink. The second network side device 22 can send A-IoT downlink information to the terminal device 23 through the A-IoT downlink, and correspondingly, the terminal device 23 can receive the A-IoT downlink information sent by the second network side device 22 through the A-IoT uplink.

[0045] In some embodiments, a data transmission link may also be established between the first network side device 21 and the second network side device 22. Data or signaling is transmitted between the first network side device 21 and the second network side device 22 via the data transmission link. The first network side device 21 and the second network side device include but are not limited to a reader (Reader), a base station (Base Station, BS), an access point device (Node B, NB), a node, etc.

[0046] It should be noted that Figure 1 and Figure 2 A possible communication system for the method for transmitting uplink service scheduling information provided in the embodiment of the present application, but the embodiment of the present application is not limited to this. The communication system to which the method for transmitting uplink service scheduling information provided in the embodiment of the present application is applied may also include more communication equipment, and the embodiment of the present application is not limited to this, and the communication system can support the method for transmitting uplink service scheduling information provided based on the embodiment of the present application.

[0047] The embodiment of the present application provides a method for transmitting uplink service scheduling information, and the method is applied to a network side device, for example, a base station. Figure 3 A schematic diagram of a process for transmitting uplink service scheduling information provided in an embodiment of the present application is shown. Figure 3 As shown, the method for transmitting the uplink service scheduling information may include:

[0048] S31. Obtain uplink service scheduling information of the A-IoT service.

[0049] The uplink service scheduling information in the embodiment of the present application refers to the relevant information sent by the network side device to the terminal device for managing and controlling the terminal device to transmit (uplink direction) service data and / or control information to the network side device.

[0050] In some embodiments, the uplink service scheduling information may include: uplink time domain resource allocation (TDRA) for indicating the time domain resources that can be used by the terminal device for uplink transmission, uplink frequency domain resource allocation (FDRA) for indicating the uplink frequency domain resource allocation that can be used by the terminal device for uplink transmission, modulation and coding scheme (MCS) for indicating the modulation and coding scheme that can be used by the terminal device for uplink transmission, transport block size (TB Size) for indicating the size of the transport block when the terminal device performs uplink transmission, reader identification code (ID), information for indicating whether the terminal device uses an uplink midamble when performing uplink transmission, information for indicating the number of repetitions when the terminal device performs uplink transmission, and information for indicating the uplink time slice length (UplinkChip Duartion) when the terminal device performs uplink transmission. One or more of the above.

[0051] The uplink time slice length may be identified by the number of On-Off Keying symbols (OOK) that can be transmitted in an uplink Orthogonal Frequency Division Multiplexing (OFDM) symbol.

[0052] In some embodiments, the uplink service scheduling information may include: uplink time domain resource allocation, uplink frequency domain resource allocation, modulation and coding format, transmission block size, reader identification code, uplink intermediate code information, repetition number information and uplink time slice length information. The uplink service scheduling information is uplink service scheduling information of fixed length.

[0053] In other embodiments, the uplink service scheduling information may include, according to actual needs, one or more of the following: uplink time domain resource allocation, uplink frequency domain resource allocation, modulation and coding format, transmission block size, reader identification code, uplink intermediate code information, repetition number information, and uplink time slice length information. The uplink service scheduling information is uplink service scheduling information of variable length.

[0054] In some embodiments, the protocol data unit (PDU) corresponding to the uplink service scheduling information includes: a medium access control control element (Medium Access Control-Control Element, MAC-CE) and a medium access control subheader (Medium Access Control subheader, referred to as MAC subheader), and the uplink service scheduling information is carried by MAC-CE.

[0055] Reference Figure 4 As shown, in some embodiments, MAC-CE includes: four octets. Among them, the uplink time domain resource allocation 41 is carried on the second bit to the fifth bit of the first octet Oct1, the uplink modulation and coding format 42 is carried on the sixth bit to the eighth bit of the first octet Oct1, the uplink transmission block size 43 is carried on the first bit to the fourth bit of the second octet Oct2, the uplink frequency domain resource allocation 44 is carried on the fifth bit to the eighth bit of the second octet Oct2, the reader identification code 45 is carried on the third bit to the eighth bit of the third octet Oct3, the uplink intermediate code information 46 is carried on the second bit and the third bit of the fourth octet Oct4, the uplink repetition number 47 is carried on the fourth bit and the fifth bit of the fourth octet Oct4, and the uplink time slice length 48 is carried on the sixth bit to the eighth bit of the fourth octet Oct4.

[0056] That is, the length of the uplink time domain resource allocation 41 is 4 bits; the length of the uplink modulation and coding format 42 is 3 bits; the length of the uplink transmission block size 43 is 4 bits; the length of the uplink time domain resource allocation 44 is 4 bits; the length of the reader identification code 45 is 6 bits; the length of the uplink intermediate code information 46 is 2 bits; the length of the uplink repetition number 47 is 2 bits; and the length of the uplink time slice length is 2 bits.

[0057] In some embodiments, the value A / D of the first bit of the first octet of MAC-CE is used to indicate activation or deactivation, the first bit and the second bit of the second octet, and the first bit of the fourth octet are reserved (Reserved, abbreviated as R in the data structure).

[0058] Reference Figure 5 As shown, in some embodiments, the media access control subheader includes: two octets (Oct1 and Oct2). The value F on the second bit of the first octet Oct1 is used to indicate the unit of the size of MAC-CE, the values ​​on the third bit to the eighth bit of the first octet Oct1 are used to indicate the type of MAC-CE, and the value L on the first bit to the eighth bit of the second octet Oct2 is used to indicate the numerical value of the size of MAC-CE.

[0059] In some embodiments, the first bit of the first octet of the MAC subheader is a reserved bit R.

[0060] In some embodiments, the correspondence between LCID and MAC-CE type may be as shown in Table 1 below:

[0061] Table 1

[0062] LCID Types of MAC-CE 0 Common control channel size of 64 bits 1～32 Logical channel identification …… …… 65 A-IoT uplink service

[0063] As shown in 1 above, when the value of LCID is 65, it indicates that the type of MAC-CE is A-IoT uplink service. Therefore, when the uplink service scheduling information of the A-IoT service is carried by MAC-CE, the value of LCID is set to the binary number 1000001.

[0064] S32. Generate a downlink message according to the uplink service scheduling information.

[0065] In some embodiments, a downlink message is generated according to the uplink service scheduling information, including: performing cyclic redundancy check (CRC) addition, channel coding, block repetition, linear coding, scrambling, modulation, pilot code addition and other operations on the uplink service scheduling information to obtain the downlink message.

[0066] S33. Send a downlink message to the terminal device through a physical reader device channel (PRDCH).

[0067] The method for transmitting uplink service scheduling information provided in the embodiment of the present application first obtains the uplink service scheduling information of the A-IoT service, then generates a downlink message according to the uplink service scheduling information, and sends the downlink message to the terminal device through the physical reader device channel. Since the method for transmitting uplink service scheduling information provided in the embodiment of the present application can send the downlink message generated according to the uplink service scheduling information to the terminal device through the PRDCH, and the PRDCH is a channel for the network side device to transmit downlink service data to the terminal device, the terminal device only needs to detect the uplink service scheduling information and downlink service data on the PRDCH, and there is no need to detect the uplink service scheduling information and downlink service data on different channels respectively, so the embodiment of the present application can reduce the power consumption of the terminal device in the A-IoT communication scenario.

[0068] As an extension and refinement of the above embodiment, the present application embodiment provides another method for transmitting uplink service scheduling information, referring to Figure 6 As shown, the method for transmitting uplink service scheduling information includes the following steps:

[0069] S601. Obtain uplink service scheduling information of the A-IoT service.

[0070] S602: Calculate a cyclic redundancy check (CRC) bit sequence of uplink service scheduling information to obtain a first CRC bit sequence.

[0071] In some embodiments, calculating the CRC bit sequence of uplink service scheduling information includes the following steps a to c:

[0072] Step a: determine whether the length of the uplink service scheduling information is greater than a first threshold length.

[0073] In some embodiments, the first threshold length is 24.

[0074] In some other embodiments, the first threshold length is 16.

[0075] In the above step a, if the length of the uplink service scheduling information is less than or equal to the first threshold length, the following step b is executed, and if the length of the uplink service scheduling information is greater than the first threshold length, the following step c is executed:

[0076] Step b: Calculate the CRC bit sequence of the uplink service scheduling information based on the first CRC algorithm.

[0077] Step c: Calculate the CRC bit sequence of the uplink service scheduling information based on the second CRC algorithm.

[0078] Among them, the length of the CRC bit sequence obtained by the second CRC algorithm is greater than the length of the CRC bit sequence obtained by the first CRC algorithm.

[0079] In some embodiments, the first CRC algorithm is a CRC-6 algorithm and the second CRC algorithm is a CRC-16 algorithm.

[0080] The polynomial expression of the CRC-6 algorithm is:

[0081] g CRC6 (D)=[D 6 +D 5 +1]foraCRClengthL=6

[0082] The polynomial expression of the CRC-16 algorithm is:

[0083] g CRC16 (D)=[D 16 +D 12 +D 5 +1]foraCRClengthL=16

[0084] From the polynomial expression of the CRC-6 algorithm and the polynomial expression of the CRC-16 algorithm, it can be seen that when the CRC-6 algorithm is used, the length of the obtained CRC bit sequence is 6, and when the CRC-6 algorithm is used, the length of the obtained CRC bit sequence is 16.

[0085] In the above embodiment, when the length of the uplink service scheduling information of the A-IoT service is less than or equal to the first threshold length, the CRC bit sequence of the uplink service scheduling information is calculated based on the first CRC algorithm; when the length of the uplink service scheduling information of the A-IoT service is greater than the first threshold length, the CRC bit sequence of the uplink service scheduling information is calculated based on the second CRC algorithm, and the length of the CRC bit sequence obtained by the second CRC algorithm is greater than the length of the CRC bit sequence obtained by the first CRC algorithm. Therefore, the above embodiment can save the overhead caused by the CRC bit sequence when the length of the uplink service scheduling information of the A-IoT service is small, thereby improving the efficiency of sending the uplink service scheduling information.

[0086] S603: Concatenate the uplink service scheduling information and the first CRC bit sequence to obtain a first bit sequence.

[0087] In some embodiments, splicing the uplink service scheduling information and the first CRC bit sequence to obtain the first bit sequence includes: splicing the first CRC bit sequence to the end of the uplink service scheduling information to obtain the first bit sequence.

[0088] For example, when the uplink service scheduling information is a0, a1, a2, a3, ..., a A-1 , the first CRC bit sequence is p0,p1,p2,p3,...,p N-1 , then the first bit sequence is a0,a1,...,a A-1 ,p0,p1,...,p N-1 , and the length of the first bit sequence is the sum of the length of the uplink service scheduling information and the length of the first CRC bit sequence.

[0089] S604: Linearly encode the first bit sequence to obtain a second bit sequence.

[0090] In some embodiments, linear encoding is performed on the first bit sequence to obtain a second bit sequence, including: performing Manchester encoding on the first bit sequence to obtain the second bit sequence.

[0091] Manchester encoding is a synchronous clock encoding technology, commonly used in LAN transmission. It represents "0" or "1" by switching between high and low levels. There is a jump action in the middle of each bit, which can be: changing the '0' in the third bit sequence to '10', and changing the '1' in the third bit sequence to '01'.

[0092] Assume: The first bit sequence is b0,b1,b2,b3,...,b B-1 , then the second bit sequence obtained by linearly encoding the first bit sequence can be: b 0,0 ,b 0,1 ,b 1,0 ,b 1,1 ,b 2,0 ,b 2,1 ,...,b B-1,0 ,b B-1,1 .

[0093] S605: Modulate the second bit sequence to obtain a modulated signal.

[0094] In some embodiments, modulating the second bit sequence includes: performing OOK (On-Off Keying) modulation on the second bit sequence.

[0095] In some embodiments, performing OOK modulation on the fourth bit sequence includes: mapping bits with a value of "1" in the second bit sequence to high-level OOK symbols (OOK ON chip), and mapping bits with a value of "0" in the fourth bit sequence to low-level OOK symbols (OOK OFF chip).

[0096] S606: Add a downlink pilot code to the modulated signal to obtain a downlink message.

[0097] In some embodiments, adding a downlink pilot code to the modulated signal includes: adding a downlink preamble (DL Preamble) to a header of the modulated signal.

[0098] In some embodiments, the downlink preamble includes: a start-indicator part and a timing acquisition signal, wherein the start-indicator part is used to indicate the start of uplink service scheduling information transmission, and the timing acquisition signal performs clock synchronization.

[0099] In some embodiments, adding a downlink pilot code to the modulated signal includes: adding a downlink postamble (DL Postamble) to the end of the modulated signal.

[0100] For example, refer to Figure 7 As shown, the downlink message obtained based on the above steps S601 to S607 includes: a downlink preamble code 71, uplink service scheduling information 72, a first CRC bit sequence 73 and a downlink post-synchronization code 74.

[0101] In some embodiments, adding a downlink pilot code to the modulated signal also includes: determining whether the length of the modulated signal is greater than a second threshold length; if the length of the modulated signal is greater than the second threshold length, adding a downlink intermediate code between the head and tail of the modulated signal.

[0102] In some embodiments, adding a downlink midamble between a head portion and a tail portion of a modulated signal includes: adding the downlink midamble at a midpoint of the modulated signal.

[0103] In some embodiments, a downlink midamble is added at a second threshold length of the modulated signal.

[0104] For example, refer to Figure 8 As shown, when the length of the modulated signal is greater than the second threshold length, the downlink message obtained based on the above steps S601 to S607 includes: a downlink preamble 81, front uplink service scheduling information 82, a downlink midamble 83, rear uplink service scheduling information 84, a first CRC bit sequence 85, and a downlink post-synchronization code 86. Among them, the front uplink service scheduling information 82 and the rear uplink service scheduling information 84 are two parts of data obtained by dividing the uplink service scheduling information 82 by the downlink midamble 83.

[0105] In some embodiments, the method for transmitting uplink service scheduling information further includes: before linearly encoding the first bit sequence, performing a block repetition operation (Repetiton) on the first bit sequence.

[0106] For example, when the first bit sequence is a0, a1, a2, ..., a A-1 , then the bit sequence obtained by performing block repetition operation on the first bit sequence is a0, a1, a2, ..., a A-1 ,a0,a1,a2,...,a A-1 .

[0107] Performing a block repetition operation on the first bit sequence can cause the uplink message to include two first bit sequences, so that even if one of the first bit sequences is erroneous during transmission, correct uplink service scheduling information can be obtained based on the other first bit sequence, thereby improving the robustness of the uplink service scheduling information transmission.

[0108] In some embodiments, the method for transmitting uplink service scheduling information further includes: before modulating the second bit sequence, performing a scrambling operation (Scrambling) on ​​the second bit sequence.

[0109] Performing a scrambling operation on the second bit sequence before modulating the second bit sequence can improve the security and relevance of the uplink service scheduling information.

[0110] As an extension and refinement of the above embodiment, the present application embodiment provides another method for transmitting uplink service scheduling information, referring to Fig. 9 As shown, the method for transmitting uplink service scheduling information includes the following steps:

[0111] S901. Obtain uplink service scheduling information of the A-IoT service.

[0112] S902: Calculate the CRC bit sequence of the uplink service scheduling information to obtain a first CRC bit sequence.

[0113] The implementation method of calculating the CRC bit sequence of the uplink service scheduling information can be the same as the implementation method of the above step S602, and will not be repeated here to avoid repeated description.

[0114] S903 . Concatenate the uplink service scheduling information and the first CRC bit sequence to obtain a first bit sequence.

[0115] In some embodiments, splicing the uplink service scheduling information and the first CRC bit sequence to obtain the first bit sequence includes: splicing the first CRC bit sequence to the end of the uplink service scheduling information to obtain the first bit sequence.

[0116] S904: Obtain downlink service data of the A-IoT service.

[0117] S905. Calculate the CRC bit sequence of the downlink service data to obtain a second CRC bit sequence.

[0118] In some embodiments, calculating the CRC bit sequence of downlink service data includes the following steps 1 to 3:

[0119] Step 1: Determine whether the length of downlink service data is greater than a first threshold length.

[0120] In some embodiments, the first threshold length is 24.

[0121] In some other embodiments, the first threshold length is 16.

[0122] In the above step 1, if the length of the downlink service data is less than or equal to the first threshold length, the following step 2 is executed, and if the length of the downlink service data is greater than the first threshold length, the following step 3 is executed:

[0123] Step b: Calculate the CRC bit sequence of the downlink service data based on the first CRC algorithm.

[0124] Step c: Calculate the CRC bit sequence of the downlink service data based on the second CRC algorithm.

[0125] Among them, the length of the CRC bit sequence obtained by the second CRC algorithm is greater than the length of the CRC bit sequence obtained by the first CRC algorithm.

[0126] In some embodiments, the first CRC algorithm is a CRC-6 algorithm and the second CRC algorithm is a CRC-16 algorithm.

[0127] S906 . Concatenate the downlink service data and the second CRC bit sequence to obtain a second bit sequence.

[0128] In some embodiments, splicing the downlink service data and the second CRC bit sequence to obtain the second bit sequence includes: splicing the second CRC bit sequence to the end of the downlink service data.

[0129] S907 . Concatenate the first bit sequence and the second bit sequence to obtain a third bit sequence.

[0130] In some embodiments, concatenating the first bit sequence and the second bit sequence to obtain a third bit sequence includes: concatenating the second bit sequence to the end of the first bit sequence.

[0131] Since concatenating the first bit sequence and the second bit sequence will concatenate the second bit sequence to the end of the first bit sequence, the terminal device can detect the uplink service scheduling information at the head of the downlink message, avoiding the overhead caused by blind detection of the uplink service scheduling information by the terminal device.

[0132] S908. Perform linear encoding on the third bit sequence to obtain a fourth bit sequence.

[0133] In some embodiments, linearly encoding the third bit sequence to obtain a fourth bit sequence includes: performing Manchester encoding on the third bit sequence to obtain the fourth bit sequence.

[0134] S909: Modulate the fourth bit sequence to obtain a modulated signal.

[0135] In some embodiments, modulating the fourth bit sequence includes: performing OOK modulation on the fourth bit sequence.

[0136] S910. Add a downlink pilot code to the modulated signal to obtain a downlink message.

[0137] In some embodiments, adding a downlink pilot code to a modulated signal includes: determining whether the length of the modulated signal is greater than a second threshold length, and when the length of the modulated signal is less than or equal to the second threshold length, adding a downlink preamble code and a downlink post-synchronization code to the head of the modulated signal.

[0138] For example, refer to Fig.10 As shown, the downlink message obtained based on the above steps S901 to S910 includes: a downlink preamble code 101, uplink service scheduling information 102, a first CRC bit sequence 103, downlink service data 104, a second CRC bit sequence 105 and a downlink post-synchronization code 106.

[0139] In some embodiments, adding a downlink pilot code to a modulated signal includes: determining whether the length of the modulated signal is greater than a second threshold length, and if the length of the modulated signal is greater than the second threshold length, adding a downlink preamble code to the head of the modulated signal, adding a downlink intermediate code between the head and tail of the modulated signal, and adding a downlink post-synchronization code to the tail of the modulated signal.

[0140] For example, refer to Fig.11 As shown, the downlink message obtained based on the above steps S901 to S910 includes: a downlink preamble code 111, uplink service scheduling information 112, a first CRC bit sequence 113, a downlink mid-code 114, downlink service data 115, a second CRC bit sequence 116 and a downlink post-synchronization code 117.

[0141] In some embodiments, the method for transmitting uplink service scheduling information further includes: before linearly encoding the third bit sequence, performing a block repetition operation on the fourth bit sequence.

[0142] In some embodiments, the method for transmitting uplink service scheduling information further includes: before modulating the fourth bit sequence, performing a scrambling operation on the fourth bit sequence.

[0143] As an extension and refinement of the above embodiment, the present application embodiment provides another method for transmitting uplink service scheduling information, referring to Fig.12 As shown, the method for transmitting uplink service scheduling information includes the following steps:

[0144] S121. Obtain uplink service scheduling information of the A-IoT service.

[0145] S122. Obtain downlink service data of the A-IoT service.

[0146] S123: Concatenate the uplink service scheduling information and the downlink service data to obtain a fifth bit sequence.

[0147] In some embodiments, splicing the uplink service scheduling information and the downlink service data to obtain the fifth bit sequence includes: splicing the downlink service data to the end of the uplink service scheduling information to obtain the fifth bit sequence.

[0148] Since the downlink service data is spliced ​​at the end of the uplink service scheduling information when the uplink service scheduling information and the downlink service data are spliced, the terminal device can detect the uplink service scheduling information at the head of the downlink message, avoiding the overhead caused by blindly detecting the uplink service scheduling information.

[0149] S124. Calculate the CRC bit sequence of the fifth bit sequence to obtain a third CRC bit sequence.

[0150] In some embodiments, calculating the CRC bit sequence of the fifth bit sequence includes the following steps I to III:

[0151] Step I: determine whether the length of the fifth bit sequence is greater than a first threshold length.

[0152] In some embodiments, the first threshold length is 24.

[0153] In some other embodiments, the first threshold length is 16.

[0154] In the above step I, if the length of the fifth bit sequence is less than or equal to the first threshold length, the following step II is performed, and if the length of the fifth bit sequence is greater than the first threshold length, the following step III is performed:

[0155] Step II: Calculate the CRC bit sequence of the fifth bit sequence based on the first CRC algorithm.

[0156] Step III: Calculate the CRC bit sequence of the fifth bit sequence based on the second CRC algorithm.

[0157] Among them, the length of the CRC bit sequence obtained by the second CRC algorithm is greater than the length of the CRC bit sequence obtained by the first CRC algorithm.

[0158] In some embodiments, the first CRC algorithm is a CRC-6 algorithm and the second CRC algorithm is a CRC-16 algorithm.

[0159] S125. Concatenate the fifth bit sequence and the third CRC bit sequence to obtain a sixth bit sequence.

[0160] In some embodiments, concatenating the fifth bit sequence and the third CRC bit sequence to obtain a sixth bit sequence includes: concatenating the third CRC bit sequence to the end of the fifth bit sequence to obtain the sixth bit sequence.

[0161] S126. Linearly encode the sixth bit sequence to obtain a seventh bit sequence.

[0162] S127. Modulate the seventh bit sequence to obtain a modulated signal.

[0163] S128. Add a downlink pilot code to the modulated signal to obtain a downlink message.

[0164] In some embodiments, adding a downlink pilot code to a modulated signal includes: determining whether the length of the modulated signal is greater than a second threshold length, and when the length of the modulated signal is less than or equal to the second threshold length, adding a downlink preamble code and a downlink post-synchronization code to the head of the modulated signal.

[0165] For example, refer to Fig.13 As shown, the downlink message obtained based on the above steps S121 to S128 includes: a downlink preamble 131, uplink service scheduling information 132, downlink service data 133, a third CRC bit sequence 134 and a downlink post-synchronization code 135.

[0166] In some embodiments, adding a downlink pilot code to a modulated signal includes: determining whether the length of the modulated signal is greater than a second threshold length, and if the length of the modulated signal is greater than the second threshold length, adding a downlink preamble code to the head of the modulated signal, adding a downlink intermediate code between the head and tail of the modulated signal, and adding a downlink post-synchronization code to the tail of the modulated signal.

[0167] For example, refer to Fig.14 As shown, the downlink message obtained based on the above steps S901 to S910 includes: a downlink preamble code 141, uplink service scheduling information 142, a downlink mid-code 143, downlink service data 144, a third CRC bit sequence 145 and a downlink post-synchronization code 146.

[0168] In some embodiments, the method for transmitting uplink service scheduling information further includes: performing a block repetition operation on the sixth bit sequence before linear encoding the sixth bit sequence.

[0169] In some embodiments, the method for transmitting uplink service scheduling information further includes: before modulating the seventh bit sequence, performing a scrambling operation on the seventh bit sequence.

[0170] Reference Fig.15 As shown, some embodiments of the present application further provide a network side device 1500, and the network side device 1500 includes:

[0171] An acquisition unit 151 is used to acquire uplink service scheduling information of the A-IoT service;

[0172] A generating unit 152, configured to generate a downlink message according to the uplink service scheduling information;

[0173] The sending unit 153 is used to send a downlink message to the terminal device via the PRDCH.

[0174] As an optional implementation mode of the embodiment of the present application, the generation unit 152 is specifically used to calculate the CRC bit sequence of the uplink service scheduling information to obtain a first CRC bit sequence; concatenate the uplink service scheduling information and the first CRC bit sequence to obtain a first bit sequence; linearly encode the first bit sequence to obtain a second bit sequence; modulate the second bit sequence to obtain a modulated signal; and add a downlink pilot code to the modulated signal to obtain a downlink message.

[0175] As an optional implementation of the embodiment of the present application, the generating unit 152 is specifically used to determine whether the length of the uplink service scheduling information is greater than the first threshold length; if the length of the uplink service scheduling information is less than or equal to the first threshold length, the CRC bit sequence of the uplink service scheduling information is calculated based on the first CRC algorithm; if the length of the uplink service scheduling information is greater than the first threshold length, the CRC bit sequence of the uplink service scheduling information is calculated based on the second CRC algorithm;

[0176] Among them, the length of the CRC bit sequence obtained by the second CRC algorithm is greater than the length of the CRC bit sequence obtained by the first CRC algorithm.

[0177] As an optional implementation of the embodiment of the present application, the generation unit 152 is specifically used to obtain downlink service data of the A-IoT service; and generate a downlink message according to the uplink service scheduling information and the downlink service data.

[0178] As an optional implementation manner of an embodiment of the present application, the generation unit 152 is specifically used to calculate the CRC bit sequence of the uplink service scheduling information to obtain a first CRC bit sequence; splice the uplink service scheduling information and the first CRC bit sequence to obtain the first bit sequence; calculate the CRC bit sequence of the downlink service data to obtain a second CRC bit sequence; splice the downlink service data and the second CRC bit sequence to obtain the second bit sequence; splice the first bit sequence and the second bit sequence to obtain a third bit sequence; linearly encode the third bit sequence to obtain a fourth bit sequence; modulate the fourth bit sequence to obtain a modulated signal; and add a downlink pilot code to the modulated signal to obtain a downlink message.

[0179] As an optional implementation of the embodiment of the present application, the generating unit 152 is specifically configured to concatenate the second bit sequence to the end of the first bit sequence to obtain a third bit sequence.

[0180] As an optional implementation mode of the embodiment of the present application, the generation unit 152 is specifically used to splice the uplink service scheduling information and the downlink service data to obtain a fifth bit sequence; calculate the CRC bit sequence of the fifth bit sequence to obtain a third CRC bit sequence; splice the fifth bit sequence and the third CRC bit sequence to obtain a sixth bit sequence; linearly encode the sixth bit sequence to obtain a seventh bit sequence; modulate the seventh bit sequence to obtain a modulated signal; and add a downlink pilot code to the modulated signal to obtain a downlink message.

[0181] As an optional implementation of the embodiment of the present application, the generating unit 152 is specifically configured to concatenate the downlink service data to the end of the uplink service scheduling information to obtain a fifth bit sequence.

[0182] As an optional implementation of the embodiment of the present application, the generation unit 152 is specifically used to add a downlink preamble code to the header of the modulated signal.

[0183] As an optional implementation of the embodiment of the present application, the generating unit 152 is specifically configured to add a downlink post-synchronization code to the tail of the modulated signal.

[0184] As an optional implementation of the embodiment of the present application, the generation unit 152 is specifically used to determine whether the length of the modulated signal is greater than the second threshold length; if the length of the modulated signal is greater than the second threshold length, a downlink intermediate code is added between the head and the tail of the modulated signal.

[0185] As an optional implementation of the embodiment of the present application, the generation unit 152 is specifically used to add the downlink intermediate code at the midpoint of the modulated signal; or, add the downlink intermediate code at the second threshold length of the modulated signal.

[0186] As an optional implementation manner of the embodiment of the present application, the uplink service scheduling information includes:

[0187] At least one of uplink time domain resource allocation, uplink frequency domain resource allocation, uplink modulation and coding format, uplink transmission block size, reader identification code, uplink midamble information, uplink repetition number, and uplink time slice length.

[0188] As an optional implementation mode of the embodiment of the present application, the protocol data unit corresponding to the uplink service scheduling information includes: MAC-CE and a media access control subheader;

[0189] Uplink service scheduling information is carried by MAC-CE.

[0190] As an optional implementation of the embodiment of the present application, MAC-CE includes: four octets;

[0191] Among them, the uplink time domain resource allocation is carried on the second bit to the fifth bit of the first octet, the uplink modulation and coding format is carried on the sixth bit to the eighth bit of the first octet, the uplink transmission block size is carried on the first bit to the fourth bit of the second octet, the uplink frequency domain resource allocation is carried on the fifth bit to the eighth bit of the second octet, the reader identification code is carried on the third bit to the eighth bit of the third octet, the uplink intermediate code information is carried on the second bit and the third bit of the fourth octet, the uplink repetition number is carried on the fourth bit and the fifth bit of the fourth octet, and the uplink time slice length is carried on the sixth bit to the eighth bit of the fourth octet.

[0192] As an optional implementation of the embodiment of the present application, the media access control subheader includes: two octets;

[0193] Among them, the value of the second bit of the first octet is used to indicate the unit of the size of MAC-CE, the values ​​of the third bit to the eighth bit of the first octet are used to indicate the type of MAC-CE, and the values ​​of the first bit to the eighth bit of the second octet are used to indicate the numerical value of the size of MAC-CE.

[0194] The network side device provided in the embodiment of the present application can execute the method for transmitting uplink service scheduling information provided in the above embodiment, and can achieve the same or similar effect. To avoid redundancy, it will not be described in detail here.

[0195] Some embodiments of the present application provide an electronic device, including: a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to implement the method for transmitting uplink service scheduling information of any of the above embodiments when executing the computer program.

[0196] Some embodiments of the present application provide a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a computing device, the computing device implements the method for transmitting uplink service scheduling information of any of the above embodiments.

[0197] Some embodiments of the present application provide a chip, which includes a processor and a memory, wherein the memory is used to store programs or instructions that can be run on the processor, and the processor is used to execute the programs or instructions so that the method for transmitting uplink service scheduling information in any of the above embodiments is executed.

[0198] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

[0199] For the convenience of explanation, the above description has been made in conjunction with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or limit the embodiments to the specific forms disclosed above. Based on the above teachings, various modifications and variations can be obtained. The selection and description of the above embodiments are to better explain the principles and practical applications, so that those skilled in the art can better use the embodiments and various different variations of the embodiments suitable for specific use considerations.

Claims

1. A method for transmitting uplink service scheduling information, characterized in that: include: Obtain uplink service scheduling information for artificial intelligence Internet of Things (A-IoT) services; Generate a downlink message according to the uplink service scheduling information; The downlink message is sent to the terminal device via the physical reader device channel PRDCH.

2. The method according to claim 1, characterized in that The generating a downlink message according to the uplink service scheduling information includes: Calculating a cyclic redundancy check (CRC) bit sequence of the uplink service scheduling information to obtain a first CRC bit sequence; splicing the uplink service scheduling information and the first CRC bit sequence to obtain a first bit sequence; Linearly encoding the first bit sequence to obtain a second bit sequence; modulating the second bit sequence to obtain a modulated signal; A downlink pilot code is added to the modulated signal to obtain the downlink message.

3. The method according to claim 2, characterized in that The calculating of a cyclic redundancy check (CRC) bit sequence of the uplink service scheduling information comprises: Determining whether the length of the uplink service scheduling information is greater than a first threshold length; If the length of the uplink service scheduling information is less than or equal to the first threshold length, calculating a CRC bit sequence of the uplink service scheduling information based on a first CRC algorithm; If the length of the uplink service scheduling information is greater than the first threshold length, calculating a CRC bit sequence of the uplink service scheduling information based on a second CRC algorithm; The length of the CRC bit sequence obtained by the second CRC algorithm is greater than the length of the CRC bit sequence obtained by the first CRC algorithm.

4. The method according to claim 2, characterized in that: The generating a downlink message according to the uplink service scheduling information includes: Obtaining downlink service data of the A-IoT service; The downlink message is generated according to the uplink service scheduling information and the downlink service data.

5. The method according to claim 4, characterized in that The generating the downlink message according to the uplink service scheduling information and the downlink service data includes: Calculating a CRC bit sequence of the uplink service scheduling information to obtain a first CRC bit sequence; splicing the uplink service scheduling information and the first CRC bit sequence to obtain a first bit sequence; Calculating a CRC bit sequence of the downlink service data to obtain a second CRC bit sequence; splicing the downlink service data and the second CRC bit sequence to obtain a second bit sequence; concatenating the first bit sequence and the second bit sequence to obtain a third bit sequence; Linearly encoding the third bit sequence to obtain a fourth bit sequence; modulating the fourth bit sequence to obtain a modulated signal; A downlink pilot code is added to the modulated signal to obtain the downlink message.

6. The method according to claim 5, characterized in that The step of concatenating the first bit sequence and the second bit sequence to obtain a third bit sequence includes: The second bit sequence is concatenated to the end of the first bit sequence to obtain the third bit sequence.

7. The method according to claim 4, characterized in that The generating the downlink message according to the uplink service scheduling information and the downlink service data includes: splicing the uplink service scheduling information and the downlink service data to obtain a fifth bit sequence; Calculating a CRC bit sequence of the fifth bit sequence to obtain a third CRC bit sequence; splicing the fifth bit sequence and the third CRC bit sequence to obtain a sixth bit sequence; Linearly encoding the sixth bit sequence to obtain a seventh bit sequence; modulating the seventh bit sequence to obtain a modulated signal; A downlink pilot code is added to the modulated signal to obtain the downlink message.

8. The method according to claim 7, characterized in that The step of splicing the uplink service scheduling information and the downlink service data to obtain a fifth bit sequence includes: The downlink service data is concatenated to the end of the uplink service scheduling information to obtain the fifth bit sequence.

9. The method according to claim 2, 5 or 7, characterized in that: The adding a downlink pilot code to the modulated signal comprises: A downlink preamble is added to the head of the modulated signal.

10. The method according to claim 2, 5 or 7, characterized in that: The adding a downlink pilot code to the modulated signal comprises: A downlink post-synchronization code is added to the tail of the modulated signal.

11. The method according to claim 2, 5 or 7, characterized in that: The adding a downlink pilot code to the modulated signal comprises: Determining whether the length of the modulated signal is greater than a second threshold length; If the length of the modulated signal is greater than the second threshold length, a downlink midamble is added between the head and the tail of the modulated signal.

12. The method according to claim 11, characterized in that The adding of a downlink midamble between the head and the tail of the modulated signal comprises: Adding the downlink midamble to the midpoint of the modulated signal; Alternatively, the downlink midamble is added to the second threshold length of the modulated signal.

13. The method according to claim 1, characterized in that The uplink service scheduling information includes: At least one of uplink time domain resource allocation, uplink frequency domain resource allocation, uplink modulation and coding format, uplink transmission block size, reader identification code, uplink midamble information, uplink repetition number, and uplink time slice length.

14. The method according to claim 13, characterized in that The protocol data unit corresponding to the uplink service scheduling information includes: a media access control element MAC-CE and a media access control subheader; The uplink service scheduling information is carried by the MAC-CE.

15. The method according to claim 14, characterized in that The MAC-CE comprises: four octets; Among them, the uplink time domain resource allocation is carried on the second bit to the fifth bit of the first octet, the uplink modulation and coding format is carried on the sixth bit to the eighth bit of the first octet, the uplink transmission block size is carried on the first bit to the fourth bit of the second octet, the uplink frequency domain resource allocation is carried on the fifth bit to the eighth bit of the second octet, the reader identification code is carried on the third bit to the eighth bit of the third octet, the uplink intermediate code information is carried on the second bit and the third bit of the fourth octet, the uplink repetition number is carried on the fourth bit and the fifth bit of the fourth octet, and the uplink time slice length is carried on the sixth bit to the eighth bit of the fourth octet.

16. The method according to claim 14, characterized in that The media access control subheader includes: two octets; Among them, the value of the second bit of the first octet is used to indicate the unit of the size of MAC-CE, the values ​​of the third bit to the eighth bit of the first octet are used to indicate the type of MAC-CE, and the values ​​of the first bit to the eighth bit of the second octet are used to indicate the numerical value of the size of MAC-CE.

17. A transmission device for uplink service scheduling information, characterized in that: include: An acquisition unit, used to acquire uplink service scheduling information of an artificial intelligence Internet of Things A-IoT service; A generating unit, configured to generate a downlink message according to the uplink service scheduling information; The sending unit is used to send the downlink message to the terminal device through the physical reader device channel PRDCH.

18. An electronic device, characterized in that: include: A memory and a processor, wherein the memory stores a computer program, and the processor is configured to implement the method for transmitting uplink service scheduling information as described in any one of claims 1 to 16 when executing the computer program.

19. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a computing device, the computing device implements the method for transmitting uplink service scheduling information according to any one of claims 1-16.

20. A chip, characterized in that: The chip includes a processor and a memory, the memory is used to store programs or instructions that can be run on the processor, and the processor is used to execute the programs or instructions so that the method for transmitting uplink service scheduling information as described in any one of claims 1-16 is executed.

Images