Information transmission method and device, terminal and network equipment

Abstract

The invention provides an information transmission method and device, a terminal and network equipment, and the method is executed by the terminal and comprises the steps that an uplink count value sent by the network equipment is received, and the uplink count value is used for the terminal to generate a root key and / or execute uplink message encryption. According to the scheme, the uplink count value used for the terminal to generate the root key and / or execute uplink message encryption is directly received from the network equipment, and the terminal does not need to generate the uplink count value, so that the problem that UL NAS COUNT generated by the terminal is inconsistent with that provided by a core network in an NTN scene can be avoided.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an information transmission method, device, terminal and network equipment. Background Art

[0002] In the non-terrestrial network (NTN, i.e. satellite network) network side, there is a store and forward (S&F) scenario. In this scenario, in order to shorten the terminal transmission delay, multiple satellites will provide services for the terminal.

[0003] The existing verification process is as follows: After the terminal updates the uplink non-access layer count (UL NAS COUNT) value, it generates KeNB (i.e., the root key) and reports the UL NAS COUNT value to the core network's access and mobility management function (Access and Mobility Management Function, AMF). AMF generates KeNB based on the UL NAS COUNT reported by the terminal. At this time, the KeNB of the terminal and gNB are calculated based on the same UL NAS COUNT value, so they can be consistent.

[0004] Since the satellite cannot connect to the core network when providing coverage to the terminal, that is, the feedback link is disconnected, the satellite can obtain the terminal security context in advance, and the core network needs to provide the UL NASCOUNT value (this is because the terminal cannot report it), then the AMF can define the UL NAS COUNT and generate the KeNB and send it to the terminal. If the terminal generates the UL NAS COUNT value by itself at this time, it may be inconsistent with the one provided by the core network. Summary of the invention

[0005] The embodiments of the present application provide an information transmission method, apparatus, terminal and network device to solve the problem of inconsistency between the UL NAS COUNT generated by the terminal itself and that provided by the core network in the NTN scenario.

[0006] In order to solve the above technical problems, an embodiment of the present application provides an information transmission method, which is executed by a terminal, including:

[0007] An uplink count value sent by a network device is received, where the uplink count value is used by the terminal to generate a root key and / or perform uplink message encryption.

[0008] Optionally, the receiving an uplink count value sent by the network device includes any one of the following:

[0009] During the random access process, receiving an uplink count value;

[0010] After the random access process, receiving the uplink count value through a radio resource control RRC message, a non-access layer NAS message or a media access control control element MAC CE;

[0011] The uplink count value is received through the small data transmission SDT mode or the advance data transmission EDT mode.

[0012] Optionally, receiving an uplink count value during a random access process includes:

[0013] Receive Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

[0014] Optionally, the method further includes:

[0015] Sending target indication information to the network device, where the target indication information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal;

[0016] The target indication information includes: a preamble code or terminal identification information.

[0017] Optionally, before receiving the uplink count value in the small data transmission SDT mode or the advance data transmission EDT mode, the method further includes:

[0018] Sending terminal identification information to the network device, where the terminal identification information is used to indicate that the terminal supports the capability of the network side to allocate an uplink count value, or the terminal identification information is used to request the network side to allocate an uplink count value for the terminal.

[0019] Optionally, the method further includes:

[0020] Determining a root key according to the uplink count value;

[0021] According to the root key, data and / or signaling sent to the network device is encrypted, and / or data and / or signaling received from the network device is decrypted.

[0022] The embodiment of the present application also provides an information transmission method, which is executed by a network device, including:

[0023] An uplink count value is sent to the terminal, where the uplink count value is used by the terminal to generate a root key or perform uplink message encryption.

[0024] Optionally, the sending the uplink count value to the terminal includes any one of the following:

[0025] During random access, an uplink count value is sent;

[0026] After the random access process, the uplink count value is sent through a radio resource control RRC message, a non-access layer NAS message or a media access control control element MAC CE;

[0027] The uplink count value is sent through the small data transmission SDT mode or the advance data transmission EDT mode.

[0028] Optionally, sending an uplink count value during a random access process includes:

[0029] Send Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

[0030] Optionally, the method further includes:

[0031] receiving target indication information sent by a terminal, where the target indication information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal;

[0032] The target indication information includes: a preamble code or terminal identification information.

[0033] Optionally, before sending the uplink count value in a small data transmission SDT mode or an advance data transmission EDT mode, the method further includes:

[0034] The terminal identification information sent by the terminal is received, where the terminal identification information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the terminal identification information is used to request the network side to allocate an uplink count value for the terminal.

[0035] Optionally, the method further includes:

[0036] Encrypting data and / or signaling sent to the terminal according to the root key; and / or

[0037] Decrypting the received data and / or signaling sent by the terminal according to the root key;

[0038] The root key is determined by a core network device or a network device according to the uplink count value.

[0039] Optionally, the method further includes:

[0040] Sending a request message to a core network device, wherein the request message is used to request an uplink count value of the terminal;

[0041] Receive the uplink count value of the terminal fed back by the core network device.

[0042] The embodiment of the present application also provides a terminal, including a memory, a transceiver, and a processor:

[0043] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0044] An uplink count value sent by a network device is received through a transceiver, and the uplink count value is used by the terminal to generate a root key and / or perform uplink message encryption.

[0045] Optionally, the processor is configured to read the computer program in the memory and perform any one of the following operations:

[0046] During the random access process, receiving an uplink count value;

[0047] After the random access process, receiving the uplink count value through a radio resource control RRC message, a non-access layer NAS message or a media access control control element MAC CE;

[0048] The uplink count value is received through the small data transmission SDT mode or the advance data transmission EDT mode.

[0049] Optionally, the processor is configured to read the computer program in the memory and perform the following operations:

[0050] Receive Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

[0051] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0052] Sending target indication information to the network device, where the target indication information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal;

[0053] The target indication information includes: a preamble code or terminal identification information.

[0054] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0055] Sending terminal identification information to the network device, where the terminal identification information is used to indicate that the terminal supports the capability of the network side to allocate an uplink count value, or the terminal identification information is used to request the network side to allocate an uplink count value for the terminal.

[0056] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0057] Determining a root key according to the uplink count value;

[0058] According to the root key, data and / or signaling sent to the network device is encrypted, and / or data and / or signaling received from the network device is decrypted.

[0059] The embodiment of the present application also provides a network device, including a memory, a transceiver, and a processor:

