A method and apparatus for transmitting uplink service scheduling information

Abstract

The application provides a transmission method and device for 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 a PRDCH. Some embodiments of the application are used for reducing the power consumption of the terminal device in an A-IoT communication scenario.

Description

Technical Field

[0001] This application relates to the field of communication technology. More specifically, it relates to a method and apparatus for transmitting uplink service scheduling information. Background Technology

[0002] Passive Internet of Things (IoT) is an IoT technology that does not require battery power. It communicates by supplying power to passive terminal devices through readers. As passive IoT technology continues to evolve, Ambient IoT (A-IoT) has emerged as a related technology.

[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, the terminal devices detect the downlink service data and uplink service scheduling information sent by the 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 signals sent by the network-side devices. Therefore, A-IoT communication scenarios have very stringent requirements for the power consumption of terminal devices. However, having the terminal device detect the downlink service data and uplink service scheduling information sent by the network-side devices on different downlink channels increases the terminal device's power consumption, leading to a significant decrease in the terminal device's battery life and affecting the duration and stability of normal operation. Summary of the Invention

[0004] An exemplary embodiment of this application provides a method and apparatus for transmitting uplink service scheduling information, which reduces the power consumption of terminal devices in A-IoT communication scenarios.

[0005] The technical solutions provided by some embodiments of this application are as follows:

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

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

[0008] Generate downlink messages based on the uplink service scheduling information;

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

[0010] Secondly, some embodiments of this application provide an uplink service scheduling information transmission apparatus, including:

[0011] The acquisition unit is used to acquire the uplink service scheduling information of the A-IoT service;

[0012] The generation unit is used to generate downlink messages based on the uplink service scheduling information;

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

[0014] Thirdly, some embodiments of this application provide an electronic device, including: a memory and a processor, wherein the memory stores a computer program, and the processor is configured to implement the uplink service scheduling information transmission method described in the first aspect when executing the computer program.

[0015] Fourthly, some embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a computing device, causes the computing device to implement the uplink service scheduling information transmission method described in the first aspect.

[0016] Fifthly, some embodiments of this application provide a chip including a processor and a memory, the memory being used to store programs or instructions executable on the processor, and the processor being used to execute the programs or instructions to enable the uplink service scheduling information transmission method described in the first aspect.

[0017] Sixthly, some embodiments of this application provide a computer program product that, when run on a computer, enables the computer to implement the uplink service scheduling information transmission method described in the first aspect.

[0018] As can be seen from the above technical solutions, the uplink service scheduling information transmission method provided in the above embodiments first obtains the uplink service scheduling information of A-IoT services, then generates downlink messages based on the uplink service scheduling information, and sends the downlink messages to the terminal device through the physical reader device channel. Since the uplink service scheduling information transmission method provided in this application embodiment can send the downlink messages generated based on the uplink service scheduling information to the terminal device through the PRDCH, and the PRDCH is the 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, without having to detect the uplink service scheduling information and downlink service data separately on different channels. Therefore, this application embodiment can reduce the power consumption of the terminal device in the A-IoT communication scenario. Attached Figure Description

[0019] To more clearly illustrate the implementation methods in some embodiments or related technologies of this application, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0020] Figure 1 A topology diagram of a communication system provided in some embodiments is shown;

[0021] Figure 2 A topology diagram of a communication system provided in some other embodiments is shown;

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

[0023] Figure 4 The diagram shows a data structure diagram of MAC-CE provided in some embodiments;

[0024] Figure 5 The diagram shows a schematic of the data structure of the MAC subheader provided in some embodiments;

[0025] Figure 6 A flowchart of steps for transmitting uplink service scheduling information is shown in some other embodiments;

[0026] Figure 7 The diagram shows a schematic representation of the structure of a downlink message in some embodiments;

[0027] Figure 8 Schematic diagrams of the structure of downlink messages in other embodiments are shown;

[0028] Figure 9 A flowchart of steps for transmitting uplink service scheduling information is shown in some other embodiments;

[0029] Figure 10 Schematic diagrams of the structure of downlink messages in other embodiments are shown;

