WO2020047724A1 - Procédé et dispositif de transmission de données - Google Patents

Procédé et dispositif de transmission de données Download PDF

Info

Publication number
WO2020047724A1
WO2020047724A1 PCT/CN2018/103853 CN2018103853W WO2020047724A1 WO 2020047724 A1 WO2020047724 A1 WO 2020047724A1 CN 2018103853 W CN2018103853 W CN 2018103853W WO 2020047724 A1 WO2020047724 A1 WO 2020047724A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
authentication code
message
base station
message authentication
Prior art date
Application number
PCT/CN2018/103853
Other languages
English (en)
Chinese (zh)
Inventor
于映辉
胡力
王燕
王宏
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2018/103853 priority Critical patent/WO2020047724A1/fr
Publication of WO2020047724A1 publication Critical patent/WO2020047724A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA

Definitions

  • Embodiments of the present invention relate to the field of communications technologies, and in particular, to a data transmission method and device.
  • EDT early data transmission
  • uplink data that is, early uplink data transmission is performed
  • downlink data that is, early downlink data transmission
  • downlink data In the process of early transmission of uplink data or early transmission of uplink data), downlink data must be delivered after the network side completes authentication to the UE.
  • the present application provides a data transmission method and device, which can improve the security of early data transmission.
  • the present application provides a data transmission method, which includes: sending a random access preamble sequence to a base station; and receiving a random access response from the base station; and protecting a key based on freshness parameters and non-access layer integrity Using a non-access layer integrity protection algorithm to generate a first message authentication code; and sending a message 3 to the base station, the message 3 carrying a first uplink message authentication code, where the first uplink message authentication code is the first message authentication code Or receiving part 4 of the message; and receiving message 4 from the base station, the message 4 including downlink data.
  • the method for generating the first message authentication code by using the non-access layer integrity protection algorithm according to the freshness parameter and the non-access layer integrity protection key may be The method includes: generating a first message authentication code by using a non-access layer integrity protection algorithm according to the terminal's serving cell identity, freshness parameters, and non-access layer integrity protection keys.
  • the data transmission method provided in the embodiment of the present invention may further include: acquiring downlink data early transmission indication information, where the downlink data early transmission indication information is used to instruct the terminal to send a message in message 4 Receiving downlink data.
  • the terminal after the terminal obtains the downlink data early transmission indication information, the terminal can learn that the downlink data needs to be received in the random access process.
  • the foregoing method for acquiring early data transmission indication information of the downlink includes: receiving a paging message, where the paging message carries the early data transmission indication information of the downlink.
  • the terminal may also obtain the downlink data indication information based on the high-level indication information of the terminal.
  • the method for sending a random access preamble sequence to a base station includes: Sending a random access preamble sequence to the base station on the physical random access channel resource; when the freshness parameter includes an access layer parameter or an uplink non-access layer parameter, the sending of the random access preamble sequence to the base station includes: The random access preamble sequence is sent to the base station on the physical random access channel resource of the early transmission.
  • the above message 4 further includes a first downlink message authentication code
  • the data transmission method provided by the embodiment of the present invention may further include: the first downlink message authentication code and When the first message authentication code matches, downlink data is obtained.
  • the terminal determines that the first downlink message authentication code matches the first message authentication code, the terminal determines that the mobile management function entity is a legal device, and receives the downlink data issued by the mobile management function entity.
  • the foregoing message 4 further includes a third downlink message authentication code and downlink non-access layer parameter indication information, and the downlink non-access layer parameter indication information is used to indicate the downlink Non-access parameters.
  • the data transmission method provided by the embodiment of the present invention may further include: generating non-access layer integrity protection algorithms according to downlink data, downlink non-access layer parameters, and non-access layer integrity protection keys, and Four-message authentication code; and when the third downlink message authentication code matches the fourth message authentication code, downlink data is obtained.
  • the present application provides a data transmission method, the method comprising: receiving a random access preamble sequence from a terminal; and sending a random access response to the terminal; and receiving a message 3 from the terminal, the message 3 including freshness Parameters and the first uplink message authentication code; and send the freshness parameter and the first uplink message authentication code to the mobility management function entity; then receive the downlink data from the mobility management function entity; and then send a message 4 to the terminal, the message 4 includes Downstream data.
  • the message 3 sent by the terminal to the base station does not need to carry the physical layer parameters or the broadcast packet parameters.
  • the base station After receiving the message 3, the base station itself The physical layer parameters or broadcast packet parameters of the terminal can be determined. In this way, the terminal can save resources for sending message 3.
  • the present application provides a data transmission method, which includes: receiving a random access preamble sequence from a terminal; and sending a random access response to the terminal; and receiving a message 3 from the terminal, the message 3 including access Layer parameter indication information and a first uplink message authentication code, the access layer parameter indication information is used to indicate an access layer parameter; and sends the access layer parameter and the first uplink message authentication code to the mobility management function entity; and then from the mobility management
  • the functional entity receives the downlink data; and then sends a message 4 to the terminal, where the message 4 includes the downlink data.
  • the terminal carries indication information of access layer parameters in message 3.
  • the base station may determine the access layer parameters according to the obtained access layer parameter indication. Because the message 3 carries the access layer parameter indication information and does not directly carry the access layer parameters, so the resource of sending the message 3 by the terminal can be saved to a certain extent.
  • the present application provides a data transmission method, which includes: receiving a random access preamble sequence from a terminal; and sending a random access response to the terminal; and receiving a message 3 from the terminal, the message 3 including an uplink non- The access layer parameter indication information and the first uplink message authentication code, the uplink non-access layer parameter indication information is used to indicate the uplink non-access layer parameter; and the uplink non-access layer parameter indication information and the first An uplink message authentication code; then receiving downlink data from the mobility management function entity; and sending a message 4 to the terminal, the message 4 including the downlink data.
  • the data transmission method provided in the present application may further include: receiving a first downlink message authentication code and downlink non-access layer parameter indication information from a mobility management function entity; and Send the first downlink message authentication code and downlink non-access layer parameter indication information to the terminal.
  • the data transmission method provided in the present application may further include: sending the serving cell identity of the terminal to the mobility management function entity.
  • the data transmission method provided in the present application may further include: receiving downlink data early transmission indication information from the mobile management function entity; and sending the downlink data early transmission indication information to the terminal.
  • the data transmission method provided in the present application may further include: receiving a first downlink message authentication code from a mobility management function entity; and sending the first downlink message authentication code to the terminal.
  • the present application provides a data transmission method.
  • the method includes: receiving a freshness parameter and a first uplink message authentication code from a base station; and adopting a non-access layer integrity protection key according to the freshness parameter and a non-access layer integrity protection key.
  • the access layer integrity protection algorithm generates a second message authentication code; when the first uplink message authentication code matches the second message authentication code, it sends downlink data to the base station.
  • the data transmission method provided in the present application may further include: receiving a terminal's serving cell identity from a base station; and the above-mentioned protection key based on the freshness parameter and the integrity of the non-access layer
  • Using a non-access layer integrity protection algorithm to generate a second message authentication code may include: using a non-access layer integrity protection key according to the terminal's serving cell identity, freshness parameters, and non-access layer integrity protection keys. The protection algorithm generates a second message authentication code.
  • the data transmission method provided in the present application may further include: sending downlink data early transmission indication information to a base station.
  • the data transmission method provided in the present application may further include: sending a first downlink message authentication code to the base station, where the first downlink message authentication code is a second message authentication Part or all of the code.
  • the present application provides a data transmission method.
  • the method includes: receiving uplink non-access layer parameter indication information, a non-access layer integrity protection key, and a first uplink message authentication code from a base station;
  • the access layer parameter indication information determines the number of uplink non-access layers, and the uplink non-access layer parameters include the value of the uplink non-access stratum timer (non-access stratum count, NAS COUNT); and according to the uplink non-access stratum
  • the parameters and the non-access layer integrity protection key use the non-access layer integrity protection algorithm to generate a second message authentication code; when the first uplink message authentication code matches the second message authentication code, the downlink data is sent to the base station.
  • a terminal sends a random access preamble sequence to a base station, and receives a random access response from the base station, and then the terminal adopts the non-access layer integrity based on the freshness parameter and the non-access layer integrity protection key.
  • Sexual protection algorithm generating a first message authentication code, and carrying the first uplink message authentication code (the first uplink message authentication code is part or all of the first message authentication code) in message 3 and sending it to the base station, so that The base station sends the first uplink message authentication code to the mobile management function entity.
  • the mobile management function entity also uses the non-access layer integrity protection algorithm to generate the second message authentication according to the freshness parameter and the non-access layer integrity protection key.
  • the mobile management function entity in the case that it is determined that the first uplink message authentication code matches the second message authentication code, the mobile management function entity sends downlink data to the base station, so that the base station sends the downlink data to the terminal in message 4 and sends it to the terminal. Security of early data transmission.
  • the data transmission method provided in the present application may further include: receiving a serving cell identity of the terminal from the base station; and the foregoing according to the uplink non-access layer parameters and the non-access layer integrity
  • the protection key adopts a non-access layer integrity protection algorithm
  • the generation of the second message authentication code may include: according to the terminal's serving cell identity, the uplink non-access layer parameters, and the non-access layer integrity protection key, the non-access layer is used.
  • a layer integrity protection algorithm generates a second message authentication code.
  • the data transmission method provided in this application may further include: adopting a non-access method according to downlink data, downlink non-access layer parameters, and non-access layer integrity protection keys.
  • the in-layer integrity protection algorithm generates a third message authentication code; and sends a third downlink message authentication code and downlink non-access layer parameter indication information to the base station, where the third downlink message authentication code is part of the third message authentication code or All.
  • the present application provides a terminal, which includes a sending module, a receiving module, and a generating module.
  • the sending module is used to send a random access preamble sequence to the base station;
  • the receiving module is used to receive a random access response from the base station;
  • the generating module is used to protect the key based on the freshness parameter and the non-access layer integrity, and adopt non-access Layer integrity protection algorithm to generate a first message authentication code;
  • the sending module is further configured to send a message 3 to the base station, where the message 3 carries a first uplink message authentication code, where the first uplink message authentication code is the first message authentication code Part or all;
  • the receiving module is further configured to receive message 4 from the base station, and the message 4 includes downlink data.
  • the foregoing generating module is specifically configured to adopt non-access layer integrity protection according to a terminal's serving cell identity, freshness parameters, and non-access layer integrity protection key. Algorithm to generate a first message authentication code.
  • the terminal provided in this application further includes an acquiring module, which is configured to acquire early downlink data transmission instruction information, and the early downlink data transmission instruction information is used to instruct the terminal to The downlink data is received in message 4.
  • the foregoing receiving module is further configured to receive a paging message, where the paging message carries downlink data early transmission indication information.
  • the sending module when the freshness parameter includes a physical layer parameter or a broadcast packet parameter, the sending module is specifically configured to be used on a physical random access channel resource for non-data early transmission. Sending a random access preamble sequence to the base station; when the freshness parameter includes an access layer parameter or an uplink non-access layer parameter, the sending module is specifically configured to send the physical random access channel resource for early data transmission to the base station. Random access preamble sequence.
  • the message 4 further includes a first downlink message authentication code
  • the obtaining module is further configured to match the first downlink message authentication code with the first message authentication code. In the case, acquire downlink data.
  • the above message 4 further includes a third downlink message authentication code and downlink non-access layer parameter indication information, and the downlink non-access layer parameter indication information is used to indicate the downlink
  • the foregoing generating module is further configured to generate a fourth message authentication code by using a non-access layer integrity protection algorithm according to downlink data, downlink non-access layer parameters, and non-access layer integrity protection keys; The module is also used to obtain downlink data when the third downlink message authentication code matches the fourth message authentication code.
  • the freshness parameter includes any of the following: a physical layer parameter, a broadcast packet parameter, an access layer parameter, and an uplink non-access layer parameter; wherein the physical layer parameter includes at least the following One: terminal identification, frame number for sending random access preamble sequence; broadcast packet parameters include at least one of the following: system frame number, system information value label, time information; access layer parameters include packet data convergence layer protocol counters (packet, data, convergence, PDCP, COUNT); the uplink non-access stratum parameters include the value of the uplink NAS, COUNT.
  • the physical layer parameter includes at least the following One: terminal identification, frame number for sending random access preamble sequence
  • broadcast packet parameters include at least one of the following: system frame number, system information value label, time information
  • access layer parameters include packet data convergence layer protocol counters (packet, data, convergence, PDCP, COUNT)
  • the uplink non-access stratum parameters include the value of the uplink NAS, COUNT.
  • the foregoing message 3 when the freshness parameter includes an access layer parameter, the foregoing message 3 further includes indication information of the access layer parameter, and the indication information of the access layer parameter is used to indicate the access layer parameter Or when the freshness parameter includes an uplink non-access layer parameter, the message 3 further includes indication information of the uplink non-access layer parameter.
  • the present application provides a base station, which includes a receiving module and a sending module.
  • the receiving module is used to receive a random access preamble sequence from the terminal; the sending module is used to send a random access response to the terminal; the receiving module is also used to receive a message 3 from the terminal, and the message 3 includes the freshness parameter and the first Uplink message authentication code; the sending module is further configured to send the freshness parameter and the first uplink message authentication code to the mobility management function entity; the receiving module is further configured to receive downlink data from the mobility management function entity; the sending module is further configured to send The terminal sends a message 4 which includes downlink data.
  • the freshness parameter includes any one of the following: a physical layer parameter and a broadcast packet parameter, wherein the physical layer parameter includes at least one of the following: an identity of the terminal, and a random access preamble sent Sequence frame number; broadcast packet parameters include at least one of the following: system frame number, system information value label, and time information.
  • the present application provides a base station, which includes a receiving module and a sending module.
  • the receiving module is used to receive a random access preamble sequence from the terminal; the sending module is used to send a random access response to the terminal; the receiving module is also used to receive a message 3 from the terminal, and the message 3 includes access layer parameter indication information And the first uplink message authentication code, the access layer parameter indication information is used to indicate the access layer parameters; the sending module is further configured to send the access layer parameters and the first uplink message authentication code to the mobility management function entity; the receiving module also The sending module is configured to receive downlink data from a mobility management function entity. The sending module is further configured to send a message 4 to the terminal, where the message 4 includes downlink data.
  • the above-mentioned access layer parameters may include a value of PDCP COUNT.
  • the present application provides a base station, which includes a receiving module and a sending module.
  • the receiving module is used to receive a random access preamble sequence from the terminal; the receiving module is used to send a random access response to the terminal; the receiving module is also used to receive a message 3 from the terminal, which includes uplink non-access layer parameters Indication information and a first uplink message authentication code, the uplink non-access layer parameter indication information is used to indicate an uplink non-access layer parameter;
  • the sending module is further configured to send the uplink non-access layer parameter indication information and the first An uplink message authentication code;
  • the receiving module is further configured to receive downlink data from the mobile management function entity; the sending module is further configured to send a message 4 to the terminal, and the message 4 includes downlink data.
  • the receiving module is further configured to receive a first downlink message authentication code and downlink non-access layer parameter indication information from a mobility management function entity; the sending module is further configured to: Send the first downlink message authentication code and downlink non-access layer parameter indication information to the terminal.
  • the above-mentioned uplink non-access stratum parameters include values of uplink NAS COUNT.
  • the foregoing sending module is further configured to send the serving cell identity of the terminal to the mobility management function entity.
  • the receiving module is further configured to receive the downlink data early transmission indication information from the mobility management function entity; and the sending module is further configured to send the downlink data early transmission indication information to the terminal.
  • the receiving module is further configured to receive the first downlink message authentication code from the mobility management function entity; and the sending module is further configured to send the first downlink message authentication code to the terminal.
  • the present application provides a mobility management function entity, including a receiving module, a generating module, and a sending module.
  • the receiving module is configured to receive the freshness parameter and the first uplink message authentication code from the base station;
  • the generating module is configured to use the non-access layer integrity protection algorithm according to the freshness parameter and the non-access layer integrity protection key, Generate a second message authentication code;
  • the sending module is configured to send downlink data to the base station if the first uplink message authentication code matches the second message authentication code.
  • the receiving module is further configured to receive a serving cell identifier of the terminal from the base station; and the generating module is specifically configured to receive the serving cell identifier of the terminal, the freshness parameter, and the non-connected terminal.
  • the in-layer integrity protection key uses a non-access layer integrity protection algorithm to generate a second message authentication code.
  • the foregoing sending module is further configured to send early downlink data transmission indication information to a base station.
  • the sending module is further configured to send a first downlink message authentication code to the base station, where the first downlink message authentication code is part of the second message authentication code or All.
  • the freshness parameter includes any one of the following: a physical layer parameter, a broadcast packet parameter, and an access layer parameter, wherein the physical layer parameter includes at least one of the following: an identifier of a terminal Send the frame number of the random access preamble sequence; the broadcast packet parameters include at least one of the following: the system frame number, the system information value label, and the absolute time; the access layer parameters include the value of PDCP and COUNT.
  • the present application provides a mobility management function entity, including a receiving module, a determining module, a generating module, and a sending module.
  • the receiving module is configured to receive the uplink non-access layer parameter indication information, the non-access layer integrity protection key, and the first uplink message authentication code from the base station;
  • the determination module is configured to determine the uplink non-access layer parameter indication information Number of uplink non-access layers.
  • the parameters of the uplink non-access layer include the value of the uplink NAS COUNT.
  • the generating module is used to protect the integrity of the non-access layer parameters based on the parameters of the uplink non-access layer and the non-access layer integrity.
  • the protection algorithm generates a second message authentication code; the sending module is configured to send downlink data to the base station if the first uplink message authentication code matches the second message authentication code.
  • the receiving module is further configured to receive a terminal's serving cell identity from a base station; and the generating module is specifically configured to use the terminal's serving cell identity and uplink non-access layer parameters And the non-access layer integrity protection key, the non-access layer integrity protection algorithm is used to generate a second message authentication code.
  • the foregoing generating module is further configured to use non-access layer integrity according to downlink data, downlink non-access layer parameters, and non-access layer integrity protection keys.
  • the protection algorithm generates a third message authentication code; the sending module is further configured to send a third downlink message authentication code and downlink non-access layer parameter indication information to the base station, where the third downlink message authentication code is part of the third message authentication code Or all.
  • the present application provides a terminal.
  • the terminal may include a processor and a memory coupled to the processor. This memory can be used to store computer instructions.
  • the processor executes the computer instructions stored in the memory, so that the terminal executes the data transmission method in the first aspect or any one of its optional implementation manners.
  • a computer-readable storage medium may include computer instructions.
  • the terminal is caused to execute the data transmission method in the first aspect or any one of its optional implementation manners.
  • a computer program product including computer instructions is provided, and when the computer program product runs on a computer, the data transmission method in the first aspect or any one of the possible implementation manners is performed.
  • the present application provides a base station, which may include a processor and a memory coupled to the processor.
  • This memory can be used to store computer instructions.
  • the processor executes the computer instructions stored in the memory, so that the base station executes the data transmission method in the second aspect, the third aspect, and the fourth aspect described above.
  • a computer-readable storage medium may include computer instructions.
  • the base station is caused to execute the data transmission method in the second aspect, the third aspect, and the fourth aspect described above.
  • a computer program product including computer instructions is provided, and when the computer program product runs on a computer, the data transmission method in the second aspect, the third aspect, and the fourth aspect is performed.
  • the present application provides a mobility management function entity.
  • the mobility management function entity may include a processor and a memory coupled to the processor. This memory can be used to store computer instructions.
  • the processor executes the computer instructions stored in the memory, so that the mobility management function entity executes the data transmission method of the fifth aspect and the sixth aspect.
  • a computer-readable storage medium may include computer instructions.
  • the mobile management function entity is caused to execute the data transmission method in the fifth aspect and the sixth aspect.
  • a computer program product including computer instructions, which when executed on a computer, causes the data transmission method in the fifth and sixth aspects described above to be performed.
  • FIG. 1 is a schematic diagram of a random access process according to an embodiment of the present invention
  • FIG. 2 is a first schematic diagram of a data transmission method according to an embodiment of the present invention
  • FIG. 3 is a second schematic diagram of a data transmission method according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of an Internet of Things communication system according to an embodiment of the present invention.
  • FIG. 5 is a hardware schematic diagram of a base station according to an embodiment of the present invention.
  • FIG. 6 is a hardware schematic diagram of a server integrated with an MME according to an embodiment of the present invention.
  • FIG. 7 is a third schematic diagram of a data transmission method according to an embodiment of the present invention.
  • FIG. 8 is a fourth schematic diagram of a data transmission method according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a method for authenticating a mobile management function entity by a terminal according to an embodiment of the present invention.
  • FIG. 10 is a fifth schematic diagram of a data transmission method according to an embodiment of the present invention.
  • FIG. 11 is a sixth schematic diagram of a data transmission method according to an embodiment of the present invention.
  • FIG. 12 is a seventh schematic diagram of a data transmission method according to an embodiment of the present invention.
  • FIG. 13 is a first schematic structural diagram of a terminal according to an embodiment of the present invention.
  • FIG. 14 is a second schematic structural diagram of a terminal according to an embodiment of the present invention.
  • FIG. 15 is a first schematic structural diagram of a base station according to an embodiment of the present invention.
  • 16 is a second schematic structural diagram of a base station according to an embodiment of the present invention.
  • FIG. 17 is a first schematic structural diagram of a mobility management function entity according to an embodiment of the present invention.
  • FIG. 18 is a second schematic structural diagram of a mobility management function entity according to an embodiment of the present invention.
  • first and second in the description and claims of the embodiments of the present invention are used to distinguish different objects, rather than to describe a specific order of the objects.
  • first message authentication code, the second message authentication code, and the like are used to distinguish different message authentication codes, and are not used to describe a specific order of the message authentication codes.
  • words such as “exemplary” or “for example” are used as examples, illustrations or illustrations. Any embodiment or design described as “exemplary” or “for example” in the embodiments of the present invention should not be construed as more preferred or more advantageous than other embodiments or designs. Rather, the use of the words “exemplary” or “for example” is intended to present the relevant concept in a concrete manner.
  • a plurality means two or more.
  • multiple processing units refer to two or more processing units; multiple systems refer to two or more systems.
  • Random access process It is the first step to establish a connection before the terminal communicates with the network.
  • the random access process is mainly to achieve uplink synchronization or allocate resources for data transmission.
  • the random access process of the terminal includes a contention-based random access process and a non-contention-based random access process.
  • the following uses the contention-based random access process as an example to briefly introduce the terminal's random access process, as shown in Figure 1.
  • the random access process of the terminal includes the transmission of message 1 (ie, message 1) to message 4 (message 4).
  • message 1 ie, message 1
  • message 4 messages 4
  • the random access process of the terminal includes S101-S104:
  • the terminal sends a message 1 to the base station, where the message 1 includes a random access preamble sequence.
  • the above message 1 may be a random access request.
  • the terminal Before sending a random access request, the terminal receives a system message broadcast by the base station.
  • the system message includes a resource for the terminal to send a random preamble sequence, so that the terminal uses the resource to pass the physical random An access channel (physical random access channel, PRACH) sends a random access preamble sequence to a base station, where a resource used by a terminal to send a random preamble sequence may also be referred to as a PRACH resource.
  • PRACH physical random access channel
  • the base station sends a message 2 to the terminal.
  • the above message 2 may be a random access response.
  • the base station may send a random access response to the terminal through a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH).
  • the random access may also include a random preamble sequence identifier, a time alignment indication, an initial uplink resource grant (UL grant), and a cell wireless network identification (C-RNTI) detected by the base station, where the time alignment indication It is used for the terminal to establish uplink synchronization.
  • the initial UL grant is used for sending message 3.
  • the C-RNTI of the terminal is used to identify the RRC connection of the terminal.
  • the terminal sends a message 3 to the base station.
  • the message 3 may be a connection request message, and the message 3 transmits a media access (MAC) layer message or a radio resource control (RRC) message, such as an RRC connection request, a scheduling request message, and the like.
  • MAC media access
  • RRC radio resource control
  • the terminal may send a message 3 through a physical uplink control channel (physical uplink shared channel, PUSCH).
  • the message 3 may also include the NAS layer identifier of the terminal (for example, S-TMSI).
  • S-TMSI is used for conflict resolution of terminal access. .
  • the base station sends a message 4 to the terminal.
  • the message 4 is a contention resolution message and an RRC connection configuration message.
  • the contention resolution message includes the identity of a successful terminal (ie, S-TMSI).
  • the terminal received the message 4 and the identifier carried in the message 4 is The identity of the terminal matches, indicating that the competition is successfully resolved.
  • the identity carried in message 4 does not match the identity of the terminal (the identity is the identity of other terminals), indicating that a contention conflict has occurred, and the terminal ’s random access process has failed. Restart a new random access procedure.
  • the terminal receives the RRC connection configuration message sent in message 4 and establishes an RRC connection.
  • the terminal can start transmitting uplink data through message 5, and then the base station transmits downlink data after message 5 (for details, refer to the flowchart of S101-S106 in FIG. 2). It should be noted that before transmitting the uplink data in the message 5, the terminal needs to obtain the resource that the base station instructs or allocates for sending uplink data (that is, resource scheduling is performed on the message 5). Therefore, the terminal can send in the message 3
  • the MAC CE including the data amount indication is used to indicate how large the uplink data sent by the terminal is from the base station, so the base station allocates resources for sending the uplink data to the terminal through message 4.
  • the base station interacts with the core network equipment (such as mobility management entity (MME)) to complete the authentication of the terminal, the core network equipment sends the downlink data to the base station, and the base station forwards the downlink to the terminal. data.
  • MME mobility management entity
  • the terminal sends authentication information (message authentication code for terminal authentication, terminal identification, authentication related parameters (such as AS parameters or NAS parameters, etc.) to the base station through message 5).
  • the random access process of the terminal the transmission process of uplink data and / or downlink data, and the authentication process of the terminal are all existing processes, which are not described in detail in this embodiment of the present invention.
  • EDT Early Data Transmission
  • the uplink data is sent in message 3, so that the base station sends the downlink data through message 4 (for details, see the flowchart of S201-S204 in Figure 3).
  • the early data transmission technology is usually applied to scenarios with small data transmission characteristics (such as the Internet of Things (such as narrowband In the field of the Internet of Things (NB-IoT) and machine type communication (MTC network), the delay and power consumption of data transmission can be reduced.
  • early data transmission includes early transmission of uplink data and early transmission of downlink data.
  • scenario 1 refers to: the terminal has an upstream data transmission requirement, and the terminal After sending the uplink data, the base station responds to the downlink data accordingly, that is, the early data transmission includes the early data transmission of the uplink data and the early data transmission of the downlink data. That is, there is downlink data on the network side that needs to be sent to the terminal.
  • a terminal sends a random access preamble sequence to a base station, and receives a random access response from the base station. Then, the terminal according to the freshness parameter and the non-access layer
  • the integrity protection key uses a non-access layer integrity protection algorithm to generate a first message authentication code, and will be based on the first uplink message authentication code (the first uplink message authentication code is part of the first message authentication code or All) is carried in message 3 and sent to the base station, so that the base station sends the first uplink message authentication code to the mobile management function entity.
  • the mobile management function entity also uses the non-access according to the freshness parameter and the access layer integrity protection key.
  • the layer integrity protection algorithm generates a second message authentication code.
  • the mobile management function entity sends downlink data to the base station, so that the base station carries the downlink data in The message 4 is sent to the terminal. In this way, the security of early data transmission can be improved.
  • the data transmission method provided in the embodiment of the present invention only involves the above scenario 2, that is, it is applied to a scenario where there is only a requirement for early transmission of downlink data.
  • the data transmission method and device provided by the embodiments of the present invention can be applied to an Internet of Things communication system, such as an Internet of Things communication system in a Long Term Evolution (LTE) (ie, 4G) network, which uses a fifth-generation mobile communication technology.
  • the network may be referred to as an Internet of Things communication system in a 5G network.
  • FIG. 4 it is a schematic architecture diagram of an Internet of Things communication system according to an embodiment of the present invention.
  • the Internet of Things communication system includes at least one terminal (in the example of FIG. 4, three terminals are an electric meter 10 a, a refrigerator 10 b, and The washing machine 10c), the base station 11 and the mobility management function entity 12.
  • the terminal (such as the meter 10a), the base station (such as the base station 11), and the core network equipment (such as the mobile management function entity 12) interact with each other to complete the terminal's random access process and terminal authentication, so that uplink data transmission and Transmission of downstream data.
  • the base station such as the base station 11
  • the core network equipment such as the mobile management function entity 12
  • the base station 11 may be an evolved base station (eNB), and the mobile management function entity 12 may be an MME; in a 5G network, the base station 11 may be The next generation base station (next generation node, base station, gNB), etc., the mobility management function entity 12 may be an access and mobility management function (AMF) entity.
  • eNB evolved base station
  • MME mobile management function entity
  • the base stations provided by the embodiments of the present invention are generally used base stations, evolved base stations (eNBs), next generation base stations (gNB) in new 5G systems, new radio base stations (new radio base stations), Macro base station, micro base station, high frequency base station, or transmission and reception point (TRP).
  • eNBs evolved base stations
  • gNB next generation base stations
  • new radio base stations new radio base stations
  • Macro base station micro base station
  • micro base station high frequency base station
  • TRP transmission and reception point
  • the embodiment of the present invention uses a base station generally used as an example to introduce the hardware structure of the base station.
  • Each component of the base station provided by the embodiment of the present invention is described in detail below with reference to FIG. 5.
  • the base station provided by the embodiment of the present invention may include: 20 parts and 21 parts. Part 20 is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals to baseband signals.
  • Part 21 is mainly used for baseband processing and controlling base stations.
  • the 20 parts can usually be called a transceiver unit, a transceiver, a transceiver circuit, or a transceiver.
  • Part 21 is usually the control center of the base station, which can usually be called the processing unit.
  • the 20-unit transceiver unit may also be called a transceiver, or a transceiver, etc., which includes an antenna and a radio frequency unit, or only includes a radio frequency unit or a part thereof, in which the radio frequency unit is mainly used for radio frequency processing.
  • the device used to implement the receiving function in section 20 can be regarded as a receiving unit and the device used to implement the transmitting function can be regarded as a transmitting unit, that is, section 20 includes a receiving unit and a transmitting unit.
  • the receiving unit may also be called a receiver, a receiver, or a receiving circuit
  • the sending unit may be called a transmitter, a transmitter, or a transmitting circuit.
  • Section 21 may include one or more single boards or chips. Each single board or chip may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement the baseband processing function. And control of the base station. If there are multiple boards, the boards can be interconnected to increase processing capacity. As an optional implementation manner, multiple single boards may share one or more processors, or multiple single boards may share one or more memories. Among them, the memory and the processor may be integrated together or may be independently set. In some embodiments, sections 20 and 21 may be integrated or independently provided. In addition, all functions in part 21 can be implemented in one chip, or part of the functions can be integrated in one chip, and other functions can be implemented in one or more chips, which is not limited in the embodiment of the present invention.
  • the terminal provided by the embodiment of the present invention is a user equipment in the Internet of Things (IoT), and may be, for example, an electric meter, a washing machine, a refrigerator, a rice cooker, a television, a stereo, and a watch.
  • IoT Internet of Things
  • the MME may be integrated on a server to implement the function of the MME.
  • the server 30 may include a processor 31, a memory 32, a communication interface 33, and the like.
  • the processor 31 is a core component of the server 30 and is used to run the operating system of the server 30 and applications (including system applications and third-party applications) on the server 30.
  • the processor 31 may specifically be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (ASIC). ), Field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof, which can implement or execute each described in combination with the content disclosed in the embodiments of the present invention.
  • An exemplary logic block, module, and circuit; the processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the memory 32 can be used to store software programs and modules.
  • the processor 31 executes various functional applications and data processing of the server 30 by running the software programs and modules stored in the memory 32.
  • the memory 32 may include one or more computer-readable storage media.
  • the memory 32 includes a storage program area and a storage data area, where the storage program area can store an operating system, application programs required for at least one function, and the like, and the storage data area can store data created by the server 30, etc.
  • the memory 32 may include an MME, and the terminal is connected to the network or the terminal establishes a session by running the MME.
  • the memory 32 may specifically include a volatile memory (such as a random-access memory (RAM); the memory may also include a non-volatile memory (non-volatile memory) , Such as read-only memory (ROM), flash memory (flash memory), hard disk (HDD) or solid-state drive (SSD); the memory may also include the above-mentioned types Memory combination.
  • a volatile memory such as a random-access memory (RAM)
  • the memory may also include a non-volatile memory (non-volatile memory) , Such as read-only memory (ROM), flash memory (flash memory), hard disk (HDD) or solid-state drive (SSD); the memory may also include the above-mentioned types Memory combination.
  • ROM read-only memory
  • flash memory flash memory
  • HDD hard disk
  • SSD solid-state drive
  • Communication interface 33 An interface circuit for the server 30 to communicate with other devices.
  • the communication interface may be a structure with a transceiver function such as a transceiver or a transceiver circuit.
  • the communication interface includes a serial communication interface and a parallel communication interface.
  • the terminal when the network side sends downlink data to the terminal, the terminal needs to be authenticated first, and after determining that the terminal is a legal or secure terminal, the downlink data is sent to the terminal.
  • the process of authenticating the terminal includes: the terminal generates a message authentication code (called message authentication code 1), and sends all or part of the message authentication code 1 to the mobile management function entity through the base station, and the mobile management function entity determines Whether all or part of the message authentication code 1 matches the message authentication code 2 generated by the mobility management function entity, and if it matches, it is determined that the terminal is a legitimate terminal.
  • message authentication code 1 a message authentication code
  • the data transmission method provided by the embodiment of the present invention may include S301-S314:
  • the terminal sends a random access preamble sequence to the base station.
  • the random access preamble sequence may be referred to as a random access preamble.
  • the random access preamble sequence can be regarded as a kind of random access request.
  • the terminal sends the random access preamble sequence on a PRACH resource allocated by the base station.
  • the base station receives a random access preamble sequence from the terminal.
  • the base station sends a random access response to the terminal.
  • the base station After receiving the random access preamble sequence sent by the terminal, the base station can respond accordingly. For details, refer to the related content of S102.
  • the terminal receives a random access response from the base station.
  • the terminal generates a first message authentication code by using the non-access layer integrity protection algorithm according to the freshness parameter and the non-access layer integrity protection key.
  • the non-access layer integrity protection key is a key generated by the terminal according to the security mode command sent by the mobile management function entity after the terminal and the mobile management function entity have completed the authentication process last time.
  • the freshness parameter may include any one of the following: physical layer parameters, broadcast packet parameters, access layer parameters, and uplink non-access layer parameters.
  • the physical layer parameters are parameters obtained by the terminal and the base station during the random access phase, and the physical layer parameters may include at least one of the following: an identifier of the terminal, a frame number for sending a random access preamble sequence, and the identifier of the terminal may be Is the C-RNTI of the terminal;
  • the broadcast packet parameter is a parameter included in the broadcast packet broadcast by the base station, and the broadcast packet parameter may include at least one of the following: a system frame number, a system information value tag, and a time Information, the system frame number is the frame number of the radio frame on the base station, and the time information can be carried in the system message, for example, the time information carried in the system information block (SIB) 16;
  • the parameters are the parameters obtained by the terminal and the base station in the RRC message, and the access layer parameters may include the value of PDCP CO
  • the terminal generates a first message authentication code by using the non-access layer integrity protection algorithm according to the terminal's serving cell identity, freshness parameters, and non-access layer integrity protection keys.
  • the terminal combines the serving cell identity and the identity of the terminal as the message input, and the non-access layer integrity protection key as the key input.
  • the count input is set to 0.
  • the direction input is set to 0
  • the bearer input is set to 0
  • the first message authentication code is generated by the integrity protection algorithm.
  • the physical layer parameter is used as the terminal identifier as an example
  • the broadcast packet parameter is used as the time information as an example
  • the access layer parameter is used as the value of PDCP
  • the non-access layer parameters in the above line are the uplink NAS counter.
  • the method for generating the first message authentication code may include any one of the following A1-A4:
  • the terminal generates a first message authentication code by using the non-access layer integrity protection algorithm according to the terminal's serving cell identity, the terminal identity, and the non-access layer integrity protection key.
  • the terminal generates a first message authentication code by using the non-access layer integrity protection algorithm according to the terminal's serving cell identity, absolute time, and non-access layer integrity protection key.
  • the terminal generates a first message authentication code by using the non-access layer integrity protection algorithm according to the terminal's serving cell identity, the terminal's PDCP count value, and the non-access layer integrity protection key.
  • the terminal uses the non-access layer integrity protection algorithm to generate the first message authentication code according to the terminal's serving cell identity, the terminal's uplink NAS COUNT, and the non-access layer integrity protection key.
  • the terminal sends a message 3 to the base station, where the message 3 includes a first uplink message authentication code.
  • the first uplink message authentication code is a part or all of the foregoing first message authentication code.
  • the first uplink message authentication code may be the lower 16 bits of the first message authentication code, or the first uplink message authentication code and the The first message authentication code is the same.
  • the above-mentioned message 3 also includes the S-TMSI (an identification information of the terminal) of the terminal; when the freshness parameter is an access layer parameter or a non-access layer parameter, the above-mentioned message 3 also Includes freshness parameter indication information, which is used to indicate the freshness parameter.
  • S-TMSI an identification information of the terminal
  • the freshness parameter indication information may include any of the following B1-B2 :
  • the above message 3 may be an RRC connection request message. Since the message 3 includes a first uplink message authentication code, the message 3 may also be understood as a downlink data early transmission request message.
  • the base station receives message 3 from the terminal.
  • the base station sends a freshness parameter or freshness parameter indication information and a first uplink message authentication code to the mobility management function entity.
  • the base station may determine the freshness parameter according to the context information of the terminal, and then send the freshness parameter to the mobile management function entity; in another implementation
  • the message 3 received by the base station includes the freshness parameter indication information. In this way, the base station can determine the freshness parameter indicated by the freshness parameter indication information according to the freshness parameter indication information, and then send the freshness parameter to the mobile management.
  • Functional entity in another implementation manner, the message 3 received by the base station includes the freshness parameter indication information, and the base station directly sends the freshness parameter indication information to the mobility management function entity.
  • the base station may obtain the serving cell identity of the terminal according to the context information of the terminal, and then the base station may send the serving cell identity of the terminal to the mobility management function entity.
  • the base station may send the S-TMSI, freshness parameter, or freshness parameter indication information of the terminal, and the first uplink message authentication code to the downlink data request or the terminal ’s initial context message and send it to the mobile. Management functional entity.
  • the mobility management function entity receives the freshness parameter or the freshness parameter indication information and the first uplink message authentication code from the base station.
  • the mobility management function entity may receive the serving cell identity of the terminal from the base station.
  • the mobile management function entity uses the non-access layer integrity protection algorithm to generate a second message authentication code according to the freshness parameter and the non-access layer integrity protection key.
  • the mobility management function entity when the mobility management function entity receives the freshness parameter from the base station, the mobility management function entity may directly adopt the non-access layer integrity protection algorithm according to the freshness parameter and the non-access layer integrity protection key.
  • the mobility management function entity To generate a second message authentication code; when the mobility management function entity receives the freshness parameter indication information from the base station, the mobility management function entity first determines the freshness parameter according to the freshness parameter indication information, and then according to the freshness parameter, non-access The layer integrity protection key uses a non-access layer integrity protection algorithm to generate a second message authentication code.
  • the method by which the mobile management function entity generates the second message authentication code is similar to the method by which the terminal generates the first message authentication code, that is, the mobile management function entity uses non-access based on the freshness parameter and the non-access layer integrity protection key.
  • the layer integrity protection algorithm generates the second message authentication code.
  • the freshness parameter used by the terminal to generate the first message authentication code is the same as the freshness parameter used by the mobile management function entity to generate the second message authentication code.
  • the freshness parameter used by the terminal to generate the first message authentication code is a physical layer parameter (such as the C-RNTI of the terminal)
  • the mobility management function entity is also generated according to the physical layer parameter (such as the C-RNTI of the terminal).
  • the above-mentioned second message authentication code, and the number of bits of the first message authentication code generated by the terminal are equal to the number of bits of the second message authentication code generated by the mobile management function entity, for example, both are 32 bits.
  • the mobility management function entity sends downlink data to the base station.
  • the mobile management function entity after the mobile management function receives the first uplink message authentication code sent by the base station, and the mobile management function entity generates the second message authentication code, the mobile management function entity first determines the first uplink message authentication code and the second message. Whether the authentication code matches. When the first uplink message authentication code matches the second message authentication code, the downlink data is sent to the base station.
  • the method for determining whether the first uplink message authentication code matches the second message authentication code by the mobility management function entity includes: determining the second message authentication code Whether the bit corresponding to the first uplink message authentication code is the same as the first uplink message authentication code.
  • the mobility management function instance compares whether the first uplink message authentication code and the second 16 bit of the second message authentication code are the same.
  • the mobile management function entity authenticates the terminal (that is, the mobile management function entity completes the authentication of the terminal), and considers the terminal to be a legal (or secure) terminal, so the mobile management function entity sends downlink data to the base station.
  • a method for the mobile management function entity to determine whether the first uplink message authentication code matches the second message authentication code includes: determining the first uplink message authentication code and Whether the second message authentication code is the same. If they are the same, the mobile management function entity authenticates the terminal and considers the terminal to be a legal (or secure) terminal, so that the mobile management function entity sends downlink data to the base station.
  • the mobility management function entity may also determine whether the first uplink message authentication code and the second message authentication code match according to other methods, which are not specifically limited in this embodiment of the present invention.
  • the base station receives downlink data from a mobility management function entity.
  • the base station sends a message 4 to the terminal, where the message 4 includes the downlink data.
  • the base station after the base station receives the downlink data from the mobility management function entity, the base station forwards the downlink data to the terminal by carrying message 4 to implement early downlink data transmission.
  • the terminal receives message 4 from the base station.
  • the data transmission method provided by the embodiment of the present invention may further include S300a-S300d:
  • the mobility management function entity sends the downlink data early transmission indication information to the base station.
  • the downlink data early transmission instruction information is used to instruct the terminal to receive the downlink data in message 4.
  • the terminal can learn that the terminal needs to perform early data transmission of the downlink during the random access process.
  • the base station receives the downlink data early transmission indication information from the mobility management function entity.
  • the base station sends the downlink data early transmission indication information to the terminal.
  • S300d The terminal obtains the downlink data early transmission indication information.
  • the mobility management function entity may send a first paging message, where the first paging message includes early downlink data transmission indication information; the base station receives the first paging message and obtains early data downlink transmission After the indication information, the base station may send a second paging message, where the second paging message includes the data early transmission indication information, so that the terminal receives the second paging message and obtains the data early transmission indication information.
  • the terminal may further obtain the downlink data indication information based on the high-level indication information of the terminal.
  • the terminal can also authenticate the mobile management function entity, and if the terminal passes the authentication of the mobile management function entity, the terminal retrieves the message from the message 4 Get downlink data.
  • the message 4 sent by the base station to the terminal further includes a first downlink message authentication code, where the first downlink message authentication code is a part of the second message authentication code.
  • the first The line message authentication code is the upper 16 bits of the second message authentication code.
  • the process for the base station to obtain the first downlink message authentication code may include: the mobile management function entity sends the first downlink message authentication code to the base station, and then the base station receives the first downlink message authentication code from the mobile management function entity.
  • the terminal after the terminal obtains the first downlink message authentication code from the message 4, the terminal determines whether the first downlink message authentication code matches the first message authentication code, and the first downlink message authentication code and the first downlink message authentication code match. When the message authentication codes match, the terminal obtains downlink data from the message 4.
  • the method is similar. For details, refer to the related description of the foregoing embodiments, and details are not described herein again.
  • the mobile management function entity After the mobile management function entity completes the authentication of the terminal and determines that the terminal is a legitimate terminal, the mobile management function entity sends downlink data to the terminal through the base station, and also sends the terminal to the terminal through the base station for the mobile management. Information for authentication by the functional entity.
  • the process of authenticating the mobile management function entity by the terminal includes the following S801-S807:
  • the mobility management function entity generates a third message authentication code by using a non-access layer integrity protection algorithm according to downlink data, downlink non-access layer parameters, and non-access layer integrity protection keys.
  • the mobility management function entity sends a third downlink message authentication code and downlink non-access layer parameter indication information to the base station.
  • the third downlink message authentication code is a part or all of the third message authentication code.
  • the base station receives the first downlink message authentication code and downlink non-access layer parameter indication information from the mobility management function entity.
  • the base station sends a first downlink message authentication code and downlink non-access layer parameter indication information to the terminal.
  • the terminal receives a third downlink message authentication code and downlink non-access layer parameter indication information.
  • the third downlink message authentication code and downlink non-access layer parameter indication information may be carried in message 4.
  • the terminal uses the non-access layer integrity protection algorithm to generate a fourth message authentication code according to the downlink data, the downlink non-access layer parameters, and the non-access layer integrity protection key.
  • the process of authenticating the terminal by the terminal to the mobile management function entity is similar to the process of authenticating the terminal by the mobile management function entity.
  • the process of authenticating the terminal by the mobile management function entity is similar to the process of authenticating the terminal by the mobile management function entity.
  • a terminal sends a random access preamble sequence to a base station, and receives a random access response from the base station, and then the terminal adopts non-access according to the freshness parameter and the non-access layer integrity protection key.
  • Layer integrity protection algorithm generating a first message authentication code, and carrying the first uplink message authentication code (the first uplink message authentication code is part or all of the first message authentication code) in message 3 and sending it to the base station Therefore, the base station sends the first uplink message authentication code to the mobile management function entity, and the mobile management function entity also uses the non-access layer integrity protection algorithm to generate a second based on the freshness parameter and the non-access layer integrity protection key.
  • the message authentication code is generating a first message authentication code, and carrying the first uplink message authentication code (the first uplink message authentication code is part or all of the first message authentication code) in message 3 and sending it to the base station.
  • the mobility management function entity When it is determined that the first uplink message authentication code matches the second message authentication code, the mobility management function entity sends the downlink data to the base station, so that the base station sends the downlink data to the terminal by sending the message 4 to the terminal. Can improve the security of early data transmission.
  • the first message authentication code or the second message authentication code may be based on different freshness parameters (for example, physical layer parameters, broadcast packet parameters, access layer parameters, or non- Any one of the parameters of the access layer) is generated.
  • different freshness parameters for example, physical layer parameters, broadcast packet parameters, access layer parameters, or non- Any one of the parameters of the access layer.
  • the data transmission method provided by the embodiment of the present invention may include S401-S414:
  • the terminal sends a random access preamble sequence to the base station.
  • the terminal before the terminal sends the random access preamble sequence, the terminal first receives a system message (for example, SIB2) from the base station, and the system message includes a PRACH resource for the terminal to send the random access preamble sequence.
  • a system message for example, SIB2
  • the PRACH resource indicated by the base station for the terminal when the terminal has no early data transmission requirement may be different from the PRACH resource indicated for the terminal when the terminal has an early data transmission requirement for the terminal.
  • the PRACH resource indicated by the base station for the terminal when the terminal has no early data transmission requirements is referred to as the non-data early transmission PRACH resource
  • the PRACH resource indicated by the terminal when the terminal has the early data transmission requirement is referred to as the early data transmission PRACH Resources.
  • the size of message 3 corresponding to the PRACH resource for non-early data transmission is 88 bits or 56 bits
  • the size of message 3 corresponding to the PRACH resource for early data transmission is a PRACH resource between 320 bits and 1000 bits.
  • the terminal sends a random access preamble sequence to the base station on a PRACH resource (for example, 88 bits) for non-data early transmission.
  • a PRACH resource for example, 88 bits
  • the base station receives a random access preamble sequence from the terminal.
  • the base station sends a random access response to the terminal.
  • the terminal receives a random access response from the base station.
  • the terminal generates a first message authentication code by using a non-access layer integrity protection algorithm according to the physical layer parameters and the non-access layer integrity protection key.
  • S405a can be specifically implemented through S405a:
  • S405a The terminal generates a first message authentication code by using the non-access layer integrity protection algorithm according to the terminal's serving cell identity, physical layer parameters, and non-access layer integrity protection key.
  • the terminal sends a message 3 to the base station, where the message 3 includes a first uplink message authentication code of the terminal.
  • first uplink message authentication code For the description of the first uplink message authentication code, reference may be made to the specific description of the first uplink message authentication code in the foregoing S306, and details are not described herein again.
  • the foregoing message 3 may not need to carry the foregoing physical layer parameters.
  • the base station receives message 3 from the terminal.
  • the base station sends physical layer parameters and a first uplink message authentication code to the mobility management function entity.
  • the physical layer parameters are parameters synchronized between the terminal and the base station, but the physical layer parameters are not synchronized on the mobility management function entity, and the physical layer parameters are not included in the above message 3.
  • the base station can determine the physical layer parameters corresponding to the terminal, such as the C-RNTI of the terminal, and can also determine the serving cell identity of the terminal, and then the base station sends the serving cell identity and physical layer of the terminal to the mobile management function entity Parameters and the first uplink message authentication code.
  • the message 3 sent by the terminal to the base station does not need to carry the physical layer parameters.
  • the base station After receiving the message 3, the base station itself can determine the physical parameters of the terminal. Layer parameters. In this way, the terminal can save resources for sending message 3.
  • the PRACH resource allocated by the base station to the terminal for non-data early transmission is 88 bits
  • the physical layer parameter does not need to be carried in the above message 3
  • the resource required by the base station to send message 3 will be less than the non-early PRACH transmission.
  • the size of message 3 corresponding to the resource for example, 88 bits or 56 bits).
  • the base station may also determine the identity of the terminal's service message, and send the terminal's serving cell identity to the mobility management function entity.
  • the mobility management function entity receives a physical layer parameter and a first uplink message authentication code from the base station.
  • the mobility management function entity may also receive the serving cell identity of the terminal from the base station.
  • the mobile management function entity uses the non-access layer integrity protection algorithm to generate a second message authentication code according to the physical layer parameters and the non-access layer integrity protection key.
  • the mobility management function entity sends downlink data to the base station.
  • the base station receives downlink data from a mobility management function entity.
  • S413 The base station sends a message 4 to the terminal, where the message 4 includes the downlink data.
  • S414 The terminal receives message 4 from the base station.
  • the terminal can authenticate the mobile management function entity (that is, the terminal can determine the first downlink message authentication code sent by the mobile management function and the first message authentication generated by the terminal. Whether the codes match), please refer to the method for authenticating the mobile management function instance by the terminal described in the embodiments of S301-S314 above.
  • the data transmission method provided by the embodiment of the present invention may include S501-S514:
  • the terminal sends a random access preamble sequence to the base station.
  • the terminal also sends a random access preamble sequence to the base station on the PRACH resource for non-data early transmission.
  • the base station receives a random access preamble sequence from the terminal.
  • the base station sends a random access response to the terminal.
  • the terminal receives a random access response from the base station.
  • S505 The terminal generates a first message authentication code by using a non-access layer integrity protection algorithm according to a broadcast packet parameter and a non-access layer integrity protection key.
  • the terminal generates a first message authentication code by using the non-access layer integrity protection algorithm according to the terminal's serving cell identity, the broadcast packet parameters, and the non-access layer integrity protection key.
  • the terminal sends a message 3 to the base station, where the message 3 includes a first uplink message authentication code of the terminal.
  • the base station receives message 3 from the terminal.
  • the base station sends a broadcast packet parameter and a first uplink message authentication code to the mobility management function entity.
  • the above broadcast packet parameters are also parameters synchronized between the terminal and the base station. Therefore, after the base station receives message 3, the base station can determine the corresponding broadcast packet parameters of the terminal, such as the time of the terminal. Information, and may also determine the serving cell identity of the terminal, and then the base station sends the serving cell identity of the terminal, the broadcast packet parameters, and the first uplink message authentication code to the mobile management function entity.
  • the broadcast packet parameters are parameters synchronized between the terminal and the base station
  • the message 3 sent by the terminal to the base station does not need to carry the broadcast packet parameters.
  • the base station After receiving the message 3, the base station itself can determine the broadcast of the terminal. Package parameters. In this way, the terminal can save resources for sending message 3.
  • the base station may also determine the identity of the terminal's service message, and send the terminal's serving cell identity to the mobility management function entity.
  • the mobility management function entity receives a broadcast packet parameter and a first uplink message authentication code from the base station.
  • the mobility management function entity may also receive the serving cell identity of the terminal from the base station.
  • the mobile management function entity uses the non-access layer integrity protection algorithm to generate a second message authentication code according to the broadcast packet parameters and the non-access layer integrity protection key.
  • the mobility management function entity sends downlink data to the base station.
  • the base station receives downlink data from a mobility management function entity.
  • the base station sends a message 4 to the terminal, where the message 4 includes the downlink data.
  • the terminal receives message 4 from the base station.
  • the terminal can authenticate the mobile management function entity.
  • the terminal can authenticate the mobile management function entity.
  • the specific process refer to the authentication of the mobile management function instance by the terminal described in the foregoing embodiment.
  • the process of early transmission of downlink data when the freshness parameter is a broadcast packet parameter is similar to the process of early transmission of downlink data when the freshness parameter is a physical layer parameter. Therefore, for a detailed description of S501-S514, refer to the foregoing implementation. The relevant descriptions of S401-S414 in the example are not repeated here.
  • the data transmission method provided by the embodiment of the present invention may include S601-S614:
  • the terminal sends a random access preamble sequence to the base station.
  • the terminal sends a random access preamble sequence to the base station on a PRACH resource (for example, 320 bits) for early data transmission.
  • a PRACH resource for example, 320 bits
  • the base station receives a random access preamble sequence from the terminal.
  • the base station sends a random access response to the terminal.
  • the terminal receives a random access response from the base station.
  • the terminal generates a first message authentication code by using a non-access layer integrity protection algorithm according to the access layer parameters and the non-access layer integrity protection key.
  • S605 may be specifically implemented through S605a:
  • S605a The terminal generates a first message authentication code by using the non-access layer integrity protection algorithm according to the terminal's serving cell identity, access layer parameters, and non-access layer integrity protection key.
  • the terminal sends a message 3 to the base station, where the message 3 includes access layer parameter indication information and a first uplink message authentication code of the terminal.
  • the access layer parameter indication information is used to indicate an access layer parameter.
  • the access layer parameter is the value of PDPC_COUNT
  • the above-mentioned access layer parameter indication information may be a partial bit of the value of PDPC_COUNT, for example, the access layer parameter indication information is the lower 8 bits or lower 5 bits of the value of PDCP_COUNT.
  • the terminal carries the indication information of the access layer parameters in the message 3, but does not directly carry the access layer parameters. In this way, the resources of the terminal sending the message 3 can be saved to a certain extent.
  • the base station receives message 3 from the terminal.
  • the base station may determine the access layer parameters according to the obtained access layer parameter indication. For example, when the access layer parameter indication information is the lower 8 bits of the value of the PDCP count, the base station The value of PDCP COUNT can be recovered according to the lower 8 bits of the value of PDCP COUNT.
  • the base station sends the access layer parameters and the first uplink message authentication code to the mobility management function entity.
  • the base station determines the access layer parameters according to the access layer parameter indication information, and then the base station sends the access layer parameters and the first uplink message authentication code to the mobility management function entity.
  • the base station may also determine the identity of the terminal's service message, and send the terminal's serving cell identity to the mobility management function entity.
  • the mobility management function entity receives an access layer parameter and a first uplink message authentication code from the base station.
  • the mobility management function entity may also receive the serving cell identity of the terminal from the base station.
  • the mobile management function entity uses the non-access layer integrity protection algorithm to generate a second message authentication code according to the access layer parameters and the non-access layer integrity protection key.
  • the mobility management function entity sends downlink data to the base station.
  • the base station receives downlink data from a mobility management function entity.
  • the base station sends a message 4 to the terminal, where the message 4 includes the downlink data.
  • S614 The terminal receives message 4 from the base station.
  • the terminal can authenticate the mobile management function entity.
  • the freshness parameter is an access layer parameter
  • the terminal can authenticate the mobile management function entity.
  • Method of authentication refer to the example of the mobile management function of the terminal described in the foregoing embodiment.
  • the data transmission method provided by the embodiment of the present invention may include S701-S714:
  • the terminal sends a random access preamble sequence to the base station.
  • the terminal sends a random access preamble sequence to the base station on a PRACH resource (for example, 300 bits) for early data transmission.
  • a PRACH resource for example, 300 bits
  • the base station receives a random access preamble sequence from a terminal.
  • S703 The base station sends a random access response to the terminal.
  • the terminal receives a random access response from the base station.
  • the terminal generates a first message authentication code by using a non-access layer integrity protection algorithm according to the uplink non-access layer parameters and the non-access layer integrity protection key.
  • S705a The terminal generates a first message authentication code by using the non-access layer integrity protection algorithm according to the terminal's serving cell identity, the uplink non-access layer parameters, and the non-access layer integrity protection key.
  • the terminal sends a message 3 to the base station, where the message 3 includes uplink non-access layer parameter indication information and a first uplink message authentication code of the terminal.
  • the uplink non-access stratum parameter indication information is used to indicate an uplink non-access stratum parameter.
  • the uplink non-access layer parameter is the value of the uplink NAS COUNT
  • the above uplink non-access layer parameter indication information may be a part of the bit of the uplink NAS COUNT value, for example, the uplink non-access layer parameter indication information is the uplink NAS COUNT value Lower 8 bits or lower 5 bits.
  • the terminal carries the indication information of the uplink non-access layer parameters in the message 3, but does not directly carry the uplink non-access layer parameters. In this way, the resources for the terminal to send the message 3 can be saved to a certain extent.
  • the base station receives message 3 from the terminal.
  • the base station sends uplink non-access layer parameter indication information and a first uplink message authentication code to the mobility management function entity.
  • the base station may also determine the identity of the terminal's service message, and send the terminal's serving cell identity to the mobility management function entity.
  • the uplink non-access layer parameter is a parameter synchronized between the terminal and the mobile management function entity, and the uplink non-access layer parameter is not synchronized on the base station, so the terminal needs to carry it in message 3.
  • the related information of the uplink non-access layer parameters (such as the above-mentioned uplink non-access layer parameter indication information), and then the base station transmits the related information of the uplink non-access layer parameters to the mobility management function entity.
  • the mobility management function entity receives uplink non-access layer parameter indication information and a first uplink message authentication code from the base station.
  • the mobility management function entity may also receive the serving cell identity of the terminal from the base station.
  • the mobile management function entity after the mobile management function entity receives the uplink non-access layer parameter indication information, it needs to determine the uplink non-access layer parameter according to the uplink non-access layer parameter indication information.
  • the base station may recover the value of the uplink NAS COUNT according to the lower 8 bits of the value of the uplink NAS COUNT.
  • the mobile management function entity uses the non-access layer integrity protection algorithm to generate a second message authentication code according to the uplink non-access layer parameters and the non-access layer integrity protection key.
  • the mobility management function entity sends downlink data to the base station.
  • the base station receives downlink data from a mobility management function entity.
  • S713 The base station sends a message 4 to the terminal, where the message 4 includes the downlink data.
  • S714 The terminal receives message 4 from the base station.
  • the terminal can authenticate the mobile management function entity.
  • the terminal can authenticate the mobile management function entity.
  • the specific process refer to the authentication of the mobile management function instance by the terminal described in the foregoing embodiment.
  • the mobility management function entity may also carry a single downlink data indication information in the paging message or the context message of the terminal, and the single downlink data indication information is used to instruct the terminal to receive during the random access process.
  • a single downlink data packet so that a single downlink data is received according to the data transmission method described in the foregoing method embodiments.
  • the base station may send an early transmission completion message of downlink data to the terminal, and then release the connection (such as the S1 connection) between the base station and the mobile management function entity.
  • each network element such as a terminal, a base station, and a mobile management function entity, includes a hardware structure and / or a software module corresponding to each function.
  • each network element such as a terminal, a base station, and a mobile management function entity
  • each network element includes a hardware structure and / or a software module corresponding to each function.
  • the embodiments of the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application of the technical solution and design constraints. A professional technician may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
  • functional modules can be divided into terminals, base stations, and mobile management function entities according to the foregoing method examples.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one.
  • Processing module may be implemented in the form of hardware or software functional modules. It should be noted that the division of the modules in the embodiments of the present invention is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • FIG. 13 illustrates a possible structural diagram of a terminal involved in the foregoing embodiment.
  • the terminal may include a sending module 40, a receiving module 41, and a generating module 42.
  • the sending module 40 is used to support the terminal to execute S101, S103, S105, S201, S203, S301, S306, S401, S406, S501, S506, S601, S606, S701, and S706 in the above method embodiment;
  • the receiving module 41 is used The support terminal executes S304, S314, S404, S414, S504, S514, S604, S614, S704, S714, and S805 in the above method embodiment;
  • the generating module 42 is used to support the terminal to execute S305, S405 in the above method embodiment , S505, S605, S705, and S806.
  • the terminal may further include an obtaining module 43, which is configured to support the terminal to execute S807 in the foregoing method embodiment.
  • all relevant content of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here.
  • FIG. 14 shows a possible structural diagram of a terminal involved in the foregoing embodiment.
  • the terminal may include a processing module 50 and a communication module 51.
  • the processing module 50 may be used to control and manage the actions of the terminal.
  • the processing module 50 may be used to support the terminal to execute S305, S405, S505, S605, S705, S806, and S807 in the foregoing method embodiment;
  • the communication module 51 may be used For supporting the communication between the terminal and other network entities, for example, the communication module 51 may be used to support the terminal to execute S101, S103, S105, S201, S203, S301, S304, S306, S314, S401, S404, S406, S414, S501, S504, S506, S514, S601, S604, S606, S614, S701, S704, S706, S714, and S805.
  • the terminal may further include a storage module 52 for storing program code and data of the terminal.
  • the processing module 50 may be a processor or a controller.
  • the processing module 50 may be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of the embodiments of the present invention.
  • the above processor may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication module 51 may be a transceiver, a transceiver circuit, or a communication interface. Exemplarily, the communication module 51 is a radio frequency transceiver circuit for up-mixing a signal to be transmitted when transmitting and down-mixing a received signal when receiving.
  • the storage module 52 may be a memory.
  • the processing module 50 is a processor
  • the communication module 51 is a transceiver
  • the storage module 52 is a memory
  • the processor, the transceiver, and the memory may be connected through a bus.
  • the bus may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • the processing module 50 and the communication module 51 jointly implement signal reception. Specifically, the processing module 50 controls or calls the communication module 51 to receive.
  • the processing module 50 is the decider and controller of the receiving behavior
  • the communication module 51 is the performer of the receiving behavior.
  • FIG. 15 shows a possible structural diagram of a base station involved in the foregoing embodiment.
  • the base station may include a receiving module 60 and a sending module 61.
  • the receiving module 60 is used to support the base station to perform S302, S307, S312, S402, S407, S412, S502, S507, S512, S602, S607, S612, S702, S707, S712, and S803 in the above method embodiment;
  • the sending module 61 Used to support the base station to execute S102, S104, S106, S202, S204, S303, S308, S313, S403, S408, S413, S503, S508, S513, S603, S608, S613, S703, S708, S713 And S804.
  • all relevant content of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here.
  • FIG. 16 shows a possible structural diagram of a base station involved in the foregoing embodiment.
  • the base station may include a processing module 70 and a communication module 71.
  • the processing module 70 may be used to control and manage the actions of the base station.
  • the communication module 71 may be used to support communication between the base station and other network entities.
  • the communication module 71 may be used to support the base station to perform S102, S104, S106, S202, S204, S302, S303, S307, S308, S312 in the above method embodiment.
  • the base station may further include a storage module 72 for storing program codes and data of the terminal.
  • the communication module 71 is a radio frequency transceiver circuit for up-mixing a signal to be transmitted when transmitting and down-mixing a received signal when receiving.
  • the processing module 70 may be a processor or a controller (for example, the processor in the above part 21 shown in FIG. 5), and may be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic. Devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of the embodiments of the present invention.
  • the above processor may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication module 71 may be a transceiver, a transmission / reception circuit, a communication interface, or the like (for example, it may be a radio frequency unit in the above 20 part shown in FIG. 5).
  • the storage module 72 may be a memory (for example, the memory in the above-mentioned part 21 shown in FIG. 5).
  • the processing module 70 is a processor
  • the communication module 71 is a transceiver
  • the storage module 72 is a memory
  • the processor, the transceiver, and the memory may be connected through a bus.
  • the bus may be a PCI bus or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • the processing module 70 and the communication module 71 jointly implement signal transmission. Specifically, the processing module 70 controls or calls the communication module 71 to send.
  • the processing module 70 is a decider and a controller of the transmission behavior
  • the communication module 71 is an executor of the transmission behavior.
  • FIG. 17 shows a possible structural schematic diagram of a mobility management function entity involved in the foregoing embodiment.
  • the mobility management function entity may include a receiving module 80, a generating module 81, and a sending module 82.
  • the receiving module 80 is used to support the mobile management function entity to perform S309, S409, S509, S609, and S709 in the above method embodiment; the generating module 81 is used to support the mobile management function entity to perform S310, S410, and S510 in the above method embodiment , S610, S710, and S801; the sending module 82 is configured to support the mobile management function entity to execute S311, S411, S511, S611, S711, and S802 in the foregoing method embodiment.
  • all relevant content of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here.
  • the mobility management function entity may further include a determining module, which is configured to determine the number of uplink non-access layers according to the uplink non-access layer parameter indication information.
  • FIG. 18 shows a possible structural diagram of a mobility management function entity involved in the foregoing embodiment.
  • the mobility management function entity may include: a processing module 90 and a communication module 91.
  • the processing module 90 may be used to control and manage the actions of the mobile management function entity.
  • the processing module 90 may be used to support the mobile management function entity to perform S310, S410, S510, S610, S710, and S801 in the foregoing method embodiments.
  • the communication module 91 may be used to support communication between the mobile management function entity and other network entities.
  • the communication module 91 may be used to support the mobile management function entity to perform S309, S311, S409, S411, S509, S511, S609 in the above method embodiment. , S611, S709, S711, and S802.
  • the mobility management function entity may further include a storage module 92 for storing program code and data of the mobility management function entity.
  • the communication module 91 is a radio frequency transceiver circuit, which is used for up-mixing a signal to be transmitted when transmitting and down-mixing a received signal when receiving.
  • the processing module 90 may be a processor or a controller (for example, the processor 31 shown in FIG. 6 described above), and may be, for example, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices and transistors. Logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of the embodiments of the present invention.
  • the above processor may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication module 91 may be a transceiver, a transmission / reception circuit, or a communication interface (for example, the communication interface 32 shown in FIG. 6 described above).
  • the storage module 92 may be a memory (for example, the memory 33 shown in FIG. 6 described above).
  • the processing module 70 is a processor
  • the communication module 91 is a transceiver
  • the storage module 92 is a memory
  • the processor, the transceiver, and the memory may be connected through a bus.
  • the bus may be a PCI bus or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • the processing module 90 and the communication module 91 jointly implement signal transmission. Specifically, the processing module 90 controls or calls the communication module 91 to send.
  • the processing module 90 is a decider and a controller of the transmission behavior
  • the communication module 91 is an executor of the transmission behavior.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present invention are wholly or partially generated.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center through a cable (Such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like including one or more available medium integration.
  • the available medium may be a magnetic medium (for example, a floppy disk, a magnetic disk, a magnetic tape), an optical medium (for example, a digital video disc (DVD)), or a semiconductor medium (for example, solid state drives (SSD)), etc. .
  • a magnetic medium for example, a floppy disk, a magnetic disk, a magnetic tape
  • an optical medium for example, a digital video disc (DVD)
  • a semiconductor medium for example, solid state drives (SSD)
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the modules or units is only a logical function division.
  • multiple units or components may be divided.
  • the combination can either be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional unit.
  • the integrated unit When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially a part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium. , Including a number of instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the method described in the embodiments of the present application.
  • the foregoing storage media include: flash media, mobile hard disks, read-only memories, random access memories, magnetic disks, or optical discs, which can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention se rapporte au domaine technique des communications. La présente invention porte, dans un mode de réalisation, sur un procédé de transmission de données permettant d'améliorer la sécurité de la transmission de données rapide. Le procédé consiste : à transmettre une séquence de préambule d'accès aléatoire à une station de base ; à recevoir une réponse d'accès aléatoire en provenance de la station de base ; à utiliser, en fonction d'un nouveau paramètre et d'une clé de protection d'intégrité de strate sans accès, un algorithme de protection d'intégrité de strate sans accès permettant de générer un premier code d'authentification de message ; à transmettre un message 3 à la station de base, le message 3 transportant un premier code d'authentification de message de liaison montante, et le premier code d'authentification de message de liaison montante comprenant le premier code d'authentification de message, en partie ou en totalité ; et à recevoir un message 4 à partir de la station de base, le message 4 comprenant des données de liaison descendante.
PCT/CN2018/103853 2018-09-03 2018-09-03 Procédé et dispositif de transmission de données WO2020047724A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/103853 WO2020047724A1 (fr) 2018-09-03 2018-09-03 Procédé et dispositif de transmission de données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/103853 WO2020047724A1 (fr) 2018-09-03 2018-09-03 Procédé et dispositif de transmission de données

Publications (1)

Publication Number Publication Date
WO2020047724A1 true WO2020047724A1 (fr) 2020-03-12

Family

ID=69721973

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/103853 WO2020047724A1 (fr) 2018-09-03 2018-09-03 Procédé et dispositif de transmission de données

Country Status (1)

Country Link
WO (1) WO2020047724A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106664511A (zh) * 2014-07-11 2017-05-10 高通股份有限公司 用于无连接接入的方法和装置

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106664511A (zh) * 2014-07-11 2017-05-10 高通股份有限公司 用于无连接接入的方法和装置

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"Clarification on EDT Procedure", 3GPP TSG-SA2 MEETING #128BIS S 2-188402, 26 August 2018 (2018-08-26) *
CORRECTIONS TO R2-1811824, 10 August 2018 (2018-08-10), XP051521463 *
ERICSSON: "E126] Protection of User Data in EDT", 3GPP TSG-RAN WG2 #103 R2-1812265, 10 August 2018 (2018-08-10), XP051521872 *
ERICSSON: "Remaining Security Aspects for EDT", 3GPP TSG-RAN WG2 #102 R2-1807801, 11 May 2018 (2018-05-11), XP051464927 *

Similar Documents

Publication Publication Date Title
TWI678123B (zh) 具有頻寬部分切換的隨機接取技術
KR102390889B1 (ko) 데이터 송신 방법, 단말 디바이스, 및 액세스 네트워크 디바이스
TWI559721B (zh) 雙連結中分配無線網路暫時識別的方法
TWI336577B (en) Method and mobile terminal for communicating data in a wireless communications system
WO2018126801A1 (fr) Procédé et appareil d'envoi de données, procédé et appareil de réception de données
CN104581843B (zh) 用于无线通信系统的网络端的处理交递方法及其通信装置
JP5851539B2 (ja) 複数の基地局および関連する通信装置との同時通信方法
JP2018518117A (ja) ワイヤレス通信システムにおける小データ送信
EP3813426B1 (fr) Procédé, appareil et système de vérification de sécurité
JP7405265B2 (ja) 端末装置及び基地局
WO2018227638A1 (fr) Procédé et appareil de communication
WO2014196908A1 (fr) Appareil de télécommunication et procédé concernant une procédure d'accès aléatoire
WO2017024468A1 (fr) Procédé et appareil d'accès aléatoire
WO2017133004A1 (fr) Procédé, appareil et système de transmission d'informations de liaison montante d'état de veille
CN116723507B (zh) 针对边缘网络的终端安全方法及装置
WO2021051974A1 (fr) Procédé et appareil de protection de sécurité pour informations d'interface radio
CN108141895B (zh) 用户设备ue接入网络的方法、网络设备及第一ue
US20220264520A1 (en) Communication method and apparatus
WO2022116809A1 (fr) Procédé, appareil et système d'accès aléatoire
WO2020047724A1 (fr) Procédé et dispositif de transmission de données
JP7401669B2 (ja) 接続再開方法及び装置
WO2020221279A1 (fr) Procédé et appareil d'accès aléatoire
CN112601222B (zh) 一种空口信息的安全保护方法及装置
US11057947B2 (en) Radio network temporary identifier generation
CN116074977A (zh) 通信方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18932684

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18932684

Country of ref document: EP

Kind code of ref document: A1