[0060] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0061] An uplink count value is sent to the terminal through a transceiver, and the uplink count value is used by the terminal to generate a root key or perform uplink message encryption.

[0062] Optionally, the processor, for reading the computer program in the memory, further performs any one of the following operations:

[0063] During random access, an uplink count value is sent;

[0064] After the random access process, the uplink count value is sent through a radio resource control RRC message, a non-access layer NAS message or a media access control control element MAC CE;

[0065] The uplink count value is sent through the small data transmission SDT mode or the advance data transmission EDT mode.

[0066] Optionally, the processor is configured to read the computer program in the memory and perform the following operations:

[0067] Send Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

[0068] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0069] receiving target indication information sent by a terminal, where the target indication information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal;

[0070] The target indication information includes: a preamble code or terminal identification information.

[0071] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0072] The terminal identification information sent by the terminal is received, where the terminal identification information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the terminal identification information is used to request the network side to allocate an uplink count value for the terminal.

[0073] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0074] Encrypting data and / or signaling sent to the terminal according to the root key; and / or

[0075] Decrypting the received data and / or signaling sent by the terminal according to the root key;

[0076] The root key is determined by a core network device or a network device according to the uplink count value.

[0077] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0078] Sending a request message to a core network device, wherein the request message is used to request an uplink count value of the terminal;

[0079] Receive the uplink count value of the terminal fed back by the core network device.

[0080] The embodiment of the present application further provides an information transmission device, applied to a terminal, including:

[0081] The first receiving unit is used to receive an uplink count value sent by a network device, where the uplink count value is used by the terminal to generate a root key and / or perform uplink message encryption.

[0082] The embodiment of the present application further provides an information transmission device, which is applied to a network device, including:

[0083] The first sending unit is used to send an uplink count value to a terminal, where the uplink count value is used by the terminal to generate a root key or perform uplink message encryption.

[0084] An embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the above method.

[0085] The beneficial effects of this application are:

[0086] In the above scheme, the uplink count value used for the terminal to generate a root key and / or perform uplink message encryption is directly received from the network device, and the terminal itself does not need to generate an uplink count value, thereby avoiding the problem of inconsistency between the UL NAS COUNT generated by the terminal itself and that provided by the core network in the NTN scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0087] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0088] Figure 1 A structural diagram showing a network system applicable to an embodiment of the present application;

[0089] Figure 2 A schematic diagram showing a flow chart of an information transmission method according to an embodiment of the present application;

[0090] Figure 3 A schematic diagram showing the transmission format of a count value;

[0091] Figure 4 A second flowchart of the information transmission method according to an embodiment of the present application is shown;

[0092] Figure 5 One of the unit schematic diagrams showing the information transmission device according to an embodiment of the present application;

[0093] Figure 6 A structural diagram showing a terminal according to an embodiment of the present application;

[0094] Figure 7 A second schematic diagram of a unit showing an information transmission device according to an embodiment of the present application;

[0095] Figure 8 A structural diagram of a network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0096] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0097] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein, for example, are implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, the process, method, system, product or equipment comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0098] In the embodiments of the present application, the term "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent three situations: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0099] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0100] The relevant concepts mentioned in this application are briefly described below.

[0101] 1. Non-Terrestrial Network (NTN, i.e. satellite network)

[0102] NTN refers to using satellites as communication relays to connect terminals and base stations wirelessly. NTN can improve network coverage and provide continuous coverage for terminals in scenarios such as deserts and oceans.

[0103] A typical NTN is as follows: the service link is between the NTN satellite and the terminal, and the feeder link is between the NTN satellite and the NTN gateway. For ease of understanding, the NTN satellite and the NTN gateway are usually considered as part of the gNB.

[0104] Based on this network architecture, NTN satellites transparently forward data from base stations to terminals. Similarly, terminal data is transparently forwarded to NTN gateways and base stations via NTN satellites.

[0105] The NTN network includes the following three service links:

[0106] Earth-fixed cell: The cell covered by NTN satellites remains unchanged, such as the cell projected on the ground by Geosynchronous Earth Orbit (GEO) satellites.

[0107] Quasi-Earth-fixed cell: The satellite beam stably covers a fixed area on the surface for a period of time.

[0108] Earth-moving cell (EMC): In this scenario, the satellite's beam coverage slides on the surface of the earth.

[0109] In a quasi-earth fixed cell (EFC), the coverage of the satellite remains unchanged over a period of time. The concept of reference location is defined in EFC to assist the user equipment (UE) in determining the distance to the cell. One possible implementation method is that the reference location is the center of a circular cell. Since the coverage of the satellite remains unchanged over a period of time in EFC, the reference location will not change during this service time. In conditional handover (CHO), the terminal determines whether it is far away from the source cell and / or whether it is close to the target cell by comparing the distance with the reference location. When the conditions are met, the terminal switches to the target cell.

[0110] In EMC, the coverage area of ​​the satellite changes as the satellite moves.

[0111] 2. Store and forward (S&F) mode

[0112] In the 5G network, S&F refers to a type of communication service provided by satellite access: for services with low latency requirements, the satellite provides intermittent / temporary satellite connections within the satellite coverage area (for example, the satellite is not connected to the ground network through a feeder link or intersatellite link).

[0113] Here is an example from S&F:

[0114] In the normal / default satellite operation mode, the interaction of signaling and data requires the simultaneous activation of the service link and feeder link on the terminal and remote ground network sides. In this way, when the terminal communicates with the satellite via the service link, there will be a continuous end-to-end (from the terminal to the satellite, and the ground network) connection path.

[0115] In contrast, in the S&F satellite mode, the end-to-end signaling / data service consists of two steps. In step A, signaling and data transmission are performed between the terminal and the satellite, but the satellite is not served by the ground network side (i.e., the satellite can provide a service link, but there is no activated feeder link). In step B, the connection between the satellite and the ground network is established, so the communication between the satellite and the ground network side begins. Therefore, the satellite is connected to the terminal in step A and then connected to the ground network in step B.

[0116] The sub-satellite point can be considered as the projection of the satellite on the ground;

[0117] Reference location: It indicates the projection of the center point of the cell served by the satellite on the ground, which has a relative position relationship with the sub-satellite point.