[0030] Figure 11 Schematic diagrams of the structure of downlink messages in other embodiments are shown;

[0031] Figure 12 A flowchart of steps for transmitting uplink service scheduling information is shown in some other embodiments;

[0032] Figure 13 Schematic diagrams of the structure of downlink messages in other embodiments are shown;

[0033] Figure 14Schematic diagrams of the structure of downlink messages in other embodiments are shown;

[0034] Figure 15 The present application provides schematic diagrams of the network-side devices in some embodiments. Detailed Implementation

[0035] It should be noted that the brief descriptions of terms in this application are only for the purpose of facilitating the understanding of the embodiments described below. In order to make the purpose and implementation of this application clearer, the exemplary embodiments of this application will be clearly and completely described below with reference to the accompanying drawings of the exemplary embodiments of this application. Obviously, the exemplary embodiments described are only some embodiments of this application, and not all embodiments.

[0036] This application is not intended to limit the implementation of the invention. Unless otherwise stated, these terms should be understood in their ordinary and common sense.

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

[0038] The use of phrases such as "some implementations" or "some embodiments" in the specification indicates that the described implementations or embodiments may include specific features, structures, or characteristics, but not every embodiment may necessarily include that specific feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same implementation. Additionally, when describing a specific feature, structure, or characteristic in connection with an embodiment, it is considered that implementing that feature, structure, or characteristic in connection with other implementations (whether explicitly described herein or not) is within the knowledge of those skilled in the art.

[0039] The communication system provided in the embodiments of this application will be described first below.

[0040] Figure 1 This is a schematic diagram of the topology of a communication system provided in some embodiments of this application. (Refer to...) 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 via the A-IoT uplink and receive A-IoT downlink information sent by the network-side device 11 via the A-IoT downlink. Correspondingly, the network-side device 11 can receive uplink A-IoT information sent by the terminal device 12 via the A-IoT uplink and can also send A-IoT downlink information to the terminal device 12 via 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 via the NR uplink and receive NR downlink information sent by the network-side device via the NR downlink. Correspondingly, the network-side device 11 can receive uplink NR information sent by the terminal device 12 via the NR uplink and can also send NR downlink information to the terminal device 12 via the NR downlink.

[0042] Terminal device 12 can be any device that supports providing voice and / or other service data connectivity to users. For example, terminal devices can be portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the wireless access network, as well as Personal Communication Service (PCS) telephones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), etc. Wireless terminals can also be mobile devices, UE terminals, access terminals, wireless communication equipment, terminal units, terminal stations, mobile stations, mobile stations, remote stations, remote terminals, subscriber units, subscriber stations, user agents, etc. As an example, Figure 1 Taking terminal device 12 as an example, which is an A-IoT device and a tag; network-side device 11 includes, but is not limited to, reader, base station (BS), access point device (Node B, NB), node, etc.

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

[0044] In other embodiments, reference is made to 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 22 can send uplink A-IoT information to the first network-side device 21 via the A-IoT uplink, and correspondingly, the first network-side device 21 can receive uplink A-IoT information sent by the terminal device 23 via the A-IoT uplink. The second network-side device 22 can send A-IoT downlink information to the terminal device 23 via the A-IoT downlink, and correspondingly, the terminal device 23 can receive A-IoT downlink information sent by the second network-side device 22 via 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 through this data transmission link. The first network-side device 21 and the second network-side device include, but are not limited to, readers, base stations (BS), access point devices (Node B, NB), nodes, etc.

[0046] It should be noted that, Figure 1 and Figure 2 The communication system provided in this application embodiment is a possible communication system for the transmission method of uplink service scheduling information. However, this application embodiment is not limited to this. The communication system in which the transmission method of uplink service scheduling information provided in this application embodiment is applied may include more communication devices. This application embodiment does not limit this, and the communication system shall be subject to the fact that it can support the transmission method of uplink service scheduling information provided in this application embodiment.