[0118] See also Figure 1 , Figure 1 is a structural diagram of a network system to which the embodiments of the present application can be applied, such as Figure 1 As shown, it includes a user terminal 11 and a base station 12, wherein the user terminal 11 may be a user equipment (User Equipment, UE), for example: it may be a terminal side device such as a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a personal digital assistant (Personal Digital Assistant, referred to as PDA), a mobile Internet device (Mobile Internet Device, MID) or a wearable device (Wearable Device). It should be noted that the specific type of the user terminal 11 is not limited in the embodiment of the present application. The above-mentioned base station 12 may be a base station of 5G and later versions (for example: gNB, 5G NR NB), or a base station in other communication systems, or referred to as a node B. It should be noted that in the embodiment of the present application, only a 5G base station is taken as an example, but the specific type of the base station 12 is not limited.

[0119] The following is an introduction to the embodiments of the present application in conjunction with the accompanying drawings. The information transmission method, device, terminal and network device provided in the embodiments of the present application can be applied to a wireless communication system. The wireless communication system can be a system using the fifth generation (5th Generation, 5G) mobile communication technology (hereinafter referred to as a 5G system). Those skilled in the art can understand that the 5G NR system is only an example and is not a limitation.

[0120] The embodiments of the present application provide an information transmission method, apparatus, terminal and network device to solve the problem of inconsistency between the UL NAS COUNT generated by the terminal itself and that provided by the core network in the NTN scenario.

[0121] Among them, the method and the device are based on the same application concept. Since the method and the device solve the problem in a similar principle, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0122] like Figure 2 As shown, an embodiment of the present application provides an information transmission method, which is executed by a terminal and includes:

[0123] Step S201: receiving an uplink count value sent by a network device, wherein the uplink count value is used by the terminal to generate a root key and / or perform uplink message encryption.

[0124] It should be noted that in the embodiment of the present application, the network device notifies the terminal of the uplink count value, and the terminal does not need to generate the uplink count value, thereby avoiding the inconsistency caused by the terminal and the network side separately obtaining the uplink count value.

[0125] Optionally, the uplink count value mentioned in the embodiment of the present application is a UL NAS COUNT value.

[0126] It should be noted that the embodiments of the present application can be applied to a terrestrial network (TN) or an NTN. When applied to an NTN, the network device refers to an on-board network device. For example, the on-board network device may be a satellite.

[0127] Optionally, in order to be able to send the uplink count value, in one implementation, the uplink count value may be actively notified to the network device by the core network device. For example, when the uplink count value changes, the core network device sends the changed uplink count value to the network device. In another implementation, the uplink count value is sent based on the request of the network device, and the specific implementation process includes:

[0128] The network device sends a request message to the core network device, where the request message is used to request an uplink count value of the terminal; and receives the uplink count value of the terminal fed back by the core network device.

[0129] Optionally, the core network device can send an uplink count value to the network device, and the network device obtains the root key based on the uplink count value, and then encrypts the data and / or signaling sent to the terminal based on the root key, and / or decrypts the data and / or signaling received from the terminal according to the root key; of course, the core network device can also determine the root key, and then send the uplink count value and the root key to the network device. In this case, the network device does not need to determine the root key, but directly uses the root key sent by the core network device to encrypt the data and / or signaling sent to the terminal, and / or uses the root key sent by the core network device to decrypt the data and / or signaling received from the terminal.

[0130] Optionally, in one implementation, the specific implementation of receiving the uplink count value sent by the network device may adopt any one of the following:

[0131] A11. During random access, receiving an uplink count value;

[0132] It should be noted that this situation is that the terminal receives the uplink count value sent by the network device during the random access process.

[0133] Optionally, the specific implementation may be:

[0134] Receive Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

[0135] That is, the network device may transmit the uplink count value in Msg4 (corresponding to the fourth message in the four-step random access) or MsgB (corresponding to the second message in the two-step random access) of the random access message sent.

[0136] Optionally, the network device may carry the uplink count value in an RRC message of Msg4 or MsgB. Optionally, in Long Term Evolution (LTE), the RRC message carried in Msg4 or MsgB may be an RRC connection establishment (RRCConnectionSetup) message, or an RRC connection re-establishment (RRCConnectionReestalishment) message, or an RRC connection recovery (RRCConnectionResume) message; in the new air interface (New Radio, NR), the RRC message carried in Msg4 or MsgB may be an RRC establishment (RRCSetup) message, or an RRC re-establishment (RRCReestalishment) message, or an RRC recovery (RRCResume) message.

[0137] A12. After the random access process, receiving an uplink count value through a radio resource control (RRC) message, a non-access stratum (NAS) message, or a media access control control element (MAC CE);

[0138] This situation refers to that after the terminal establishes an RRC connection with the network device, the network device sends an uplink count value through an RRC message, a NAS message and / or a MAC CE.

[0139] Optionally, the RRC message may be a reconfiguration message. For example, in LTE, the reconfiguration message refers to an RRC connection reconfiguration (RRCConnectionReconfiguration) message; in NR, the reconfiguration message refers to an RRC reconfiguration (RRCReconfiguration) message.

[0140] Optionally, the NAS message may be a downlink information transfer (DLInformationTransfer) message or an RRC reconfiguration message (it should be noted that the RRC reconfiguration message here refers to a message that does not require parsing by a network device, which is an information element (IE) in the RRC message).

[0141] Optionally, in the case of A11 and A12 above, in one implementation, the method further includes:

[0142] Sending target indication information to the network device, where the target indication information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal;

[0143] The target indication information includes: a preamble code or terminal identification information.

[0144] It should be noted that, since both A11 and A12 need to perform a random access process, the terminal can send a request for an uplink count value or an indication of supporting the ability to allocate an uplink count value by the network side to the network device during the random access process, so that the network device sends the uplink count value.

[0145] Optionally, a plurality of preamble codes with different functions are provided in an embodiment of the present application. When the terminal needs to obtain an uplink count value, the corresponding preamble code can be sent so that the network device can realize feedback of the uplink count value; optionally, in an embodiment of the present application, the terminal identification information can be associated with an indication that the terminal supports the ability of the network side to allocate an uplink count value, or requests the network side to allocate an uplink count value to the terminal. When the terminal needs to obtain the uplink count value, the terminal identification information is sent to the network device so that the network device can realize feedback of the uplink count value.

[0146] Optionally, for A11, if two-step random access is adopted, the terminal usually needs to indicate through the preamble that the terminal supports the ability of the network side to allocate uplink count values, or request the network side to allocate uplink count values ​​for the terminal, and the network device feeds back the uplink count value through MsgB. If the terminal adopts four-step random access, the terminal can indicate through the preamble that the terminal supports the ability of the network side to allocate uplink count values, or request the network side to allocate uplink count values ​​for the terminal, and the network device feeds back the uplink count value through Msg4; the terminal can also indicate through the terminal identification information that the terminal supports the ability of the network side to allocate uplink count values, or request the network side to allocate uplink count values ​​for the terminal. In this case, the terminal identification information is usually carried in Msg3, and the network device feeds back the uplink count value through Msg4.

[0147] Optionally, for A12, if two-step random access is adopted, the terminal usually needs to indicate through a preamble that the terminal supports the ability of the network side to allocate an uplink count value, or request the network side to allocate an uplink count value for the terminal. After the terminal establishes an RRC connection with the network device, the network device feeds back the uplink count value through an RRC message, a NAS message and / or a MAC CE. If the terminal adopts four-step random access, the terminal can indicate through a preamble that the terminal supports the ability of the network side to allocate an uplink count value, or request the network side to allocate an uplink count value for the terminal. The terminal can also indicate through terminal identification information that the terminal supports the ability of the network side to allocate an uplink count value, or request the network side to allocate an uplink count value for the terminal. In this case, the terminal identification information is usually carried in Msg3. After the terminal establishes an RRC connection with the network device, the network device feeds back the uplink count value through an RRC message, a NAS message and / or a MAC CE.

[0148] Optionally, the ability of the terminal to support the allocation of uplink count values ​​by the network side mentioned in the embodiment of the present application can be understood as the terminal having the ability to use the uplink count values ​​allocated by the network side, that is, if the network side allocates an uplink count value to the terminal, the terminal uses the uplink count value allocated by the network side. The request for the network side to allocate an uplink count value to the terminal mentioned in the embodiment of the present application can be understood as if the terminal needs to use the uplink count value allocated by the network side, a request is sent to the terminal to request the network device to send the uplink count value. The network side mentioned here can be a network device or a core network device.

[0149] A13, receiving an uplink count value through a small data transmission (SDT) mode or an early data transmission (EDT) mode;

[0150] It should be noted that SDT and EDT refer to the information transmission process introduced when the terminal has not established an RRC connection with the network device in order to ensure that the terminal and the network device can also achieve information exchange. For details, see the definition in the relevant 3GPP protocol. The embodiment of the present application uses SDT and EDT to transmit the uplink count value.

[0151] Optionally, in one implementation, before receiving the uplink count value in a small data transmission SDT mode or an advance data transmission EDT mode, the method further includes:

[0152] Sending terminal identification information to the network device, where the terminal identification information is used to indicate that the terminal supports the capability of the network side to allocate an uplink count value, or the terminal identification information is used to request the network side to allocate an uplink count value for the terminal.

[0153] In this case, it can be understood that the uplink count value is sent based on the request or instruction of the terminal, that is, only when the terminal needs to use the uplink count value allocated by the network side, the network device needs to send the uplink count value to the terminal. Optionally, the terminal usually sends an uplink message on a preconfigured uplink resource, and the uplink message carries the terminal identification information. After receiving the uplink message, the network device sends a response message to the terminal, and the response message carries the uplink count value.

[0154] Optionally, the terminal identification information (ie, UE ID) mentioned in the embodiments of the present application, for example, the terminal identification information may be an International Mobile Subscriber Identity (IMSI).

[0155] Optionally, in one implementation, the method further includes:

[0156] The terminal determines a root key according to the uplink count value; encrypts the data and / or signaling sent to the network device according to the root key, and / or decrypts the data and / or signaling received from the network device.

[0157] Optionally, the uplink count value transmitted by the network device may be a complete uplink count value or a part of the complete uplink count value. If the terminal receives a partial uplink count value, the terminal needs to form a complete uplink count value based on another part of the uplink count value recorded by itself.

[0158] For example, optionally, the complete uplink count value can be 8 bits or 16 bits; taking the complete uplink count value of 16 bits as an example, the terminal side can maintain the upper 8 bits of the uplink count value. For example, when the received uplink count value is 8 bits and is 11111111, if the terminal still sends a UL NAS message, the received uplink count value becomes 00000000. At this time, the terminal determines that the complete uplink count value is 0000000100000000; it should be noted that only transmitting part of the bits of the uplink count value can reduce signaling overhead.

[0159] Taking the communication between a terminal and an onboard network device as an example, the specific application examples of the embodiments of the present application are illustrated as follows.

[0160] Application 1: Sending uplink count value via Msg4

[0161] Specifically, the implementation process on the onboard network device (i.e., satellite) includes:

[0162] Step 101: The onboard network device obtains the uplink count value of the terminal at time T0.

[0163] Optionally, the onboard network device may obtain the uplink count value of the terminal in the process of obtaining the context of the terminal.

[0164] Optionally, the uplink count value may be acquired by the onboard network device requesting the uplink count value of the terminal from the core network device, and the core network device sends the uplink count value of the terminal to the onboard network device according to the request of the onboard network device.

[0165] Step 102: After receiving the uplink count value from the terminal, the onboard network device saves it in the context of the terminal;

[0166] Step 103: When the onboard network device is able to provide coverage for the first geographical area where the terminal is located, the onboard network device receives a preamble sent by the terminal;

[0167] Step 104: After receiving the Preamble sent by the terminal, the onboard network device feeds back a random access response (RAR) to the terminal;

[0168] Optionally, the onboard network device may carry an uplink grant (UL grant) and an uplink advance (ULTA) in the RAR;

[0169] Step 105: The onboard network device receives Msg3 sent by the terminal at the resource location indicated by the UL grant in the RAR;

[0170] Optionally, the Msg3 carries terminal identification information, such as IMSI.

[0171] Step 106: The onboard network device sends the stored uplink count value corresponding to the terminal to the terminal via Msg4 according to the terminal identification information reported by the terminal.

[0172] Optionally, the network side receives a Preamble or terminal identification information sent by the terminal. If it is determined that the Preamble or terminal identification information is used to indicate that the terminal supports the ability of the network side to allocate an uplink count value, or is used to request the network side to allocate an uplink count value to the terminal, the onboard network device will send the corresponding uplink count value to the terminal.

[0173] Specifically, the uplink count value is sent via MAC CE, and its multiplexing relationship with Msg4 is as follows: Figure 3 As shown, Figure 3 The COUNT in it indicates the uplink count value, which is included in the media access control sub-protocol data unit (MACsubPDU).

[0174] It should be noted that in this application, the uplink count value has a fixed length of 8 bits, and of course the length of the uplink count value can also be 2 bytes or 3 bytes, which is not limited here. Furthermore, the length of the uplink count value can be variable, which is not limited here either.