[0047] This application provides a method for transmitting uplink service scheduling information, which is applied to network-side equipment, such as a base station. Figure 3 This application provides a schematic flowchart illustrating the method for transmitting uplink service scheduling information according to an embodiment of the present application. Figure 3 As shown, the method for transmitting the uplink service scheduling information may include:

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

[0049] In this application embodiment, the uplink service scheduling information refers to relevant information sent by the network-side device to the terminal device for managing and controlling the transmission (uplink direction) of service data and / or control information from the terminal device to the network-side device.

[0050] In some embodiments, uplink service scheduling information may include one or more of the following: uplink time domain resource allocation (TDRA) for instructing the terminal device to use time domain resources when performing uplink transmission; uplink frequency domain resource allocation (FDRA) for instructing the terminal device to use frequency domain resources when performing uplink transmission; modulation and coding scheme (MCS) for instructing the terminal device to use modulation and coding scheme (MCS) when performing uplink transmission; transport block size (TB size) for instructing the size of transport blocks when performing uplink transmission; reader identification (ID); information for instructing whether the terminal device uses uplink midamble when performing uplink transmission; information for instructing the number of repetitions when performing uplink transmission; and information for instructing the uplink chip length when performing uplink transmission.

[0051] The uplink time slice length can be identified by the number of on-off keying symbols (OOKs) that can be transmitted in an uplink orthogonal frequency division multiplexing (OFDM) symbol.

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

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

[0054] In some embodiments, the Protocol Data Unit (PDU) corresponding to the uplink service scheduling information includes a Medium Access Control-Control Element (MAC-CE) and a Medium Access Control subheader (MAC subheader), and the uplink service scheduling information is carried through the MAC-CE.

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

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

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

[0058] Reference Figure 5 As shown, in some embodiments, the Media Access Control (MAC) subheader includes two octets (Oct1 and Oct2). The value F on the second bit of the first octet Oct1 represents the unit of the MAC-CE size, the values ​​from the third to the eighth bit of the first octet Oct1 represent the type of the MAC-CE, and the value L on the first to the eighth bit of the second octet Oct2 represents the numerical value of the MAC-CE size.

[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 can be shown in Table 1 below:

[0061] Table 1

[0062] LCID MAC-CE type 0 64-bit common control channel 1～32 Logical channel identifier …… …… 65 A-IoT uplink services

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

[0064] S32. Generate downlink messages based on uplink service scheduling information.

[0065] In some embodiments, generating downlink messages based on uplink service scheduling information includes performing operations such as cyclic redundancy check (CRC) appending, channel coding, block repetition, linear coding, scrambling, modulation, and pilot code addition on the uplink service scheduling information to obtain downlink messages.

[0066] S33. Send downlink messages to the terminal device through the Physical Reader Device Channel (PRDCH).

[0067] The uplink service scheduling information transmission method provided in this application first obtains the uplink service scheduling information of A-IoT services, then generates downlink messages based on the uplink service scheduling information, and sends the downlink messages to the terminal device through the physical reader device channel. Since the uplink service scheduling information transmission method provided in this application can send the downlink messages generated based on the uplink service scheduling information to the terminal device via the PRDCH, and the PRDCH is the channel for network-side devices 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, without needing to detect them separately on different channels. Therefore, this application embodiment can reduce the power consumption of the terminal device in A-IoT communication scenarios.

[0068] As an extension and refinement of the above embodiments, this application 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 for A-IoT services.

[0070] S602. Calculate the Cyclic Redundancy Check (CRC) bit sequence of the uplink service scheduling information to obtain the 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 upstream service scheduling information is greater than the first threshold length.

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

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

[0075] In step a above, if the length of the uplink service scheduling information is less than or equal to the first threshold length, then step b is executed; if the length of the uplink service scheduling information is greater than the first threshold length, then 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] 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 the CRC-6 algorithm, and the second CRC algorithm is the CRC-16 algorithm.

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

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

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

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

[0084] From the polynomial expressions of the CRC-6 algorithm and the CRC-16 algorithm, we can see that when using the CRC-6 algorithm, the length of the obtained CRC bit sequence is 6, while when using the CRC-16 algorithm, the length of the obtained CRC bit sequence is 16.