[0175] Optionally, the network side sends the uplink count value in Msg4, carried in an RRC message, such as an RRCConnectionSetup message, or an RRCConnectionReestalishment message, or an RRCConnectionResume message in LTE, and an RRCSetup message, or an RRCReestalishment message, or an RRCResume message in NR.

[0176] Taking RRCConnectionSetup as an example, the IE format can be:

[0177]

[0178] Among them, RadioResourceConfigDedicated carries the uplink count value.

[0179] Specifically, the IE format of RadioResourceConfigDedicated can be:

[0180]

[0181]

[0182]

[0183]

[0184] Step 107: When the onboard network device subsequently communicates with the terminal, the onboard network device performs NAS signaling encryption and decryption operations according to the uplink count value.

[0185] Specifically, the terminal side implementation process includes:

[0186] Step 111: When the terminal determines that the onboard network device can provide coverage for the first geographical area, if the terminal has UL data to send, or receives a paging message from the network side for the terminal, the terminal sends a Preamble;

[0187] Step 112: The terminal receives the RAR sent by the onboard network device;

[0188] Optionally, the RAR carries information such as UL grant and TA;

[0189] Step 113: The terminal sends Msg3 at the resource location indicated by the UL grant carried by the RAR;

[0190] Optionally, Msg3 may carry terminal identification information, such as TMSI, etc.;

[0191] Optionally, when the terminal sends the Preamble or the terminal identification information, the Preamble or the terminal identification information may be used to indicate the capability of the terminal to support the network side to allocate the uplink count value, or the target indication information is used to request the network side to allocate the uplink count value for the terminal;

[0192] Step 114: The terminal receives Msg4 sent by the onboard network device, where Msg4 carries an uplink count value.

[0193] Step 115: When the onboard network device subsequently communicates with the terminal, the terminal performs encryption and decryption operations according to the uplink count value.

[0194] For example: after receiving the complete uplink count value or part of the complete uplink count value, the terminal updates the sending status of its NAS layer, or

[0195] The terminal updates K_RAN based on the complete uplink count value. K_RAN is the root key for security operations between the base station and the terminal, which can be K_eNB, K_gNB or other similar keys.

[0196] Application 2: Carrying uplink count value in RRC message

[0197] Specifically, the implementation process on the satellite network equipment side includes:

[0198] Step 201-step 205, same as step 101-step 105 in application case 1;

[0199] Step 206: The onboard network device sends Msg4 to the terminal according to Msg3 sent by the terminal.

[0200] Step 207: The onboard network device sends an RRC message to the terminal, where the RRC message includes an uplink count value corresponding to the terminal.

[0201] Optionally, the network side receives a Preamble or terminal identification information sent by the terminal. If it is determined that the Preamble or terminal identification information is used to indicate that the terminal supports the ability of the network side to allocate an uplink count value, or is used to request the network side to allocate an uplink count value to the terminal, the onboard network device will send the corresponding uplink count value to the terminal.

[0202] For example, in LTE, the RRC message is an RRCConnectionReconfiguration message, and in NR, the RRC message is an RRCReconfiguration message.

[0203] Specifically, taking RRCConnectionReconfiguration as an example, the IE format can be:

[0204]

[0205] Step 207: When the onboard network device subsequently communicates with the terminal, the onboard network device performs encryption and decryption operations according to the uplink count value.

[0206] Specifically, the terminal side implementation process includes:

[0207] Step 211: When the terminal determines that the onboard network device can provide coverage for the first geographical area, if the terminal has UL data to send, or receives a paging message from the network side for the terminal, the terminal sends a Preamble;

[0208] Step 212: The terminal receives the RAR sent by the onboard network device;

[0209] Optionally, the RAR carries information such as ULgrant and TA;

[0210] Step 213: The terminal sends Msg3 at the resource location indicated by the UL grant carried by the RAR;

[0211] Optionally, Msg3 may carry terminal identification information, such as TMSI, etc.;

[0212] Optionally, when the terminal sends the Preamble or the terminal identification information, the Preamble or the terminal identification information may be used to indicate the capability of the terminal to support the network side to allocate the uplink count value, or the target indication information is used to request the network side to allocate the uplink count value for the terminal;

[0213] Step 214: The terminal receives Msg4 sent by the onboard network device.

[0214] Step 215: The terminal receives an RRC message sent by the onboard network device to the terminal, where the RRC message includes an uplink count value corresponding to the terminal.

[0215] Step 216: When the onboard network device subsequently communicates with the terminal, the terminal performs encryption and decryption operations according to the uplink count value.

[0216] For example: after receiving the complete uplink count value or part of the complete uplink count value, the terminal updates the sending status of its NAS layer, or

[0217] The terminal updates K_RAN based on the complete uplink count value. K_RAN is the root key for security operations between the base station and the terminal, which can be K_eNB, K_gNB or other similar keys.

[0218] Application 3: Carrying uplink count value in NAS message or MAC CE

[0219] Specifically, the implementation process on the satellite network equipment side includes:

[0220] Step 301-step 305, same as step 101-step 105 in application case 1;

[0221] Step 306: The onboard network device sends Msg4 to the terminal according to Msg3 sent by the terminal.

[0222] Step 307: The onboard network device sends a DLInformationTransfer message or an RRCReconfiguration message, or a MAC CE to the terminal, wherein the DLInformationTransfer message or the RRCReconfiguration message or the MAC CE includes an uplink count value corresponding to the terminal.

[0223] Optionally, the network side receives a Preamble or terminal identification information sent by the terminal. If it is determined that the Preamble or terminal identification information is used to indicate that the terminal supports the ability of the network side to allocate an uplink count value, or is used to request the network side to allocate an uplink count value to the terminal, the onboard network device will send the corresponding uplink count value to the terminal.

[0224] Step 308: When the onboard network device subsequently communicates with the terminal, the onboard network device performs encryption and decryption operations according to the uplink count value.

[0225] Specifically, the terminal side implementation process includes:

[0226] Step 311: When the terminal determines that the onboard network device can provide coverage for the first geographical area, if the terminal has UL data to send, or receives a paging message from the network side for the terminal, the terminal sends a Preamble;

[0227] Step 312: The terminal receives the RAR sent by the onboard network device;

[0228] Optionally, the RAR carries information such as ULgrant and TA;

[0229] Step 313: The terminal sends Msg3 at the resource location indicated by ULgrant carried by the RAR;

[0230] Optionally, Msg3 may carry terminal identification information, such as TMSI, etc.;

[0231] Optionally, when the terminal sends the Preamble or the terminal identification information, the Preamble or the terminal identification information may be used to indicate the capability of the terminal to support the network side to allocate the uplink count value, or the target indication information is used to request the network side to allocate the uplink count value for the terminal;

[0232] Step 314: The terminal receives Msg4 sent by the onboard network device.

[0233] Step 315: The terminal receives a DLInformationTransfer or RRCReconfiguration message or MAC CE sent by the onboard network device to the terminal, where the DLInformationTransfer or RRCReconfiguration or MAC CE includes an uplink count value corresponding to the terminal.

[0234] Step 316: When the onboard network device subsequently communicates with the terminal, the terminal performs encryption and decryption operations according to the uplink count value.

[0235] For example: after receiving the complete uplink count value or part of the complete uplink count value, the terminal updates the sending status of its NAS layer, or

[0236] The terminal updates K_RAN based on the complete uplink count value. K_RAN is the root key for security operations between the base station and the terminal, which can be K_eNB, K_gNB or other similar keys.

[0237] It should be noted that the embodiment of the present application solves the problem that the terminal NAS COUNT value is inconsistent with the COUNT value maintained by the core network in the S&F scenario of the satellite, so that the terminal can use the same set of NAS COUNT values ​​as the core network to calculate KeNB / KgNB, ensuring that the terminal and the core network can encrypt and decrypt successfully.

[0238] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, etc. These various systems include terminals (also referred to as terminal equipment) and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0239] The terminal involved in the embodiment of the present application may also be referred to as a terminal device, which may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be referred to as a user equipment (UE). A wireless terminal device may communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may 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. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0240] The network device involved in the embodiment of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay terminal node (relay node), a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0241] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoded transmission or beamforming transmission, etc.

[0242] like Figure 4 As shown, an embodiment of the present application provides an information transmission method, which is executed by a network device, including:

[0243] Step S401: sending an uplink count value to a terminal, where the uplink count value is used by the terminal to generate a root key or perform uplink message encryption.

[0244] Optionally, the sending the uplink count value to the terminal includes any one of the following:

[0245] During random access, an uplink count value is sent;

[0246] After the random access process, the uplink count value is sent through a radio resource control RRC message, a non-access layer NAS message or a media access control control element MAC CE;

[0247] The uplink count value is sent through the small data transmission SDT mode or the advance data transmission EDT mode.

[0248] Optionally, sending an uplink count value during a random access process includes:

[0249] Send Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

[0250] Optionally, the method further includes:

[0251] receiving target indication information sent by a terminal, where the target indication information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal;

[0252] The target indication information includes: a preamble code or terminal identification information.

[0253] Optionally, before sending the uplink count value in a small data transmission SDT mode or an advance data transmission EDT mode, the method further includes:

[0254] The terminal identification information sent by the terminal is received, where the terminal identification information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the terminal identification information is used to request the network side to allocate an uplink count value for the terminal.

[0255] Optionally, the method further includes:

[0256] Encrypting data and / or signaling sent to the terminal according to the root key; and / or

[0257] Decrypting the received data and / or signaling sent by the terminal according to the root key;

[0258] The root key is determined by a core network device or a network device according to the uplink count value.

[0259] Optionally, the method further includes:

[0260] Sending a request message to a core network device, wherein the request message is used to request an uplink count value of the terminal;

[0261] Receive the uplink count value of the terminal fed back by the core network device.

[0262] It should be noted that all implementation methods in the above embodiments are applicable to the embodiments of the information transmission method applied to the network device side, and can achieve the same technical effect, which will not be repeated here.

[0263] like Figure 5 As shown, the embodiment of the present application provides an information transmission device 500, which is applied to a terminal, including:

[0264] The first receiving unit 501 is used to receive an uplink count value sent by a network device, where the uplink count value is used by the terminal to generate a root key and / or perform uplink message encryption.

[0265] Optionally, the first receiving unit 501 is configured to implement any one of the following:

[0266] During the random access process, receiving an uplink count value;

[0267] After the random access process, receiving the uplink count value through a radio resource control RRC message, a non-access layer NAS message or a media access control control element MAC CE;

[0268] The uplink count value is received through the small data transmission SDT mode or the advance data transmission EDT mode.

[0269] Optionally, the implementation method of receiving the uplink count value during the random access process includes:

[0270] Receive Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

[0271] Optionally, the device further comprises:

[0272] A second sending unit, configured to send target indication information to the network device, wherein the target indication information is used to indicate that the terminal supports the capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal;

[0273] The target indication information includes: a preamble code or terminal identification information.

[0274] Optionally, before the first receiving unit 501 receives the uplink count value in a small data transmission SDT mode or an advance data transmission EDT mode, the device further includes:

[0275] The third sending unit is used to send terminal identification information to the network device, where the terminal identification information is used to indicate the terminal's ability to support the network side's allocation of uplink count values, or the terminal identification information is used to request the network side to allocate uplink count values ​​for the terminal.

[0276] Optionally, the device further comprises:

[0277] A determining unit, configured to determine a root key according to the uplink count value;

[0278] The first processing unit is used to encrypt the data and / or signaling sent to the network device and / or decrypt the data and / or signaling received from the network device according to the root key.

[0279] It should be noted that the device embodiment is a device that corresponds one-to-one to the above-mentioned method embodiment. All implementation methods in the above-mentioned method embodiment are applicable to the device embodiment and can achieve the same technical effect.

[0280] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0281] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0282] like Figure 6 As shown, the embodiment of the present application further provides a terminal, including a processor 600, a transceiver 610, a memory 620, and a program stored in the memory 620 and executable on the processor 600; wherein the transceiver 610 is connected to the processor 600 and the memory 620 through a bus interface, wherein the processor 600 is used to read the program in the memory and execute the following process:

[0283] An uplink count value sent by a network device is received through a transceiver, and the uplink count value is used by the terminal to generate a root key and / or perform uplink message encryption.

[0284] The transceiver 610 is configured to receive and send data under the control of the processor 600 .

[0285] Among them, Figure 6 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 600 and various circuits of memory represented by memory 620 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 610 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, including wireless channels, wired channels, optical cables, and other transmission media. For different user devices, the user interface 630 may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0286] The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 can store data used by the processor 600 when performing operations.

[0287] Optionally, the processor 600 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array) or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

[0288] The processor calls the computer program stored in the memory to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[0289] In some embodiments, the processor is configured to read the computer program in the memory and perform any one of the following operations:

[0290] During the random access process, receiving an uplink count value;

[0291] After the random access process, receiving the uplink count value through a radio resource control RRC message, a non-access layer NAS message or a media access control control element MAC CE;

[0292] The uplink count value is received through the small data transmission SDT mode or the advance data transmission EDT mode.

[0293] In some embodiments, the processor is configured to read the computer program in the memory and perform the following operations:

[0294] Receive Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

[0295] In some embodiments, the processor, for reading the computer program in the memory, further performs the following operations:

[0296] Sending target indication information to the network device, where the target indication information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal;

[0297] The target indication information includes: a preamble code or terminal identification information.

[0298] In some embodiments, the processor, for reading the computer program in the memory, further performs the following operations:

[0299] Sending terminal identification information to the network device, where the terminal identification information is used to indicate that the terminal supports the capability of the network side to allocate an uplink count value, or the terminal identification information is used to request the network side to allocate an uplink count value for the terminal.

[0300] In some embodiments, the processor, for reading the computer program in the memory, further performs the following operations:

[0301] Determining a root key according to the uplink count value;

[0302] According to the root key, data and / or signaling sent to the network device is encrypted, and / or data and / or signaling received from the network device is decrypted.

[0303] It should be noted here that the above-mentioned terminal provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0304] The embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the information transmission method applied to a terminal. The processor-readable storage medium may be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), and semiconductor storage (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0305] like Figure 7 As shown, the embodiment of the present application provides an information transmission device 700, which is applied to a network device, including:

[0306] The first sending unit 701 is used to send an uplink count value to a terminal, where the uplink count value is used by the terminal to generate a root key or perform uplink message encryption.

[0307] Optionally, the first sending unit 701 is configured to implement any one of the following:

[0308] During random access, an uplink count value is sent;

[0309] After the random access process, the uplink count value is sent through a radio resource control RRC message, a non-access layer NAS message or a media access control control element MAC CE;

[0310] The uplink count value is sent through the small data transmission SDT mode or the advance data transmission EDT mode.

[0311] Optionally, the implementation method of sending the uplink count value during the random access process includes:

[0312] Send Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

[0313] Optionally, the device further comprises:

[0314] A second receiving unit, configured to receive target indication information sent by a terminal, where the target indication information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal;

[0315] The target indication information includes: a preamble code or terminal identification information.

[0316] Optionally, before the first sending unit 701 sends the uplink count value in a small data transmission SDT mode or an advance data transmission EDT mode, the device further includes:

[0317] The third receiving unit is used to receive terminal identification information sent by the terminal, where the terminal identification information is used to indicate the terminal's ability to support the network side's allocation of uplink count values, or the terminal identification information is used to request the network side to allocate uplink count values ​​for the terminal.

[0318] Optionally, the device further comprises:

[0319] a second processing unit, configured to encrypt data and / or signaling sent to the terminal according to the root key; and / or

[0320] Decrypting the received data and / or signaling sent by the terminal according to the root key;

[0321] The root key is determined by a core network device or a network device according to the uplink count value.

[0322] Optionally, the device further comprises:

[0323] A fourth sending unit, configured to send a request message to a core network device, wherein the request message is used to request an uplink count value of the terminal;

[0324] The fourth receiving unit is used to receive the uplink count value of the terminal fed back by the core network device.

[0325] It should be noted that the device embodiment is a device that corresponds one-to-one to the above-mentioned method embodiment. All implementation methods in the above-mentioned method embodiment are applicable to the device embodiment and can achieve the same technical effect.

[0326] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0327] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0328] like Figure 8 As shown, the embodiment of the present application further provides a network device, including a processor 800, a transceiver 810, a memory 820, and a program stored in the memory 820 and executable on the processor 800; wherein the transceiver 810 is connected to the processor 800 and the memory 820 through a bus interface, wherein the processor 800 is used to read the program in the memory and execute the following process:

[0329] An uplink count value is sent to the terminal through a transceiver, and the uplink count value is used by the terminal to generate a root key or perform uplink message encryption.

[0330] The transceiver 810 is configured to receive and send data under the control of the processor 800 .

[0331] Among them, Figure 8In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 800 and memory represented by memory 820. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 810 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, including transmission media such as wireless channels, wired channels, optical cables, and the like.

[0332] The processor 800 is responsible for managing the bus architecture and general processing, and the memory 820 can store data used by the processor 800 when performing operations.

[0333] Optionally, the processor 800 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array) or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

[0334] The processor calls the computer program stored in the memory to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[0335] In some embodiments, the processor, for reading the computer program in the memory, further performs any one of the following operations:

[0336] During random access, an uplink count value is sent;

[0337] After the random access process, the uplink count value is sent through a radio resource control RRC message, a non-access layer NAS message or a media access control control element MAC CE;

[0338] The uplink count value is sent through the small data transmission SDT mode or the advance data transmission EDT mode.

[0339] In some embodiments, the processor is configured to read the computer program in the memory and perform the following operations:

[0340] Send Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

[0341] In some embodiments, the processor, for reading the computer program in the memory, further performs the following operations:

[0342] receiving target indication information sent by a terminal, where the target indication information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal;

[0343] The target indication information includes: a preamble code or terminal identification information.

[0344] In some embodiments, the processor, for reading the computer program in the memory, further performs the following operations:

[0345] The terminal identification information sent by the terminal is received, where the terminal identification information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the terminal identification information is used to request the network side to allocate an uplink count value for the terminal.

[0346] In some embodiments, the processor, for reading the computer program in the memory, further performs the following operations:

[0347] Encrypting data and / or signaling sent to the terminal according to the root key; and / or

[0348] Decrypting the received data and / or signaling sent by the terminal according to the root key;

[0349] The root key is determined by a core network device or a network device according to the uplink count value.

[0350] In some embodiments, the processor, for reading the computer program in the memory, further performs the following operations:

[0351] Sending a request message to a core network device, wherein the request message is used to request an uplink count value of the terminal;

[0352] Receive the uplink count value of the terminal fed back by the core network device.

[0353] It should be noted here that the above-mentioned network device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

[0354] The embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the information transmission method applied to a network device. The processor-readable storage medium may be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), and semiconductor storage (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0355] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0356] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0357] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0358] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0359] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. An information transmission method, characterized in that: Executed by the terminal, including: An uplink count value sent by a network device is received, where the uplink count value is used by the terminal to generate a root key and / or perform uplink message encryption.