[0085] In the above embodiments, 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 embodiments 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 uplink service scheduling information transmission.

[0086] S603. Assemble the upstream service scheduling information and the first CRC bit sequence to obtain the first bit sequence.

[0087] In some embodiments, concatenating uplink service scheduling information and a first CRC bit sequence to obtain a first bit sequence includes: concatenating the first CRC bit sequence to the end of the uplink service scheduling information to obtain a 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 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. Perform linear encoding on the first bit sequence to obtain the second bit sequence.

[0090] In some embodiments, linear encoding of the first bit sequence to obtain the second bit sequence includes: Manchester encoding of the first bit sequence to obtain the second bit sequence.

[0091] Manchester encoding is a synchronous clock encoding technique commonly used in local area networks (LANs). It represents "0" or "1" by switching between high and low voltage levels. Each bit has a transition in the middle, specifically changing a '0' in the third bit sequence to a '10', and changing a '1' in the third bit sequence to a '01'.

[0092] Let the first bit sequence be 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 the 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, OOK modulation of 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 downlink pilot code to the modulation signal to obtain downlink messages.

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

[0098] In some embodiments, the downlink preamble includes a start-indicator part and a timing acquisition signal. The start-indicator part indicates the start of uplink service scheduling information transmission, and the timing acquisition signal performs clock synchronization.

[0099] In some embodiments, adding downlink pilot codes to the modulated signal includes adding 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: downlink preamble 71, uplink service scheduling information 72, first CRC bit sequence 73, and downlink synchronization code 74.

[0101] In some embodiments, adding downlink pilot codes to the modulated signal further 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, then adding downlink intermediate codes between the head and tail of the modulated signal.

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

[0103] In some embodiments, a downlink intermediate code 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, a front uplink service scheduling information 82, a downlink intermediate code 83, a rear uplink service scheduling information 84, a first CRC bit sequence 85, and a downlink post-synchronization code 86. The front uplink service scheduling information 82 and the rear uplink service scheduling information 84 are two parts of data obtained by segmenting the uplink service scheduling information 82 using the downlink intermediate code 83.

[0105] In some embodiments, the method for transmitting uplink service scheduling information further includes: performing a block repetition operation on the first bit sequence before linearly encoding 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 a 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 make the uplink message contain two first bit sequences. This way, even if one of the first bit sequences is erroneous during transmission, the correct uplink service scheduling information can still be obtained based on the other first bit sequence, thereby improving the robustness of uplink service scheduling information transmission.

[0108] In some embodiments, the method for transmitting uplink service scheduling information further includes: scrambling the second bit sequence before modulating it.

[0109] Scrambling the second bit sequence before modulation can improve the security and relevance of uplink service scheduling information.

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

[0111] S901. Obtain uplink service scheduling information for A-IoT services.

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

[0113] The method for calculating the CRC bit sequence of the uplink service scheduling information can be the same as the method for step S602 above. To avoid repetition, it will not be repeated here.

[0114] S903. Assemble the upstream service scheduling information and the first CRC bit sequence to obtain the first bit sequence.

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

[0116] S904. Obtain downlink business data for A-IoT services.

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

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

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

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

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

[0122] In step 1 above, if the length of the downlink service data is less than or equal to the first threshold length, then step 2 is executed; if the length of the downlink service data is greater than the first threshold length, then 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] 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 the CRC-6 algorithm, and the second CRC algorithm is the CRC-16 algorithm.

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

[0128] In some embodiments, concatenating downlink service data and a second CRC bit sequence to obtain a second bit sequence includes: concatenating 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 the third bit sequence.

[0130] In some embodiments, concatenating the first bit sequence and the second bit sequence to obtain the 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 append the second bit sequence to the end of the first bit sequence, the terminal device can detect uplink service scheduling information in the header of the downlink message, thus avoiding the overhead of blind detection of uplink service scheduling information by the terminal device.

[0132] S908. Linearly encode the third bit sequence to obtain the fourth bit sequence.