2. The method according to claim 1, characterized in that The receiving network device sends an uplink count value, including any one of the following: During the random access process, receiving an uplink count value; After the random access process, receiving the uplink count value through a radio resource control RRC message, a non-access layer NAS message or a media access control control element MAC CE; The uplink count value is received through the small data transmission SDT mode or the advance data transmission EDT mode.

3. The method according to claim 2, characterized in that The receiving of the uplink count value during the random access process includes: Receive Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

4. The method according to claim 2 or 3, characterized in that: Also includes: Sending target indication information to the network device, where the target indication information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal; The target indication information includes: a preamble code or terminal identification information.

5. The method according to claim 2, characterized in that: Before receiving the uplink count value by the small data transmission SDT mode or the advance data transmission EDT mode, the method further includes: Sending terminal identification information to the network device, where the terminal identification information is used to indicate that the terminal supports the capability of the network side to allocate an uplink count value, or the terminal identification information is used to request the network side to allocate an uplink count value for the terminal.

6. The method according to claim 1, characterized in that Also includes: Determining a root key according to the uplink count value; According to the root key, data and / or signaling sent to the network device is encrypted, and / or data and / or signaling received from the network device is decrypted.

7. An information transmission method, characterized in that: Performed by network devices, including: An uplink count value is sent to the terminal, where the uplink count value is used by the terminal to generate a root key or perform uplink message encryption.

8. The method according to claim 7, characterized in that The sending of the uplink count value to the terminal includes any one of the following: During random access, an uplink count value is sent; After the random access process, the uplink count value is sent through a radio resource control RRC message, a non-access layer NAS message or a media access control control element MAC CE; The uplink count value is sent through the small data transmission SDT mode or the advance data transmission EDT mode.

9. The method according to claim 8, characterized in that The sending of the uplink count value during the random access process includes: Send Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

10. The method according to claim 8 or 9, characterized in that: Also includes: receiving target indication information sent by a terminal, where the target indication information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal; The target indication information includes: a preamble code or terminal identification information.

11. The method according to claim 8, characterized in that Before sending the uplink count value by using the small data transmission SDT mode or the advance data transmission EDT mode, the method further includes: The terminal identification information sent by the terminal is received, where the terminal identification information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the terminal identification information is used to request the network side to allocate an uplink count value for the terminal.

12. The method according to claim 7, characterized in that Also includes: Encrypting data and / or signaling sent to the terminal according to the root key; and / or Decrypting the received data and / or signaling sent by the terminal according to the root key; The root key is determined by a core network device or a network device according to the uplink count value.

13. The method according to claim 7, characterized in that Also includes: Sending a request message to a core network device, wherein the request message is used to request an uplink count value of the terminal; Receive the uplink count value of the terminal fed back by the core network device.

14. A terminal, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: An uplink count value sent by a network device is received through a transceiver, and the uplink count value is used by the terminal to generate a root key and / or perform uplink message encryption.

15. The terminal according to claim 14, characterized in that: The processor is configured to read the computer program in the memory and perform any one of the following operations: During the random access process, receiving an uplink count value; After the random access process, receiving the uplink count value through a radio resource control RRC message, a non-access layer NAS message or a media access control control element MAC CE; The uplink count value is received through the small data transmission SDT mode or the advance data transmission EDT mode.

16. The terminal according to claim 15, characterized in that: The processor is configured to read the computer program in the memory and perform the following operations: Receive Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

17. The terminal according to claim 15 or 16, characterized in that: The processor is configured to read the computer program in the memory and further perform the following operations: Sending target indication information to the network device, where the target indication information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal; The target indication information includes: a preamble code or terminal identification information.

18. The terminal according to claim 15, characterized in that: The processor is configured to read the computer program in the memory and further perform the following operations: Sending terminal identification information to the network device, where the terminal identification information is used to indicate that the terminal supports the capability of the network side to allocate an uplink count value, or the terminal identification information is used to request the network side to allocate an uplink count value for the terminal.

19. The terminal according to claim 15, characterized in that: The processor is configured to read the computer program in the memory and further perform the following operations: Determining a root key according to the uplink count value; According to the root key, data and / or signaling sent to the network device is encrypted, and / or data and / or signaling received from the network device is decrypted.

20. A network device, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: An uplink count value is sent to the terminal through a transceiver, and the uplink count value is used by the terminal to generate a root key or perform uplink message encryption.

21. The network device according to claim 20, characterized in that: The processor is configured to read the computer program in the memory and further perform any one of the following operations: During random access, an uplink count value is sent; After the random access process, the uplink count value is sent through a radio resource control RRC message, a non-access layer NAS message or a media access control control element MAC CE; The uplink count value is sent through the small data transmission SDT mode or the advance data transmission EDT mode.

22. The network device according to claim 21, characterized in that: The processor is configured to read the computer program in the memory and perform the following operations: Send Msg4 or MsgB, where the Msg4 or MsgB carries the uplink count value.

23. The network device according to claim 21 or 22, characterized in that: The processor is configured to read the computer program in the memory and further perform the following operations: receiving target indication information sent by a terminal, where the target indication information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the target indication information is used to request the network side to allocate an uplink count value for the terminal; The target indication information includes: a preamble code or terminal identification information.

24. The network device according to claim 21, characterized in that: The processor is configured to read the computer program in the memory and further perform the following operations: The terminal identification information sent by the terminal is received, where the terminal identification information is used to indicate that the terminal supports a capability of the network side to allocate an uplink count value, or the terminal identification information is used to request the network side to allocate an uplink count value for the terminal.

25. The network device according to claim 20, characterized in that: The processor is configured to read the computer program in the memory and further perform the following operations: Encrypting data and / or signaling sent to the terminal according to the root key; and / or Decrypting the received data and / or signaling sent by the terminal according to the root key; The root key is determined by a core network device or a network device according to the uplink count value.

26. The network device according to claim 20, characterized in that: The processor is configured to read the computer program in the memory and further perform the following operations: Sending a request message to a core network device, wherein the request message is used to request an uplink count value of the terminal; Receive the uplink count value of the terminal fed back by the core network device.

27. An information transmission device, applied to a terminal, characterized in that: include: The first receiving unit is used to receive an uplink count value sent by a network device, where the uplink count value is used by the terminal to generate a root key and / or perform uplink message encryption.

28. An information transmission device, applied to a network device, characterized in that: include: The first sending unit is used to send an uplink count value to a terminal, where the uplink count value is used by the terminal to generate a root key or perform uplink message encryption.

29. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the method according to any one of claims 1 to 13.

Images