[0133] In some embodiments, linear encoding of the third bit sequence to obtain the fourth bit sequence includes: Manchester encoding of the third bit sequence to obtain the fourth bit sequence.

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

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

[0136] S910: Add downlink pilot code to the modulation signal to obtain downlink messages.

[0137] In some embodiments, adding downlink pilot codes to the 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 less than or equal to the second threshold length, adding a downlink preamble and a downlink post-synchronization code to the header of the modulated signal.

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

[0139] In some embodiments, adding downlink pilot codes to the 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 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 Figure 11 As shown, the downlink message obtained based on the above steps S901 to S910 includes: downlink preamble 111, uplink service scheduling information 112, first CRC bit sequence 113, downlink intermediate code 114, downlink service data 115, second CRC bit sequence 116, and downlink synchronization code 117.

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

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

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

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

[0145] S122. Obtain downlink business data for A-IoT services.

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

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

[0148] Since downlink service data is appended to the end of the uplink service scheduling information when splicing uplink service scheduling information and downlink service data, terminal devices can detect uplink service scheduling information at the beginning of downlink messages, avoiding the overhead of blindly detecting uplink service scheduling information.

[0149] S124. Calculate the CRC bit sequence of the fifth bit sequence to obtain the 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 the first threshold length.

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

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

[0154] In step I above, if the length of the fifth bit sequence is less than or equal to the first threshold length, then step II is executed; if the length of the fifth bit sequence is greater than the first threshold length, then step III is executed.

[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] 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 the CRC-6 algorithm, and the second CRC algorithm is the CRC-16 algorithm.

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

[0160] In some embodiments, concatenating the fifth bit sequence and the third CRC bit sequence to obtain the 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. Perform linear encoding on the sixth bit sequence to obtain the seventh bit sequence.

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

[0163] S128. Add downlink pilot code to the modulation signal to obtain downlink messages.

[0164] In some embodiments, adding downlink pilot codes to the 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 less than or equal to the second threshold length, adding a downlink preamble and a downlink post-synchronization code to the header of the modulated signal.

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

[0166] In some embodiments, adding downlink pilot codes to the 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 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 Figure 14 As shown, the downlink message obtained based on the above steps S901 to S910 includes: downlink preamble 141, uplink service scheduling information 142, downlink intermediate code 143, downlink service data 144, third CRC bit sequence 145, and downlink 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 linearly encoding the sixth bit sequence.

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

[0170] Reference Figure 15 As shown, some embodiments of this application also provide a network-side device 1500, which includes:

[0171] Acquisition unit 151 is used to acquire uplink service scheduling information of A-IoT services;

[0172] Generation unit 152 is used to generate downlink messages based on uplink service scheduling information;

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

[0174] As an optional implementation of this 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; perform linear encoding on the first bit sequence to obtain a second bit sequence; modulate the second bit sequence to obtain a modulated signal; and add downlink pilot code to the modulated signal to obtain a downlink message.

[0175] As an optional implementation of this application, the generation 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, then 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, then the CRC bit sequence of the uplink service scheduling information is calculated based on the second CRC algorithm.

[0176] 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 this application, the generation unit 152 is specifically used to obtain downlink service data of A-IoT service; and generate downlink messages based on uplink service scheduling information and downlink service data.

[0178] As an optional implementation of this application, the generation unit 152 is specifically used to calculate the CRC bit sequence of 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; calculate the CRC bit sequence of downlink service data to obtain a second CRC bit sequence; concatenate the downlink service data and the second CRC bit sequence to obtain a second bit sequence; concatenate the first bit sequence and the second bit sequence to obtain a third bit sequence; perform linear encoding on the third bit sequence to obtain a fourth bit sequence; modulate the fourth bit sequence to obtain a modulated signal; and add downlink pilot codes to the modulated signal to obtain a downlink message.

[0179] As an optional implementation of this application, the generation unit 152 is specifically used to append the second bit sequence to the end of the first bit sequence to obtain the third bit sequence.

[0180] As an optional implementation of this application, the generation unit 152 is specifically used to splice uplink service scheduling information and 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; perform linear encoding on the sixth bit sequence to obtain a seventh bit sequence; modulate the seventh bit sequence to obtain a modulated signal; and add downlink pilot code to the modulated signal to obtain a downlink message.

[0181] As an optional implementation of this application, the generation unit 152 is specifically used to concatenate downlink service data to the end of uplink service scheduling information to obtain the fifth bit sequence.

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

[0183] As an optional implementation of this application, the generation unit 152 is specifically used to add a downlink post-synchronization code to the end of the modulated signal.

[0184] As an optional implementation of this 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, then a downlink intermediate code is added between the head and tail of the modulated signal.

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

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

[0187] At least one of the following: uplink time domain resource allocation, uplink frequency domain resource allocation, uplink modulation and coding format, uplink transport block size, reader identification code, uplink intermediate code information, uplink repetition count, and uplink time slice length.

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

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

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

[0191] Specifically, the uplink time domain resource allocation is carried on bits 2 to 5 of the first octet, the uplink modulation and coding format is carried on bits 6 to 8 of the first octet, the uplink transport block size is carried on bits 1 to 4 of the second octet, the uplink frequency domain resource allocation is carried on bits 5 to 8 of the second octet, the reader identification code is carried on bits 3 to 8 of the third octet, the uplink intermediate code information is carried on bits 2 and 3 of the fourth octet, the uplink repetition count is carried on bits 4 and 5 of the fourth octet, and the uplink time slice length is carried on bits 6 to 8 of the fourth octet.

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

[0193] In this octet, the value at the second bit of the first octet represents the unit of size of the MAC-CE, the values ​​at the third to eighth bits of the first octet represent the type of the MAC-CE, and the values ​​at the first to eighth bits of the second octet represent the numerical value of the size of the MAC-CE.

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

[0195] Some embodiments of this application provide an electronic device, including: a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the uplink service scheduling information transmission method of any of the above embodiments.

[0196] Some embodiments of this application provide a computer-readable storage medium storing a computer program. When the computer program is executed by a computing device, the computing device implements the uplink service scheduling information transmission method of any of the above embodiments.

[0197] Some embodiments of this application provide a chip, which includes a processor and a memory. The memory is used to store programs or instructions that can run on the processor, and the processor is used to execute the programs or instructions to enable the transmission method of uplink scheduling information in any of the above embodiments to be executed.

[0198] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

[0199] For ease of explanation, the above description has been provided in conjunction with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the embodiments to the specific forms disclosed above. Various modifications and variations can be obtained based on the above teachings. The selection and description of the above embodiments are for the purpose of better explaining the principles and practical applications, thereby enabling those skilled in the art to better utilize the described embodiments and various different variations of 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 A-IoT services; Generate downlink messages based on the uplink service scheduling information; The downlink message is sent to the terminal device via the Physical Reader Device Channel (PRDCH). The step of generating a downlink message based on the uplink service scheduling information includes: Obtain the downlink service data of the A-IoT service; By concatenating the uplink service scheduling information and the downlink service data, a fifth bit sequence is obtained; Calculate the cyclic redundancy check (CRC) bit sequence of the fifth bit sequence to obtain the third CRC bit sequence; The fifth bit sequence and the third CRC bit sequence are concatenated to obtain the sixth bit sequence; After performing a block repetition operation on the sixth bit sequence, the sixth bit sequence is linearly encoded to obtain the seventh bit sequence; After scrambling the seventh bit sequence, the seventh bit sequence is modulated to obtain a modulated signal; Add downlink pilot code to the modulation signal to obtain the downlink message.

2. The method according to claim 1, characterized in that, The calculation of the CRC bit sequence of the fifth bit sequence includes: Determine whether the length of the fifth bit sequence is greater than the first threshold length; If the length of the fifth bit sequence is less than or equal to the first threshold length, then the CRC bit sequence of the fifth bit sequence is calculated based on the first CRC algorithm; If the length of the fifth bit sequence is greater than the first threshold length, then the CRC bit sequence of the fifth bit sequence is calculated based on the 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.

3. The method according to claim 1, characterized in that, The step of concatenating the uplink service scheduling information and the downlink service data to obtain the fifth bit sequence includes: The downlink service data is appended to the end of the uplink service scheduling information to obtain the fifth bit sequence.

4. The method according to claim 1, characterized in that, Adding downlink pilot codes to the modulated signal includes: A downlink preamble is added to the header of the modulated signal.

5. The method according to claim 1, characterized in that, Adding downlink pilot codes to the modulated signal includes: A downlink post-synchronization code is added to the end of the modulated signal.

6. The method according to claim 1, characterized in that, Adding downlink pilot codes to the modulated signal includes: 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 tail of the modulated signal.

7. The method according to claim 6, characterized in that, Adding a downlink intermediate code between the head and tail of the modulated signal includes: The downlink intermediate code is added to the midpoint of the modulated signal; Alternatively, the downlink intermediate code can be added to the second threshold length of the modulated signal.

8. The method according to claim 1, characterized in that, The uplink service scheduling information includes: At least one of the following: uplink time domain resource allocation, uplink frequency domain resource allocation, uplink modulation and coding format, uplink transport block size, reader identification code, uplink intermediate code information, uplink repetition count, and uplink time slice length.

9. The method according to claim 8, characterized in that, The protocol data unit corresponding to the uplink service scheduling information includes: Media Access Control Element (MAC-CE) and Media Access Control Subheader; The uplink service scheduling information is carried through the MAC-CE.

10. The method according to claim 9, characterized in that, The MAC-CE includes: four octets; Specifically, the uplink time-domain resource allocation is carried on the second to fifth bits of the first octet; the uplink modulation and coding format is carried on the sixth to eighth bits of the first octet; the uplink transport block size is carried on the first to fourth bits of the second octet; the uplink frequency-domain resource allocation is carried on the fifth to eighth bits of the second octet; the reader identification code is carried on the third to eighth bits of the third octet; the uplink intermediate code information is carried on the second and third bits of the fourth octet; the uplink repetition count is carried on the fourth and fifth bits of the fourth octet; and the uplink time slice length is carried on the sixth to eighth bits of the fourth octet.

11. The method according to claim 9, characterized in that, The media access control subheader includes: two octets; In this octet, the value at the second bit of the first octet represents the unit of size of the MAC-CE, the values ​​at the third to eighth bits of the first octet represent the type of the MAC-CE, and the values ​​at the first to eighth bits of the second octet represent the numerical value of the size of the MAC-CE.

12. A device for transmitting uplink service scheduling information, characterized in that, include: The acquisition unit is used to acquire uplink service scheduling information for A-IoT services; The generation unit is used to generate downlink messages based on the uplink service scheduling information; The sending unit is configured to send the downlink message to the terminal device via the Physical Reader Device Channel (PRDCH). The generation unit is specifically configured to: concatenate the uplink service scheduling information and downlink service data to obtain a fifth bit sequence; calculate the cyclic redundancy check (CRC) bit sequence of the fifth bit sequence to obtain a third CRC bit sequence; concatenate the fifth bit sequence and the third CRC bit sequence to obtain a sixth bit sequence; perform a block repetition operation on the sixth bit sequence, then perform linear encoding on the sixth bit sequence to obtain a seventh bit sequence; perform a scrambling operation on the seventh bit sequence, then modulate the seventh bit sequence to obtain a modulated signal; and add downlink pilot codes to the modulated signal to obtain the downlink message.

13. 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 execute the computer program to implement the method for transmitting uplink service scheduling information as described in any one of claims 1-11.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a computing device, causes the computing device to implement the uplink service scheduling information transmission method according to any one of claims 1-11.

15. A chip, characterized in that, The chip includes a processor and a memory, the memory being used to store programs or instructions that can run on the processor, and the processor being used to execute the programs or instructions to cause the transmission method of uplink service scheduling information as described in any one of claims 1-11 to be executed.

Images