WO2020155174A1

WO2020155174A1 - Information transmission method and communication device

Info

Publication number: WO2020155174A1
Application number: PCT/CN2019/074688
Authority: WO
Inventors: 王宏; 单宝堃
Original assignee: 华为技术有限公司
Priority date: 2019-02-03
Filing date: 2019-02-03
Publication date: 2020-08-06

Abstract

Provided in the present application are an information transmission method and a communication device. The method comprises: a first access network device receiving first information from a core network device, wherein the first information is used for the first access network device to determine a context of a terminal device; the context is used for the first access network device to send downlink data to the terminal device; and the context is suspended; the first access network device determining the context according to the first information; and the first access network device sending the downlink data to the terminal device according to the context. According to the information transmission method provided in the present application, the core network device notifies the first access network device of first information used for the first access network device to determine the context of the terminal device. The first access network device can restore the context of the terminal device according to the first information, so that when the downlink data sent by the core network device is received, the downlink data can be sent to the terminal device according to the context. The downlink data can be sent to the terminal device earlier, thereby reducing the power consumption overheads for the terminal device to receive the downlink data, and improving the efficiency and reliability of downlink data transmission, and thus improving communication efficiency.

Description

Information transmission method and communication device

Technical field

This application relates to the field of communications, and more specifically, to a method and communication device for information transmission.

Background technique

In the current user plane solution for early data transmission, the access network device sends downlink data to the terminal device after Msg3. The access network device will obtain the context of the terminal device according to Msg3, and use the context of the terminal device to send downlink data from the core network device to the terminal device. For example, the access network device uses the security information in the context of the terminal device to encrypt the downlink data. Then the encrypted downlink data is sent to the terminal device. For the scenario of small downlink data, for example, the core network device has the downlink data of the terminal device arrives, and the data volume of the downlink data is small, if the downlink data is still sent to the terminal device after Msg3, the terminal device needs to go through complicated signaling The interaction process, for example, needs to go through Msg1, Msg2, Msg3, and then the access network device can send the downlink data to the terminal device. There are more uplink and downlink signaling interactions, which makes the transmission power consumption of downlink data larger, which seriously affects the downlink The efficiency of data transmission. Therefore, how to improve the transmission efficiency of downlink data has become an urgent problem to be solved at present.

Summary of the invention

The present application provides an information transmission method, which reduces the power consumption overhead of the terminal receiving downlink data, improves the efficiency and reliability of downlink data transmission, and thereby improves communication efficiency.

In the first aspect, a method for information transmission is provided, and the execution subject of the method can be either an access network device or a chip applied to the access network device. The method includes: a first access network device receives first information from a core network device, the first information is used by the first access network device to determine the context of the terminal device, and the context is used by the first access network device The terminal device sends downlink data; wherein the context is suspended; the first access network device determines the context according to the first information; the first access network device sends the context to the terminal device according to the context Downlink data.

In the information transmission method provided in the first aspect, the core network device notifies the first access network device of first information used for the first access network device to determine the context of the terminal device. Among them, the context of the terminal device has been suspended. The first access network device may determine (restore or activate) the context of the terminal device according to the first information, so that when receiving downlink data sent by the core network device, it may send the downlink data to the terminal device according to the context . The downlink data can be sent to the terminal device earlier. For example, the downlink data can be sent to the terminal device before Msg4 or Msg3, which reduces the power consumption overhead of the terminal receiving downlink data and improves the efficiency and reliability of downlink data transmission. Improve communication efficiency.

In a possible implementation manner of the first aspect, the context includes a security context; the first access network device sending the downlink data to the terminal device according to the context includes: the first access network device according to the The security context encrypts and/or integrity protects the downlink data; the first access network device sends the encrypted and/or integrity protected downlink data to the terminal device. In this implementation, by using the security context to encrypt and/or integrity protect the downlink data, and then send the encrypted and/or integrity protected downlink data to the terminal device, the security and reliability of the downlink data transmission can be improved It further improves the guarantee of downlink data transmission.

In a possible implementation of the first aspect, the first access network device sending the downlink data to the terminal device according to the context includes: the first access network device sending the downlink data to the terminal device according to the context Send second information, where the second information includes the downlink data.

In a possible implementation manner of the first aspect, the method further includes: the first access network device sends second information to the terminal device at a paging time when the paging message is sent, and the second information is used for scheduling The downlink data; or, the first access network device sends second information to the terminal device, the second information includes scheduling information, and the scheduling information is used to schedule the downlink data.

In a possible implementation of the first aspect, the second information is the paging message, the paging message further includes scheduling information, and the scheduling information is used to schedule the downlink data, or the second information is scheduling Information, the scheduling information is used to schedule the downlink data.

In a possible implementation manner of the first aspect, the first information includes a first identifier of the terminal device and the context, and the first identifier is allocated by the core network device; or, the first information includes the terminal device The second identifier of the terminal device is assigned by the first access network device, and the second identifier is used to identify the context; or, the first information includes the second identifier of the terminal device and the context.

In a possible implementation of the first aspect, the method further includes: the first access network device sends a first request to the core network device, where the first request is used to request suspension or deactivation of the context, The first request includes third information, and the third information is used by the first access network device to determine the context of the terminal device; the first access network device receives the first request from the core network device in response to the first request A response message, the first response message is used to instruct the first access network device to suspend or deactivate the context of the terminal device; the first access network device suspends or deactivates according to the first response message The context of the terminal device. In this implementation manner, the first access network device notifies the core network device of the context related information when the context of the terminal device is suspended, so that when the core network device has downlink data from the terminal device, the core network device The device can notify the access network device of the related information of the context of the terminal device, so as to realize early transmission of downlink data, and improve the efficiency of the downlink data transmission.

In a possible implementation manner of the first aspect, the third information includes a first identifier of the terminal device and the context, and the first identifier is allocated by the core network device; or, the third information includes the terminal device The second identifier is assigned by the first access network device, and the second identifier is used to identify the context; or, the third information includes the second identifier of the terminal device and the context.

In a possible implementation of the first aspect, the first information further includes first indication information, and the first indication information is used to indicate that the downlink data will trigger the terminal device to send uplink data, and the downlink data will not trigger The terminal device sends uplink data and the downlink data only includes at least one of a data packet.

In a possible implementation of the first aspect, the first identifier is the system architecture evolution temporary mobile equipment identifier S-TMSI or the international mobile subscriber identity IMSI of the terminal device; the second identifier is the recovery of the terminal device Identifies the resume ID.

In the second aspect, a method for information transmission is provided, and the execution subject of the method can be either a core network device or a chip applied to the core network device. The method includes: a core network device determines first information, the first information is used by a first access network device to determine a context of a terminal device, and the context is used by the first access network device to send downlink data to the terminal device, where , The context is suspended; the core network device sends the first information to the first access network device.

The information transmission method provided in the second aspect notifies the core network device of relevant information about the context of the suspended terminal device through the access network device, so that when the core network device has downlink data from the terminal device, the core network device The related information of the context of the terminal device can be notified to the access network device, so that when the access network device receives the downlink data, the access network device can obtain the context of the terminal device according to the related information of the context , And then send the downlink data to the terminal device according to the context. The downlink data can be sent to the terminal device before Msg4 or Msg3, which reduces the power consumption of the terminal receiving downlink data, improves the efficiency and reliability of downlink data transmission, and thereby improves communication efficiency.

In a possible implementation manner of the second aspect, the first information includes a first identifier of the terminal device and the context, and the first identifier is allocated by the core network device; or, the first information includes the terminal device's A second identifier, where the second identifier is allocated by the first access network device, and the second identifier is used to identify the context; or, the first information includes the second identifier of the terminal device and the context.

In a possible implementation of the second aspect, the method further includes: the core network device receives a first request from the first access network device, the first request is used to request to suspend or deactivate the context, the The first request includes third information, which is used by the first access network device to determine the context of the terminal device; the core network device sends the first access network device in response to the first request to the first access network device. A response message, where the first response message is used to instruct the first access network device to suspend or deactivate the context. In this implementation manner, the first access network device notifies the core network device of the context related information when the terminal device is suspended up and down, so that when the core network device has downlink data from the terminal device, the core network device The device can notify the access network device of the related information of the context of the terminal device, so as to realize early transmission of downlink data, and improve the efficiency of the downlink data transmission.

In a possible implementation manner of the second aspect, the third information includes the first identifier of the terminal device and the context, and the first identifier is allocated by the core network device; or, the third information includes the terminal device The second identifier is assigned by the first access network device, and the second identifier is used to identify the context; or, the third information includes the second identifier of the terminal device and the context.

In a possible implementation of the second aspect, the first information further includes first indication information, and the first indication information is used to indicate that the downlink data will trigger the terminal device to send uplink data, and the downlink data will not trigger The terminal device sends uplink data, and the downlink data only includes at least one of a data packet.

In a possible implementation of the second aspect, the first identifier is the system architecture evolution temporary mobile equipment identifier S-TMSI or the international mobile subscriber identity IMSI of the terminal device; the second identifier is the recovery of the terminal device Identifies the resume ID.

In a possible implementation of the second aspect, the core network device may be an S-GW, or an MME, or an SMF, or an AMF, or a UPF, etc.

In the third aspect, a method of information transmission is provided, and the execution subject of the method can be a terminal device or a chip applied to the terminal device. The method includes: a terminal device receives second information from a first access network device, the second information includes second indication information, the second indication information is used to instruct the terminal device to restore the context of the terminal device, wherein the context Is suspended; the terminal device restores the context according to the second information;

The terminal device receives downlink data from the first access network device according to the restored context.

According to the information transmission method provided by the third aspect, the terminal device can restore the context according to the second information sent by the access network device, and receive the downlink data sent by the access network device according to the restored context section, which can realize the early downlink data For example, the terminal device can receive the downlink data before Msg4 or Msg3 according to the context, which reduces the power consumption of the terminal device for receiving downlink data, and improves the efficiency and reliability of downlink data transmission. Thereby improving communication efficiency.

In a possible implementation manner of the third aspect, the context includes a security context, and the method further includes: the terminal device performs processing on the downlink received from the first access network device according to the security context in the context The data is decrypted.

In a possible implementation manner of the third aspect, the second information is a paging message, and the paging message includes the downlink data.

In a possible implementation manner of the third aspect, the terminal device receiving the second information from the first access network device includes: the terminal device receives the paging message from the first access network device at the paging time The second information is received, and the second information further includes scheduling information, and the scheduling information is used to schedule the downlink data.

In a possible implementation of the third aspect, the second information is a paging message, the paging message further includes scheduling information, the scheduling information is used to schedule the downlink data, or the second information is scheduling information , The scheduling information is used to schedule the downlink data.

In a fourth aspect, a communication device is provided, which includes steps for executing the methods in the first to third aspects, or any one of the first to third aspects and their possible implementations. Unit.

In one design, the communication device is a communication chip, and the communication chip may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

In another design, the communication device is a communication device (for example, a terminal device or an access network device or a core network device), and the communication chip may include a transmitter for sending information or data, and for receiving information or Data receiver.

In a fourth aspect, a terminal device is provided, including a transceiver, a processor, and a memory. The processor is used to control the transceiver to send and receive signals, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the terminal device executes the third aspect or any of the third aspects. The method in each implementation mode.

Optionally, there are one or more processors and one or more memories.

Optionally, the memory may be integrated with the processor, or the memory and the processor may be provided separately.

In a fifth aspect, an access network device is provided, including a transceiver, a processor, and a memory. The processor is used to control the transceiver to send and receive signals, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the access network device executes the first aspect or any one of the first aspect The method in each possible implementation of the aspect.

Optionally, there are one or more processors and one or more memories.

In a specific implementation process, the foregoing processor may be used to perform, for example, but not limited to, baseband related processing, and the receiver and transmitter may be used to perform, for example, but not limited to, radio frequency transceiving. The above-mentioned devices can be arranged on separate chips, or at least partly or completely on the same chip. For example, the receiver and transmitter can be arranged on separate receiver chips and transmitter chips. It can be integrated as a transceiver and then set on the transceiver chip. For another example, the processor can be further divided into an analog baseband processor and a digital baseband processor, where the analog baseband processor can be integrated with the transceiver on the same chip, and the digital baseband processor can be set on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be combined with a variety of application processors (such as but not limited to graphics processors, multimedia processors, etc.) Integrated on the same chip. Such a chip can be called a system on chip. Whether each device is independently arranged on different chips or integrated on one or more chips often depends on the specific needs of product design. The embodiment of the present application does not limit the specific implementation form of the foregoing device.

In a sixth aspect, a processor is provided, including: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the first aspect to the third aspect, or any one of the first aspect to the third aspect The method in each implementation in the.

In a specific implementation process, the foregoing processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits. The input signal received by the input circuit may be received and input by, for example, but not limited to, the receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by the transmitter, and the input circuit and output The circuit can be the same circuit, which is used as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.

In a seventh aspect, a processing device is provided, including a memory and a processor. The processor is configured to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute any of the first aspect to the third aspect, or the first aspect to the third aspect On the one hand, the methods in each implementation.

Optionally, there are one or more processors and one or more memories.

In the specific implementation process, the memory can be a non-transitory (non-transitory) memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be set in different On the chip, the embodiment of the present application does not limit the type of memory and the setting mode of the memory and the processor.

In an eighth aspect, a chip is provided, including a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program from the memory, the computer program is used to implement the first to third aspects Aspect, or the method in any one of the first aspect to the third aspect.

In a ninth aspect, a computer program product is provided. The computer program product includes: a computer program (also called code, or instruction), which when the computer program is executed, causes the computer to execute the first to third aspects. Aspect, or the method in any one of the first aspect to the third aspect.

In a tenth aspect, a computer-readable medium is provided, and the computer-readable medium stores a computer program (also called code, or instruction) when it runs on a computer, so that the computer executes the first to third aspects. Aspect, or the method in any one of the first aspect to the third aspect.

According to the solution provided in this application, early transmission of downlink data is realized. For example, the downlink data can be sent to the UE before Msg4 or Msg3, which saves excessive power overhead caused by sending downlink data and improves communication efficiency.

Description of the drawings

Fig. 1 is a schematic block diagram of a wireless communication system architecture applicable to an embodiment of the present application.

Fig. 2 is a schematic block diagram of another wireless communication system architecture applicable to an embodiment of the present application.

Fig. 3 is a schematic block diagram of another wireless communication system architecture applicable to an embodiment of the present application.

Figure 4 is a schematic flow chart of the process of establishing a connection between an access network device and a terminal device.

Fig. 5 is a schematic flowchart of suspending the context of a terminal device.

Figure 6 shows a schematic flowchart of a method for restoring an RRC connection.

Figure 7 shows a schematic flowchart of another method for restoring an RRC connection.

Figure 8 shows a schematic flow chart of a method for early data transmission under the UP scheme.

Figure 9 shows a schematic flowchart of a method for early data transmission under the CP scheme.

FIG. 10 is a schematic interaction diagram of an information transmission method according to an embodiment of the present application.

FIG. 11 is a schematic interaction diagram of an information transmission method according to another embodiment of the present application.

FIG. 12 is a schematic interaction diagram of an information transmission method according to some embodiments of the present application.

FIG. 13 is a schematic interaction diagram of an information transmission method according to some embodiments of the present application.

FIG. 14 is a schematic interaction diagram of a method for suspending the context of a terminal device according to some embodiments of the present application.

FIG. 15 is a schematic interaction diagram of the context of suspending a terminal device in some other embodiments of the present application.

FIG. 16 is a schematic interaction diagram of restoring the context of a terminal device in some embodiments of the present application.

FIG. 17 is a schematic block diagram of a communication device provided by an embodiment of this application.

FIG. 18 is another schematic block diagram of a communication device provided by an embodiment of this application.

FIG. 19 is a schematic block diagram of a communication device provided by an embodiment of the application.

FIG. 20 is another schematic block diagram of a communication device according to an embodiment of the application.

FIG. 21 is a schematic block diagram of a communication device provided by an embodiment of this application.

FIG. 22 is another schematic block diagram of a communication device according to an embodiment of the application.

FIG. 23 is a schematic block diagram of a terminal device according to an embodiment of the application.

FIG. 24 is a schematic block diagram of an access network device provided by an embodiment of this application.

detailed description

The technical solution in this application will be described below in conjunction with the drawings.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: global system for mobile communications (GSM) system, code division multiple access (CDMA) system, broadband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE Time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, the future fifth generation (5th generation, 5G) system or new radio (NR), etc.

The terminal equipment in the embodiments of this application may refer to user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, terminal, wireless Communication equipment, user agent or user device. The terminal device can also be a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (personal digital assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in the future 5G network, or future evolution of the public land mobile network (PLMN) Terminal equipment, etc., this embodiment of the application does not limit this.

The access network device in the embodiment of the application may be a device used to communicate with terminal devices, and the access network device may be a global system for mobile communications (GSM) system or code division multiple access (code division multiple) The base transceiver station (BTS) in access, CDMA) can also be the base station (NodeB, NB) in the wideband code division multiple access (WCDMA) system, or the evolution of the LTE system Evolved base station (evolved NodeB, eNB or eNodeB), can also be a wireless controller in the cloud radio access network (CRAN) scenario, or the access network device can be a relay station, access point, or vehicle-mounted device , Wearable devices and access network equipment in the future 5G network or access network equipment in the future evolved PLMN network, etc., which are not limited in the embodiment of the present application.

In the embodiment of the present application, the terminal device or the access network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory). The operating system may be any one or more computer operating systems that implement business processing through processes, for example, Linux operating system, Unix operating system, Android operating system, iOS operating system, or windows operating system. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. In addition, the embodiments of the application do not specifically limit the specific structure of the execution body of the method provided in the embodiments of the application, as long as the program that records the codes of the methods provided in the embodiments of the application can be provided according to the embodiments of the application. For example, the execution subject of the method provided in the embodiment of the present application may be a terminal device or an access network device, or a functional module in the terminal device or the access network device that can call and execute the program.

In addition, various aspects or features of the present application can be implemented as methods, devices, or products using standard programming and/or engineering techniques. The term "article of manufacture" used in this application encompasses a computer program that can be accessed from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (for example, hard disks, floppy disks, or tapes, etc.), optical disks (for example, compact discs (CD), digital versatile discs (DVD)) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). In addition, various storage media described herein may represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.

The following will briefly introduce the communication system applicable to the embodiment of the present application.

FIG. 1 is a schematic block diagram of a wireless communication system architecture 100 applicable to an embodiment of the present application. As shown in FIG. 1, the system architecture 100 includes a terminal device 110, an access network device 120, a core network device 130, and a data network 160 (DN). The core network device 130 includes a management device 140 and a gateway. Equipment 150. Among them, the terminal device 110 in FIG. 1 can be used to connect to the access network device 120 deployed by the operator through a wireless air interface, and then to the data network through the core network device 130; the access network device 120 is mainly used to implement the wireless physical layer Functions, resource scheduling and wireless resource management, wireless access control, and mobility management. The access network device may be the above-mentioned access network device; the core network device 130 may include a management device 140, a gateway device 150, and a management device 140 It is mainly used for device registration, security authentication, mobility management and location management of terminal devices. The gateway device 150 is mainly used for establishing a channel with the terminal device, and forwarding data packets between the terminal device and the external data network on the channel; The data network 160 may correspond to a variety of different service domains, such as IP multimedia subsystem (IMS), Internet (Internet), Internet protocol television (IPTV), and other operator service domains, etc. It is used to provide multiple data service services for terminal equipment, which may include network equipment such as servers (including servers that provide multicast services), routers, and gateways. Fig. 1 is only an exemplary architecture diagram. In addition to the functional units shown in Fig. 1, the network architecture may also include other functional units or functional entities, which are not limited in the embodiment of the present application.

When the communication network shown in Figure 1 is a 5G network, the aforementioned terminal devices can be user equipment (UE), such as mobile phones, computers, cellular phones, cordless phones, and session initiation protocols (SIP). ) Telephones, smart phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), computers, laptops, handheld communication devices, handheld computing devices, satellite wireless devices , Wireless modem card, TV set top box (STB), customer premise equipment (customer premise equipment, CPE) and/or other equipment used for communication on the wireless system. The aforementioned access network equipment may be an access network (AN)/radio access network (RAN) equipment, and a network composed of multiple 5G-AN/5G-RAN nodes. The 5G-AN/ 5G-RAN nodes can be: access point (access point, AP), next-generation base station (NR nodeB, gNB), central unit (CU) and distributed unit (DU) separated form gNB, Transmission receive point (TRP), transmission point (TP) or some other access node. The above-mentioned core network equipment may include: access and mobility management function (AMF), session management function (session management function, SMF), policy control function (PCF), user plane function (user plane funtion) , UPF) and other functional units, these functional units can work independently, can also be combined to achieve certain control functions, such as: AMF, SMF and PCF can be combined together as a management device to complete the access authentication of terminal equipment , Security encryption, location registration and other access control and mobility management functions, as well as session management functions such as the establishment, release and modification of user plane transmission paths, as well as analysis of some slice-related data (such as congestion) and terminal equipment related functions As a gateway device, UPF mainly completes the routing and forwarding of user plane data, such as: responsible for data message filtering, data transmission/forwarding, rate control, and charging information generation for terminal devices.

Figure 2 is a schematic diagram of another example of network architecture applicable to this application. In the 5G network architecture shown in Figure 2, each functional unit can establish a connection through a next generation network (NG) interface to achieve communication, such as : The terminal equipment establishes an air interface connection with the RAN equipment through the new radio (NR) interface to transmit user plane data and control plane signaling; the terminal equipment can establish control plane signaling with AMF through NG interface 1 (abbreviated as N1) Connection; AN/RAN equipment such as the next-generation radio access base station (NR NodeB, gNB) can establish a user plane data connection with UPF through NG interface 3 (abbreviated as N3); AN/RAN equipment can pass NG interface 2 (abbreviated as N2) Establish control plane signaling connection with AMF; UPF can establish control plane signaling connection with SMF through NG interface 4 (abbreviated as N4); UPF can exchange user plane data with data network through NG interface 6 (abbreviated as N6); AMF can use NG Interface 11 (abbreviated as N11) establishes a control plane signaling connection with SMF; SMF can establish a control plane signaling connection with PCF through NG interface 7 (abbreviated as N7). The air interface shown in FIG. 2 may also be referred to as 3GPP air interface.

It should be noted that the diagram shown in Figure 2 is only an exemplary architecture diagram. In addition to the functional units shown in Figure 2, the network architecture may also include other functional units or functional entities. For example, the core network equipment may also include unified Other functional units such as a data management function (unified data management, UDM) are not limited in this embodiment of the application.

When the communication network shown in Figure 1 is a 4G network, the terminal equipment can refer to the related description of the terminal equipment in Figure 2, which will not be repeated here; the access network equipment can be a base station (nodeB, NB), an evolved base station (evolution nodeB) , ENB), HeNB, TRP, TP, AP or some other access unit; core network equipment may include: mobility management entity (MME), policy and charging rules function (PCRF) ) And other management equipment, as well as gateway equipment such as serving gateway (serving gateway, S-GW), packet data network gateway (packet data network gateway, P-GW), and local gateway (local gateway, L-GW).

FIG. 3 shows a schematic diagram of another 4G network architecture applicable to the present application. In the 4G network architecture shown in Figure 3, the terminal equipment can establish an air interface connection with the eNB through the Uu interface, the eNB establishes a control plane signaling connection with the MME through the S1-C interface, and the eNB establishes a user with the S-GW through the S1-U interface For data connection, the S-GW establishes a control plane signaling connection with the MME through S11, the S-GW establishes a user plane data connection with the P-GW through the S5/S8 interface, and the P-GW and the data network are connected through the SGi interface. Each air interface shown in FIG. 3 may also be referred to as a 3GPP air interface.

It should be noted that FIG. 3 is only an exemplary architecture diagram. In addition to the functional units shown in FIG. 3, the network architecture may also include other functional units or functional entities, which are not limited in the embodiment of the present application.

Machine type communication (MTC) or (narrow band internet of things, NB-IoT) is different from traditional LTE communication. For example, for MTC, it does not pursue data transmission rates, multiple frequency bands, multiple antennas, and full dual Instead, it pursues longer battery time of terminal equipment and lower terminal equipment cost. That is, terminal equipment is required to achieve low power consumption and low cost. In addition, considering the application scenarios of MTC terminal equipment, such as water meters, electricity meters, etc., the signal coverage strength of terminal equipment cannot meet the signal reception requirements, so MTC is enhanced to enable access network equipment (such as base stations) and terminal equipment to support Expansion coverage (Coverage Enhancement). At present, the main method to achieve extended coverage is to repeatedly send uplink or downlink signals multiple times, and achieve the purpose of increasing the success rate of data reception through multiple reception combinations. Furthermore, in the application scenario of MTC or NB-IoT, the data transmission is characterized by a small amount of data, and the time of data arrival is uncertain. For example, the network side calls the terminal equipment to report data, or the network side issues control instructions to the terminal equipment. At present, in order to successfully transmit data, it is necessary to establish a wireless connection between the access network device and the terminal, and the establishment of the wireless connection requires certain signaling overhead. If it is only for the transmission of small data, it will make the use of wireless resources. The efficiency is reduced, a lot of resources are used for the process of connection establishment, and a small amount of resources are used for data transmission.

Figure 4 is a schematic flow chart of the process of establishing a connection between an access network device and a terminal device. When the access network equipment (take the base station as an example) has no downlink data transmission from the terminal equipment (take the UE as an example), no connection will be established between the base station and the UE, for example, no connection between the base station and the UE will be established Radio resource control (RRC) connection. At this time, the UE is in an IDLE state. When the base station side has UE downlink data to be transmitted, the base station needs to page the UE to establish an RRC connection, and the UE enters the connected state from the IDLE state, and the UE needs to establish the RRC connection through the process shown in FIG. 4.

Among them, steps A1 to A3 are the paging process triggered by downlink data. specific:

A1: When the S-GW on the core network side has the arrival of downlink data from the UE, the S-GW sends a downlink data notification message to the MME to notify the MME that the downlink data of a certain UE has arrived. The downlink data indication message contains Carry the UE's evolved packet system (evolved packet system, EPS) bearer identifier (EPS Bearer ID).

A2: After the MME receives the downlink data indication message sent by the S-GW, the MME sends a paging message (A2 paging) to the base station (taking the eNB as an example) to make the eNB page the UE.

A3: After receiving the paging message sent by the MME, the eNB sends the paging message in a broadcast form (A3 paging). The UE in the IDLE state will periodically monitor the Paging message sent by the eNB. When the UE monitors the paging message sent by the eNB and the paging message carries its own identity, the UE will trigger the RRC connection establishment process. Among them, step S101 to step S104 are the process of random access (Random Access) performed by the UE.

S101: The UE sends a random access preamble (Preamble) to an eNB. The sending of the random access preamble (Preamble) can be regarded as a process of sending message 1 (message 1, Msg1). The random access preamble is a message sent by the eNB through a broadcast Broadcast to all UEs, the UE that needs to initiate the random access process randomly selects a Preamble from the several Preambles broadcast by the eNB, and randomly selects a resource from the preamble broadcast resources of the eNB to send the UE to the eNB Preamble of choice.

S102. The eNB monitors the Preamble sent by the UE on the Preamble resource. When a certain Preamble is detected, the eNB confirms that the UE has sent the Preamble, and sends a random access response (RAR) message to the UE. The incoming response message can be regarded as Message 2 (Msg2). The RAR includes timing (advanced, TA) information for the UE to send Msg3, uplink resource (UL Grant) for the UE to send Msg3, and cell radio network temporary identifier (C-RNTI).

S103: After receiving the RAR sent by the eNB, the UE uses the TA and UL Grant included in the RAR to send Msg3 to the eNB. The Msg3 is an RRC connection establishment request message. The RRC connection establishment request message carries a UE identity (ID). The UE ID can be the system architecture evolution temporary mobile station identifier (S) of the UE. -TMSI) or International Mobile Subscriber Identification Number (IMSI).

S104, considering that in step S101, different UEs may randomly select the same Preamble code and resources for sending the Preamble. At this time, in the process from S101 to S102, the eNB does not know that different UEs use the same code and resources. In this way, the RRC connection establishment request message in S103 may actually be sent by multiple UEs using the same resources, but the UE ID in different RRC connection establishment request messages is different. In S104, in order to avoid subsequent data transmission If the conflict occurs, the eNB sends a contention resolution (Contention Resolution) message to the UE, which carries a UE ID. In this way, when one of these conflicting UEs detects that the UE ID is its own ID, the UE thinks that the eNB has accepted its connection establishment request, while other UEs think that the eNB does not have its own ID because it has not detected its own ID. Accept their connection establishment request, wait for a certain time, and then send the Preamble. In S104, the eNB may also send an RRC Connection Setup (RRC Connection Setup) message to the UE, and the RRC Connection Setup message may be regarded as Msg4. So far, the random access process of the UE is completed.

S105: The UE sends an RRC Connection Setup Complete (RRC Connection Setup Complete) message to the eNB, and carries a non-access stratum (Non-Access Stream, NAS) service request (service request) message.

In S106 to S107, the eNB requests the MME to initialize the UE message (initial UE message) through the S1-AP interface. The message may include the NAS message, the tracking area identity (TAI), and the E-UTRAN cell global identifier (E-UTRAN). -UTRAN cell global identifier, ECGI), S-TMSI, RRC establishment reason (Cause). The NAS message may carry a service request (service request). The S1-AP interface is the communication interface between the eNB and the MME. Specifically, in S106, the UE sends a service request to the MME, and in S107, the MME sends an initial context setup request (initial context setup request) to the eNB.

In S108 to S109, the eNB sets the security context to the UE. Specifically, in S108, the eNB sends a security mode command (security mode command) to the UE. In S108, the UE sends a security mode complete (security mode complete) to the eNB.

In S110 to S111, the eNB configures the bearer of the UE for transmitting signaling and data. Specifically, in S110, the eNB sends an RRC connection reconfiguration (RRC connection reconfiguration) to the UE. In S111, the UE sends an RRC connection reconfiguration complete (RRC connection reconfiguration complete) to the eNB.

In S112 to S114, it is the process of establishing or modifying the bearer on the core network side for the UE. Specifically, in S112, the eNB sends an initial context setup complete to the MME. In S113, the MME sends a modify bearer request to the S-GW. In S114, the S-GW sends a modified bearer request to the MME. Response (modify bearer response).

In S115 to S116, the S-GW sends downlink data to the UE through the eNB. Specifically, in S115, the S-GW sends downlink data (DL data) to the eNB, and in S116, the eNB sends the downlink data to the UE.

It can be seen that when the network side has the UE's downlink data, it needs to go through a very complicated connection establishment process. When the network side only has smaller data packets of the UE, the above process will undoubtedly increase the burden on the system and reduce the utilization of resources. effectiveness.

The UE is in the RRC idle state (IDLE state) before establishing the RRC connection, and is in the RRC connected state (RRC connected) after the RRC connection is established. When the UE transitions from the RRC connected state to the RRC idle state, the UE releases the configuration information configured by the eNB to the UE (For example, including the UE context, etc.), the eNB releases the context of the UE. The context of the UE may include the identity of the UE, resource configuration information configured for the UE, encryption algorithm, and capability information of the UE.

In order to reduce the complicated signaling interaction overhead in the RRC connection establishment process, currently, a suspend and resume solution is introduced into the RRC connection establishment process. The specific process is shown in Figure 5 and Figure 6.

Figure 5 is a schematic flow chart of the context of suspending a UE.

As shown in Figure 5, when the eNB determines that the UE has no uplink and downlink data, in S201, the eNB decides to suspend the context of the UE. Suspending the context of the UE can be understood as the eNB releasing the RRC connection with the UE, but the eNB does not release the context of the UE.

In S202, the eNB requests the MME to suspend the UE (Suspend). Specifically, the eNB sends a UE context suspend request (UE context suspend request) to the MME, requesting to release the RRC connection with the UE, but the eNB does not release the UE’s Context.

In S203, the MME and the S-GW interact to release access bearers (release access bearers) information.

In S204, the MME sends a UE context suspend response (UE context suspend response) to the eNB. When the eNB receives a positive response from the MME, the eNB is allowed to suspend the UE.

In S205, the eNB sends an RRC connection release (RRC connection Release) message to the UE, and instructs the UE to suspend in the message. At this time, the eNB releases the RRC connection with the UE, but the eNB does not release the UE context. The RRC connection release message carries a resume ID, and the resume ID is used to identify the context of the UE, and the context of the UE can be obtained according to the resume ID.

In S206, the UE releases the RRC connection of the UE according to the RRC connection release message, and saves the context of the UE. Specifically, the UE saves the context (suspends the context of the UE), suspends the signaling radio bearer (SRB) and data radio bearer (DRB) with the eNB, and the UE enters RRC idle state.

When there is downlink data for the UE on the network side, after the eNB initiates a paging to the UE, the UE requests to restore the RRC connection. Figure 6 shows a schematic flowchart for restoring the RRC connection. As shown in Figure 6:

Steps A1 to A3 are the paging process triggered by the downlink data. It is the same as that shown in FIG. 4, and the specific description can refer to the description of steps A1 to A3 in FIG. 4. For the sake of brevity, details are not repeated here.

Steps S301 and S302 are the same as steps S101 and S102 shown in FIG. 4. For specific descriptions, reference may be made to the description of steps S101 and S102 in FIG. 4. For brevity, details are not repeated here.

S303: The UE sends an RRC connection resume request (RRC connection Resume Request) to the eNB, and the RRC connection resume request can be regarded as Msg3. The RRC connection recovery request is used to request the eNB to recover the RRC connection. The RRC connection recovery request carries a Resume ID, a resume cause, and a truncated message authentication code (short resume message authentication code of integrity, short Resume MAC-I) used for integrity protection of the RRC connection recovery process.

Among them, the Resume ID is used to identify the context of the suspended UE;

Resume Cause is used to indicate the reason for the UE to resume the connection, including emergency call (emergency), high priority access (high Priority Access), called (mt-Access), calling signaling (mo-Signalling), calling data (mo-Data), delay tolerance access (delayTolerant Access), calling voice (mo-Voice Call), etc.

Short Resume MAC-I is used to protect the integrity of Msg3 (RRC connection Resume Request) to prevent Msg3 from being tampered with.

S304. The eNB sends an RRC connection Resume (RRC connection Resume) message to the UE to restore the context of the UE, which carries the next hop chaining count (NCC) and measurement configuration (measConfig) used to derive the security key. ), dedicated radio resource configuration (radioResourceConfigDedicated), etc.

S305: The UE receives the RRC connection recovery message and restores the context of the UE. Specifically, it includes the recovery of SRB and DRB bearers, and the recovery of access stream (AS) layer security context. Then the UE enters the RRC connected state.

S306: The UE sends an RRC Connection Resume Complete (RRC Connection Resume Complete) message to the eNB to notify the eNB that the UE has resumed the RRC connection.

S307: The eNB requests the MME to restore the UE context.

S308, the MME and the S-GW exchange bearer modification messages.

S309: The MME sends a recovery response message to the eNB.

After that, the S-GW can send the downlink data to the eNB, and then the eNB to the UE. The UE may also send uplink data to the S-GW through the eNB.

Wherein, steps S307 to S309 shown in FIG. 6 are the same as the steps shown in S110 to S114 shown in FIG. 4, and the specific description can refer to the description of S110 to S114 in FIG. 4. For brevity, the details are not repeated here.

When the UE does not send uplink data or receive downlink data, it enters the RRC idle state through a release process (for example, the suspension process shown in FIG. 5).

In the foregoing S303, when the eNB that the UE sends the RRC connection Resume Request (RRC connection Resume Request) is not the eNB that suspends the UE, that is, the eNB shown in FIG. 5 and the eNB shown in FIG. 6 are not the same eNB. For example, when the UE moves from the eNB (denoted by old eNB) shown in FIG. 5 to the cell of the eNB (denoted by new eNB) shown in FIG. 6, it can follow the schematic diagram of restoring the RRC connection shown in FIG. The flowchart restores the RRC connection. In Figure 7, the old base station (old eNB) is the eNB that suspends the UE context, and the new base station (new eNB) is the base station that the UE requests to resume the RRC connection. As shown in Figure 7, the method includes:

Steps A1 to A3 are the paging process triggered by the downlink data. It is the same as the corresponding steps shown in FIG. 4, and the specific description can refer to the description of steps A1 to A3 in FIG. 4. For brevity, details are not repeated here.

Steps S401 and S402 are the same as steps S101 and S102 shown in FIG. 4, except that the interaction with the eNB is all new eNB. For a specific description, reference may be made to the description of steps S101 and S102 in FIG. 4. For brevity, details are not repeated here.

S403: The UE sends an RRC connection resume request (RRC connection Resume Request) to the new eNB, and the RRC connection resume request can be regarded as msg3. The RRC connection recovery request is used to request the new eNB to resume the RRC connection. The RRC connection recovery request carries a Resume ID, a resume cause, and a truncated message authentication code (short resume message authentication code of integrity, short Resume MAC-I) used for integrity protection of the RRC connection recovery process.

S404: The new eNB sends a Retrieve UE context request (Retrieve UE context request) to the old eNB through the X2-AP interface to request the UE context, which carries the resume ID, and X2-AP is the communication interface between the base station and the base station.

S405: The old eNB sends a UE context recovery response (Retrieve UE context response) to the new eNB through the X2-AP interface, which carries the UE context. The old eNB can obtain the UE context through the resume ID.

S406: The new eNB sends an RRC connection recovery message to the UE for recovering the context of the UE, which carries the NCC used to derive the security key.

S407: After the UE receives the RRC connection recovery message, it recovers the context of the UE, including the recovery of SRB and DRB bearers, and the establishment of AS layer security context. Then the UE enters the RRC connected state.

S408: The UE sends an RRC Connection Resume Complete message to the new eNB to notify the new eNB that the RRC connection has been restored.

S409: The new eNB requests a path switch (path switch) from the MME.

S410: The MME and the S-GW exchange a bearer modification message.

S411: The MME sends a path switch response message to the new eNB.

S412: The new eNB instructs the old eNB to release the UE context.

After that, the S-GW can send the downlink data to the new eNB, and send it to the UE through the new eNB. The UE may also send uplink data to the S-GW through the new eNB.

In each of the above procedures, the downlink data is transmitted through the S-GW->eNB->UE process, and this data transmission method is called a user plane (UP) solution (UP Solution). Another solution corresponding to this is the control plane (CP) solution (CP Solution). The downlink data of the CP solution is transmitted through the S-GW->MME->eNB->UE process, which is transmitted in the RRC Connection The Setup Complete message can carry uplink data. After this message, the eNB can use a downlink information transmission (DL Information Tranfer) to carry downlink data to the UE. If there is no data afterwards, the UE context is released through the release procedure. For the CP scheme, the downlink data is forwarded through the MME, the messages exchanged between the UE and the MME can be called NAS messages, the downlink data is exchanged with the UE through the NAS messages, and the downlink data is transmitted at the NAS layer during the NAS layer transmission. Encryption, so no security context at the AS layer is required.

In order to transmit small uplink data packets while reducing signaling overhead, currently, an early data transmission (EDT) method is also proposed. The improvement is mainly based on the process of restoring the RRC connection shown in FIG. 6 or FIG. 7. Specifically, it is mainly that the uplink data can be carried in Msg3, and the uplink data can be sent to the eNB together with the RRC connection Resume Request.

In MTC, when Msg3 does not carry uplink data, the size of the media access control protocol data unit (MAC PDU) corresponding to Msg3 is 56 bits (bits). In NB-IoT, it is 88bits. If it wants to send uplink data when sending Msg3, the UE needs to request more time-frequency resources to send additional uplink data. Since the resource for sending Msg3 is indicated by the UL grant in the RAR sent by the eNB, in order to obtain more resources in the RAR, the UE needs to indicate to the eNB that the UE will send uplink data in Msg3. Specifically, as shown in FIG. 8, FIG. 8 is a schematic method flowchart of the data early transmission method under the UP scheme, and the method includes:

S501: The UE sends a random access preamble (Preamble) to the eNB, where the random access preamble is used to indicate to the eNB that the UE will send uplink data at Msg3. The random access preamble is broadcasted by the eNB to all UEs through a broadcast message. The UE that needs to initiate the random access process is broadcast from the eNB to indicate that a preamble is randomly selected among the several preambles used by Msg3 to send uplink data. Among the resources for sending the Preamble broadcast by the eNB, a resource is randomly selected to send the Preamble selected by the UE to the eNB. Alternatively, the time-frequency resource for sending the Preamble broadcast by the eNB is used to indicate the time-frequency resource for sending uplink data in Msg3, and the UE selects this resource to send the Preamble.

S502: When the eNB detects a certain Preamble used to indicate the sending of uplink data on Msg3, or when the eNB indicates to detect a certain Preamble on the random access time-frequency resource for sending uplink data on Msg3, the eNB confirms that the UE has sent it. Preamble and indicates to send uplink data in Msg3, then the eNB sends RAR to the UE, which is the process of sending Msg2. The RAR contains the TA and UL Grant for the UE to send Msg3. UL Grant indicates a larger TBS, for example, it can transmit MAC PDUs of less than 1000 bits.

S503: After the UE receives the RAR sent by the eNB, it uses the corresponding TA and UL Grant to send the Msg3 to the eNB, which includes the RRC message and uplink data. The RRC message is an RRC connection Resume Request (RRC connection Resume Request). The RRC connection establishment request message carries the Resume ID, the resume cause (resume cause), and the short Resume MAC-I. The RRC message is carried on a common control channel (CCCH), and uplink data is carried on a dedicated traffic channel (DTCH). The MAC SDUs on the two channels are multiplexed at the MAC layer to form a MAC PDU. In addition, the uplink data needs to be encrypted with a key, which is derived by an NCC, and the NCC can be carried in the RRC connection release (RRC connection Release) message previously sent by the eNB to the UE.

S504: The eNB requests the MME to resume the context of the UE (UE Context Resume Request).

S505: The MME and the S-GW exchange a bearer modification message.

S506: The MME sends a resume response message (UE Context Resume Response) to the eNB.

S507: After receiving the response message sent by the MME, the eNB sends uplink data to the S-GW.

S508: If the S-GW has downlink data that needs to be sent to the UE, the downlink data can be sent to the eNB.

S509: After the eNB finishes sending the uplink data to the S-GW, if it does not receive the downlink data, it requests the MME to suspend the context of the UE. If downlink data is received, it also requests the MME to suspend the UE context. In addition, the MME and the S-GW exchange bearer modification messages.

S510: The eNB sends an RRC Connection Release message to the UE, the message is carried on a dedicated control channel (dedicated control channel, DCCH), and the message carries a release cause, resume ID, and NCC. If the eNB has UE downlink data, which is carried on the DTCH, the eNB multiplexes the downlink data with the RRC Connection Release message, that is, sends the downlink data together with the RRC Connection Release message to the UE.

It should be understood that in the process shown in FIG. 8, the UE is always in the IDLE state and has not entered the RRC connected state. After the data packet is transmitted between the UE and the eNB, the eNB can suspend the context of the UE.

Figure 8 shows the main flow of the UP scheme. The main flow of the CP scheme’s early data transmission will be described below in conjunction with Figure 9. As shown in Figure 9,

S601 and S602 are the same as the above-mentioned steps S501 and S502. For specific descriptions, reference may be made to the description of S501 and S502 in FIG. 8. For the sake of brevity, details are not repeated here.

S603: The UE sends an RRC Early Data Request (RRC Early Data Request) to the eNB, which carries the S-TMSI, the establishment cause, and the dedicated Info NAS (dedicated Info NAS). S-TMSI is used to identify the UE, establishment Cause is used to indicate the reason for initiating the request, dedicated Info NAS is used to carry NAS messages, which carry uplink data, that is, the uplink data sent by the UE is encapsulated in the form of NAS messages at the NAS layer , Do not use security protection at the AS layer, just use the NAS layer security. Therefore, there is no issue of NCC and AS security keys in the CP scheme.

S604: The eNB sends an Initial UE message (Initial UE message) to the MME, which carries non-access stratum information (NAS message) including uplink data.

S605: The MME and the S-GW exchange bearer modification.

S606: The MME sends uplink data to the S-GW.

S607: If the S-GW has downlink data, the S-GW sends the downlink data to the MME.

S608: If the S-GW has downlink data to send to the MME, the MME sends a NAS message containing the downlink data to the eNB. Optionally, the MME may indicate the size of the downlink data to the eNB.

S609: If there is no downlink data or the downlink data is small, the eNB triggers a connection release procedure, and the MME and the S-GW exchange a bearer modification message.

S610: The eNB sends an RRC Early Data Complete (RRC Early Data Complete) message to the UE, which may carry a NAS message, and the NAS message carries downlink data.

It should be understood that in the process shown in FIG. 9, the UE is always in the IDLE state and has not entered the RRC connected state. After the data packet is transmitted between the UE and the eNB, the eNB will release the UE.

It can be seen from the above description that in the current UP scheme for early transmission of uplink data, the eNB sends downlink data to the UE after Msg3. The eNB will obtain the resume ID through Msg3, obtain the UE context through the Resume ID, and use the UE context The security information in encrypts the downstream data. Then send the encrypted downlink data to the UE. For the scenario of small downlink data, for example, the core network side has the downlink data of the terminal equipment arriving, and the data volume of the downlink data is small. In this case, the uplink data can be used to transmit early after Msg3. For example, the access network equipment uses Msg4 to transfer The downlink data is sent to the terminal equipment. Obviously, starting from the terminal device receiving the paging message, the terminal device needs to go through Msg1, Msg2, and Msg3 before it can receive the downlink data sent by the eNB. For the transmission of small data volume downlink packets, the transmission efficiency is still not high. If the downlink data is sent before Msg3, in the UP scheme, because the eNB does not have a resume ID, the context of the UE cannot be obtained, and the downlink data cannot be secured, and the eNB lacks the context of the UE (such as the configuration of the access layer AS, etc. ) Unable to perform data transmission on the air interface, which will seriously affect the security and reliability of downlink data transmission, seriously affect the efficiency of data transmission, and reduce communication quality.

Based on the above problems, this application provides a method for information transmission. The eNB notifies the core network device of the relevant information about the context of the suspended UE, so that when the core network device has downlink data from the UE, the core network device can Notify the eNB of the relevant information about the context of the UE, so that when the eNB receives the downlink data, the eNB can obtain the context of the UE according to the relevant information of the context, and then send the downlink data according to the context of the UE To the UE. The embodiment of this application realizes early transmission of downlink data. For example, the downlink data can be sent to the UE before Msg4 or Msg3, which saves excessive power overhead caused by sending downlink data and improves communication efficiency.

The information transmission method provided by this application will be described in detail below with reference to FIG. 10. FIG. 10 is a schematic interaction diagram of an information transmission method 700 according to an embodiment of this application. The method 700 can be applied to the scenarios shown in FIGS. 1 to 9 Of course, it can also be applied in other communication scenarios, and the embodiments of the present application are not limited herein.

It should be understood that, in the embodiments of the present application, the terminal device, the first access network device, and the core network device are used as an example to execute the execution methods of the respective embodiments to describe the methods of the respective embodiments. The first access network device may be the aforementioned access network device, for example, it may be an eNB, a gNB, or the like. The core network equipment may be S-GW, or MME, or SMF, or AMF or UPF, and so on. The terminal device may be the above-mentioned terminal device, for example, UE. The embodiments of the application are not limited here. As an example and not a limitation, the execution subject of the execution method may also be a chip applied to the terminal device and a chip applied to the first access network device and the core network device.

As shown in FIG. 10, the method 700 shown in FIG. 10 may include step S710 to step S740. The steps in the method 700 are described in detail below with reference to FIG. 10.

S710: The core network device determines the first information. The first information is used by the first access network device to determine the context of the terminal device, or the first information is used to identify the context of the terminal device. The context may be used by the first access network device to send downlink data to the terminal device. Optionally, the context is suspended or deactivated.

S720. The core network device sends the first information to the first access network device.

Correspondingly, the first access network device receives the first information from the core network device.

S730. The first access network device determines the context according to the first information.

S740: The first access network device sends the downlink data to the terminal device according to the context.

Correspondingly, the terminal device receives the downlink data.

Specifically, in step S710, the core network device determines first information, and the first information is used by the first access network device to determine the context (UE context) of the terminal device, and the context is used for the first access network. The device sends downlink data to the terminal device. The context of the terminal device may include the resource configuration information, encryption algorithm, key, and capability information of the terminal device of the terminal device. Among them, the context of the terminal device is suspended or inactive. That is, the first access network device releases the RRC connection with the terminal device, but does not release the context of the terminal device. The first access network device and the terminal device are in an RRC idle state or an RRC inactive state, but both the first access network device and the terminal device save the context of the terminal device. When the first access network device sends downlink data to the terminal device, it can use the context to send downlink data to the terminal device.

When the core network device has downlink data of the terminal device, in S720, the core network device sends the first information to the first access network device. Correspondingly, the first access network device receives the first information from the core network device.

Optionally, after the first access network device receives the first information, the first access network device may send a UE context recovery request to the core network device for requesting to restore the context of the terminal device. After receiving the UE context recovery request, the UE context recovery response may be sent to the first access network device to instruct the first access network device to recover the UE context.

In step S730, the first access network device may determine (restore) the context according to the first information (or the restore UE context response sent by the core network device). Since the context is suspended, determining the context can be understood as restoring or activating the context, and the context is in a state that can be used after restoration or activation. After the context is suspended, the context is only stored and cannot be used when sending downlink data.

Optionally, the method 700 may further include: the core network device sending downlink data to the first access network device.

In step S740, the first access network device may send the downlink data to the terminal device according to the context when receiving the downlink data of the terminal device sent by the core network device according to the context. For example, the first access network device may determine the time-frequency resource and transmission power for sending the downlink data, coding mode, configuration of the access layer AS, and air interface for sending the downlink data according to the context. The first access network device sends the downlink data to the terminal device according to the context, reducing terminal power consumption overhead caused by sending the downlink data, and improving the efficiency and reliability of downlink data sending.

Optionally, step S710 and/or step S730 in the method 700 may be optional steps.

In the information transmission method provided in this application, the core network device notifies the first access network device of the first information used for the first access network device to determine the context of the terminal device. Among them, the context of the terminal device has been suspended. The first access network device may determine (restore or activate) the context of the terminal device according to the first information, so that when receiving downlink data sent by the core network device, it may send the downlink data to the terminal device according to the context. The downlink data can be sent to the terminal device earlier. For example, the downlink data can be sent to the terminal device before Msg4 or Msg3, which reduces the power consumption overhead of the terminal receiving downlink data and improves the efficiency and reliability of downlink data transmission. Improve communication efficiency.

As shown in FIG. 11, FIG. 11 is a schematic interaction diagram of an information transmission method in some embodiments of the present application. In some embodiments, the context includes a security context. In step S740 of the method shown in FIG. 10: the first access network device sending the downlink data to the terminal device according to the context includes:

S741: The first access network device encrypts and/or integrity protects the downlink data according to the security context.

S742: The first access network device sends the encrypted and/or integrity-protected downlink data to the terminal device.

Specifically, for the description of steps S710 to S730 shown in FIG. 11, reference may be made to the description of steps S710 to S730 in FIG. 10, which is not repeated here for brevity.

The context of the terminal device includes a security context. The security context is mainly used by the first access network device to encrypt and/or integrity protect the downlink data that needs to be sent to the terminal device, to ensure the security and integrity of the downlink data transmission Sex. The aforementioned step S740 may further include steps S741 and S742. In step S741, the first access network device encrypts and/or integrity protects the downlink data according to the security context. For example, the key K _UPint in the security context can be used to protect the integrity of the downlink data, the NCC in the security context can be used to determine or derive a new security key, and the new security key can be used to encrypt the downlink data. For example, use NCC to derive K _eNB , and then _derive K _RRCint , K _UPint , K _RRCenc , and K _UPenc based on K _eNB , and use K _UPenc to encrypt the downlink data, instead of using the key K _UPint in the security context to _perform downlink data. The method of integrity protection, the downlink data can be integrity protected using the K _{UPint deduced} above. In step S742, the first access network device may send the encrypted and/or integrity-protected downlink data to the terminal device. In this implementation, the downlink data is encrypted and/or integrity protected by using the security context, and then the encrypted and/or integrity protected downlink data is sent to the terminal device, which can improve the security and reliability of downlink data transmission It further improves the guarantee of downlink data transmission.

In some embodiments of the present application, after the core network device sends the downlink data to the first access network device, the first access network device may send the downlink data to the terminal device according to the context. Optionally, the first access network device may send the downlink data to the terminal device in the following four ways.

The first type: the first access network device may send a paging message to the terminal device, and the paging message includes the downlink data. The paging message may be A3 paging in the process shown in FIG. 4. A paging message (Uu paging) sent by the first access network device to the terminal device through the Uu interface, and the paging message carries the downlink data. Optionally, the paging message further includes second indication information, and the second indication information is used to instruct the terminal device to restore or activate the context. Restoring or activating the context may include SRB, DRB bearer restoration, and AS layer security context establishment. After the terminal device restores the context, the downlink data can be received according to the context, for example, the security information in the context can be used to decrypt the downlink data. The paging message is equivalent to the second information received by the terminal device from the first access network device. In this implementation manner, by carrying the downlink data in the paging message and sending it to the terminal device together, the signaling overhead can be reduced and the resource utilization efficiency can be improved.

The second type: the first access network device can send downlink data to the terminal device at the paging occasion (Paging Occasion, PO) when sending a paging message to the terminal device, for example, send scheduling information at the PO, and the scheduling information is used for scheduling Downlink data. In a possible implementation manner, the first access network device does not send a paging message (Uu paging) to the terminal device, but instead sends scheduling information to the terminal device when the paging message is sent. The scheduling information is used To instruct the terminal equipment to receive the downlink data, optionally, the scheduling information may include the time-frequency resource location of the downlink data and related transmission parameters. Optionally, the scheduling information further includes second indication information, and the second indication information is used to instruct the terminal device to restore or activate the context. Restoring or activating the context may include SRB, DRB bearer restoration, and AS layer security context establishment. The scheduling information is equivalent to the second information received by the terminal device from the first access network device. After the terminal device restores the context, the terminal device receives the downlink data according to the context. For example, the security information in the context can be used to decrypt the downlink data. After the first access network device sends the scheduling information to the terminal device, the first access network device may send the downlink data to the terminal device according to the context. Correspondingly, the terminal device receives the downlink data, and further, can use the security information in the context to decrypt the downlink data.

The third type: the first access network device sends a paging message (Uu paging) to the terminal device. The paging message includes scheduling information. The scheduling information is used to schedule downlink data. For example, the scheduling information is used to instruct the terminal device to receive The downlink data, optionally, the scheduling information may include the time-frequency resource location of the downlink data and related transmission parameters. Optionally, the paging message further includes second indication information, and the second indication information is used to instruct the terminal device to restore or activate the context. The paging message is equivalent to the second information received by the terminal device from the first access network device. After the first access network device sends the paging message to the terminal device, the first access network device can send the downlink data to the terminal device according to the context. Correspondingly, the terminal device receives the downlink data, and further, can use the security information in the context to decrypt the downlink data.

The fourth type: the first access network device sends a paging message (Uu paging) to the terminal device, the paging message includes the configuration information of the first resource, and the first resource is used by the terminal device to send a paging message to the first access network device. Send a downlink data request. For example, the first resource may be PRACH time-frequency resource and/or Preamble resource. The downlink data request may be an implicit indication. For example, the terminal device indicates the downlink data request by sending a Preamble to the first access network device. Optionally, the paging message further includes second indication information, and the second indication information is used to instruct the terminal device to restore or activate the context. The paging message is equivalent to the second information received by the terminal device from the first access network device. The second indication information may be an implicit indication. For example, if the paging message includes the configuration information of the first resource, it implicitly instructs the terminal device to restore or activate the context. Then, when the terminal device receives the paging message, if the paging message contains the configuration information of the first resource, the terminal device sends a downlink data request to the first access network device. At the same time, the terminal device restores or activates the context. The first access network device sends downlink data to the terminal device according to the received downlink data request.

In some embodiments of the present application, the second information sent by the first access network device to the terminal device may be the paging message, and the paging message also includes scheduling information, and the scheduling information is used to schedule the downlink data, or, The second information may be scheduling information, and the scheduling information is used to schedule the downlink data. The second information includes second indication information, and the second indication information is used to instruct the terminal device to restore the context of the terminal device.

It should be understood that the above four methods are only exemplary and should not cause any limitation to the embodiments of the present application. The first access network device may also use other methods to send the downlink data to the terminal device. For example, the first access network device may first send a paging message to the terminal device, and the paging message is also used to instruct the terminal device to restore or activate the context. Then the first access network device may send scheduling information to the terminal device, where the scheduling information is used to schedule the downlink data. Finally, the first access network device can send the downlink data to the terminal device. The embodiments of the application are not limited here.

Optionally, in some embodiments of the present application, the first information includes:

The first identifier of the terminal device and the context, where the first identifier is allocated by the core network device; or,

The first information includes a second identifier of the terminal device, the second identifier is allocated by the first access network device, and the second identifier is used to identify the context; or,

The first information includes the second identifier of the terminal device and the context.

Specifically, the first information is used by the first access network device to determine the context of the terminal device. In some possible implementation manners, the first information includes the first identifier of the terminal device and the context. The first identifier of the terminal device may be the S-TMSI or IMSI of the terminal device. S-TMSI is an ID assigned by the core network device to identify the terminal device. The IMSI is stored in the subscriber identity module (SIM) card of the terminal device. The context belongs to the terminal device, and the context corresponds to the first identifier. According to the first identifier, the first access network device can determine the terminal device, and the first access network device may be the access network device that suspends the context , Or it may not be the access network device that suspends the context. When the first access network device is the access network device that suspends the context, the first access network device itself stores the context. When the first access network device is not the access network device that suspends the context, the first access network device itself does not store the context.

When the first information includes the first identifier of the terminal device and the context, regardless of whether the first access network device is an access network device that suspends the context, the context can be obtained or determined according to the first information.

When the first information includes the second identifier of the terminal device, the second identifier is allocated by the first access network device, and the second identifier is used to identify the context. For example, the second identifier may be a resume ID. When the first access network device is the access network device that suspends the context, the first access network device itself stores the context. The first access network device may obtain the context according to the second identifier. When the first access network device is not the access network device that suspends the context, the first access network device itself does not store the context. The first access network device can use the resume ID to request the context from the access network device that has suspended the context, and the first access network device can obtain the context from the access network device that has suspended the context.

In the embodiments of the present application, suspending or resuming the context may also be referred to as suspending or resuming the RRC connection of the terminal device.

When the first information includes the second identifier of the terminal device and the context, regardless of whether the first access network device is the access network device that suspends the context, the context can be obtained or determined according to the first information .

It should be understood that the above-mentioned content included in the first information should not limit the content included in the first information. For example, the first information may also include other content used by the first access network device to determine the context. For example, the first information may also include the first identifier, the second identifier, and the context. The embodiments of the application are not limited here.

Optionally, in some embodiments of the present application, the first information further includes first indication information, and the first indication information is used to indicate that the downlink data will trigger the terminal device to send uplink data, and the downlink data will not trigger The terminal device sends uplink data, and the downlink data only includes at least one of a data packet.

Specifically, when the core network device has downlink data of the terminal device that needs to be transmitted, the core network device sends the first information to the first access network device. Further, the first information may also include the first indication information, which is used to indicate that the downlink data will trigger the terminal device to send uplink data, the downlink data will not trigger the terminal device to send uplink data, the The downlink data only includes at least one of a data packet. For example, the first indication information may indicate one or more of the following four types of information:

a) The downlink data has only one data packet;

b) The size of the downstream data packet (size) is less than a threshold;

c) The downlink data packet will not trigger the uplink data;

d) The downlink data packet will trigger the uplink data.

The downlink data including only one data packet can be regarded as the data volume of the downlink data. The first indication information may also be used to indicate the data amount of the downlink data, and the data amount may be the size of the downlink data, for example, the number of data packets included in the downlink data, the size of each data packet, and the like. In this application, there is no restriction on the specific representation form of the data volume of the downlink data.

The core network device notifies the first access network device by carrying relevant information about the downlink data in the first information, so that the first access network device obtains information about the downlink data and obtains the information of the terminal device according to the first information. Context, in order to realize the early transmission of downlink data, and improve the efficiency of the downlink data transmission.

As shown in FIG. 12, FIG. 12 is a schematic interaction diagram of an information transmission method in some embodiments of the present application. In some embodiments, before step S710 of the method shown in FIG. 10, the method 700 includes:

S705. The first access network device sends a first request to the core network device, where the first request is used to request to suspend or deactivate the context, the first request includes third information, and the third information is used for the first request. An access network device determines the context of the terminal device; correspondingly, the core network device receives the first request.

S706: The core network device sends a first response message in response to the first request to the first access network device, where the first response message is used to instruct the first access network device to suspend or deactivate the context. Correspondingly, the first access network device receives a first response message in response to the first request from the core network device.

S707: The first access network device suspends or deactivates the context of the terminal device according to the first response message.

S708. The first access network device sends third instruction information to the terminal device, where the third instruction information is used to instruct to suspend or deactivate the context of the terminal device. Accordingly, the terminal device receives from the first terminal device. The network access device receives the third indication information.

S709: The terminal device suspends or deactivates the context of the terminal device according to the third indication information.

Specifically, for the description of steps S710 to S740 shown in FIG. 12, reference may be made to the description of steps S710 to S740 in FIG. 10 and FIG. 11. For brevity, details are not repeated here.

As shown in Figure 12, in S705, the first access network device decides to suspend the context of the terminal. For example, when the first access network device determines that the terminal device has no uplink and downlink data, the first access network device decides Suspend the context of this terminal. Suspending the context of the terminal can be understood as the first access network device releasing the RRC connection with the terminal device, and the first access network device saves the context. The first access network device sends a first request to the core network device, the first request is used to request suspension or deactivation of the context, the first request includes third information, and the third information is used for the first access The network device determines the context of the terminal device. The third information may include the first identifier and the context, or the third information may include the second identifier of the terminal device and the context, or the third information may include the second identifier of the terminal device. It should be understood that the foregoing first information may include the third information. Alternatively, the aforementioned first information may be the same as the third information, that is, the content included in the first information and the content included in the third information are the same. Alternatively, the third information may include the aforementioned first information.

The first request may be the UE context suspend request. In step S706, after the core network device receives the first request, the core network device may send a first response message in response to the first request to the first access network device, where the first response message is used to indicate The first access network device suspends or deactivates the context. The first response message may be a UE context suspend response message. In step S707, the first access network device suspends or deactivates the context of the terminal device according to the first response message. For example, the first access network device releases the RRC connection with the terminal device, but does not release the context. After the first access network device suspends the context, in step S708, the first access network device sends third instruction information to the terminal device, where the third instruction information is used to instruct to suspend or deactivate the terminal device Of that context. The third indication information may be RRC Connection Release, or the third indication information may be the suspend indication in release cause in the RRC Connection Release message, or the third indication information may include the above-mentioned first information and instructions for the terminal device The indication information of suspending the context, or the third indication information includes the above suspend indication and the Resume ID. After the terminal device receives the third instruction information, in step S709, the terminal device suspends or deactivates the context of the terminal device according to the third instruction information. Specifically, the terminal device releases the RRC connection with the first access network device, saves the context, and suspends the signaling radio bearer SRB and data radio bearer DRB with the first access network device.

Optionally, after the context of the terminal device is suspended, when the core network device has the terminal device’s downlink data to send, the core network device may perform the above steps S710 and S720, and the first access network device may perform The above steps S730 and S740 realize the transmission of downlink data.

It should be understood that the aforementioned steps S705 to S709 are steps of suspending or deactivating the context. The process of suspending or deactivating the context can be performed before step S710.

Optionally, in some embodiments of the present application, as shown in FIG. 13, FIG. 13 is a schematic interaction diagram of the information transmission method in some embodiments of the present application. After step S740, steps S705 to S705 can be executed. S709. For example, after step S740, when the downlink data is sent, the first access network device determines that the terminal device does not have uplink and downlink data, and may perform steps S705 to S709. The embodiments of the application are not limited here.

Optionally, in some possible implementation manners of the present application, the third indication information sent in step S708 and the downlink data sent in step S740 may be sent to the terminal device in the same signaling. For example, the first access network device may send third information to the terminal device. The third information includes the third indication information and downlink data. After the terminal device receives the third information, it may first receive the downlink data according to the context. For data, after the downlink data is received, the context is suspended or deactivated.

Optionally, in some possible implementation manners of the present application, as shown in FIG. 14, FIG. 14 is a schematic interaction diagram of a method for suspending the context of a terminal device in some embodiments of the present application. As shown in FIG. 14, step The steps of suspending or deactivating the context shown in S705 to S709 may not depend on the steps of restoring the up and down shown in steps S710 to S740. Steps S705 to S709 can be performed separately. For example, no matter whether there is downlink data transmission after S709, or whether context recovery and downlink data transmission are performed before S705, when the first access network device determines that the terminal device does not currently have uplink and downlink data, step S705 is executed. To S709.

It should also be understood that, in the above suspension process, the first access network device is the access network that suspends the context as an example for description. In the embodiment of the present application, the access network device that suspends the context is still It may be another access network device (for distinguishing, the second access network device is taken as an example for description). When the access network device for which the context is suspended is not the first access network device, in the above step S730, when the first information includes the resume ID, the first access network device needs to request the second access device The context. Specifically, the first access network device may send a resume UE context request (Retrieve UE context request) to the second access network device through the X2-AP interface to request the context, and the resume context request carries a resume ID. The second access network device sends a Retrieve UE context response (Retrieve UE context response) to the first access network device through the X2-AP interface, which carries the context. The second access network device can obtain the context through the resume ID.

The method of information transmission provided in this application will be described below with specific examples.

First describe the specific process of suspending the context.

As shown in FIG. 15, FIG. 15 is a schematic interaction diagram of suspending the context in some embodiments of the present application. In the example shown in FIG. 15, the core network equipment includes the MME and the S-GW, the terminal equipment takes the UE as an example, and the first access network equipment takes the eNB as an example for illustration.

As shown in Figure 15, in S801, the eNB decides to suspend the context of the UE. For example, when the eNB determines that the UE does not have uplink and downlink data, the eNB decides to suspend the context of the UE. The eNB allocates a resume ID for the UE, and the resume ID is used to identify the context of the UE. Suspending the context of the UE can be understood as the eNB releasing the RRC connection with the UE, but the eNB does not release the context of the UE, but saves the context of the UE.

In S802, the eNB requests the MME to suspend the UE (Suspend). For example, the eNB sends a UE context suspend request (UE context suspend request) to the MME, requesting to release the RRC connection with the UE, but the eNB does not release the UE context . The UE context suspension request is equivalent to the first request in step S705, and the UE context suspension request includes the resume ID of the UE. Optionally, the UE context suspension request includes the first identifier and the context, or includes the UE context, or includes the resume ID and the context. The first identifier may be the S-TMSI or IMSI of the UE. The MME can save the resume ID and/or the context.

In S803, the MME and the S-GW interact to release access bearers (release access bearers) information.

In S804, the MME sends a UE context suspend response (UE context suspend response) to the eNB. The UE context suspension response is equivalent to the first response message in step S707. When the eNB receives the UE context suspension response from the MME, the eNB is allowed to suspend the UE context, and the eNB suspends the UE context at this time.

In S805, the eNB sends an RRC connection release (RRC connection Release) message to the UE, and indicates in the message to suspend the context of the UE. The RRC connection release message may be equivalent to the third indication information in step S708. The RRC connection release message carries a resume ID, and the resume ID is used to identify the context of the UE.

In S806, the UE releases the RRC connection of the UE according to the RRC connection release message, and saves the context of the UE. Specifically, the UE saves the context (or referred to as suspending the context of the UE), suspends the SRB and DRB with the eNB, and the UE enters the RRC idle state.

Optionally, in the process shown in FIG. 15, in step S802, if the UE context suspend request includes the resume ID, the resume ID may be carried in the UE context suspend request information for paging. The recommended cell and base station information (Information on Recommended Cells and eNBs for Paging) field, that is, the Information on Recommended Cells and eNBs for Paging information includes the resume ID. Alternatively, the resume ID may also be carried in the UE context suspend request information and the cell identifier and coverage enhancement level (Cell Identifier and Coverage Enhancement Level) fields, that is, the Cell Identifier and Coverage Enhancement Level information includes the resume ID. This application does not limit the specific position of the resume ID in the UE context suspend request cell.

Optionally, in the above step S804, if the UE Context Suspend Response message includes a security context (Security Context), the eNB saves the Security Context to the UE Context (UE Context), and deletes any saved unused { NH, NCC}. Security Context provides security-related parameters for deriving security keys, which include Next-Hop (NH) and Next Hop Chaining Count (NCC).

As shown in FIG. 16, FIG. 16 is a schematic interaction diagram of restoring the context in some embodiments of the present application. In the example shown in FIG. 16, the core network equipment includes MME and S-GW. The terminal device is illustrated by taking the UE as an example. The first access network device is the access network device that sends a paging message to the UE, and the second access network device is the access network device that suspends the context of the UE. The second access network device is the eNB shown in FIG. 15. In some possible implementation manners, the steps shown in FIG. 16 may be performed after the steps shown in FIG. 15. In other possible implementation manners, the steps shown in FIG. 16 may be performed before the steps shown in FIG. 15.

As shown in Figure 16, the method includes:

S901: The S-GW sends a downlink data notification message (downlink data notification) to the MME, indicating that downlink data of the UE has arrived.

Optionally, the S-GW also sends first indication information to the MME, where the first indication information is used to indicate at least one of the following four types of information:

The downlink data has only one data packet (single packet);

The size of the data packet of the downlink data is less than a threshold;

The downlink data packet will not trigger the uplink data;

This downstream data packet will trigger upstream data.

Optionally, the first indication information may be included in the downlink data notification message.

Optionally, the S-GW also sends downlink data to the MME.

S902: The MME sends a Paging message (denoted as S1 Paging) to the first access network device according to the received downlink data notification message, and the S1 Paging message includes the Resume ID. Alternatively, the S1 Paging message includes the first identifier of the UE and the context, or the S1 Paging message includes the Resume ID of the UE and the context. The first identifier may be the S-TMSI or IMSI of the UE.

Optionally, S1 Paging may also include the foregoing first indication information.

Optionally, if the MME receives downlink data from the S-GW, the MME may include the downlink data in S1 Paging, that is, the S1 Paging includes the downlink data. Alternatively, the MME may save the downlink data, and send the downlink data to the first access network device after the S1 Paging message.

Optionally, the S1 Paging message may carry indication information used to indicate CP-DL-EDT or UP-DL-EDT, and the indication information is used to instruct the MME to recommend or suggest that the first access network device uses the CP scheme and/or UP Scheme to send downlink data.

Optionally, the Resume ID in the S1 Paging message may be carried in the field used to carry the S-TMSI of the UE in the S1 Paging message, that is, the S-TMSI is not carried in the S1 Paging message.

Optionally, the S-TMSI and the Resume ID are carried in the S1 Paging message.

S903. The first access network device determines, according to the Resume ID carried in the received S1 Paging message, whether to save the context of the UE identified by the Resume ID.

In a possible implementation manner, if the first access network device determines that the context of the UE is not saved, for example, the first access network device is not the access network device that suspends the context of the UE, assuming the second access The network device is an access network device that suspends the context of the UE, and the first access network device needs to perform steps S904 and S905.

S904: The first access network device sends a Retrieve UE Context Request (Retrieve UE Context Request) to the second access network device indicated by the Resume ID. Optionally, the Retrieve UE Context Request may also include indication information used to instruct the second access network device not to perform MAC-I verification.

S905: The second access network device sends a UE context recovery response (Retrieve UE context response) to the first access network through the X2-AP interface, which carries the context of the UE. The second access network device can obtain the context of the UE through the resume ID.

In a possible implementation manner, if the first access network device saves the context of the UE, steps S904 and S905 do not need to be performed, and after S903, steps S906 to S913 are directly performed.

In some possible implementations, if step S901 does not carry downlink data, steps S906 to S909 need to be executed.

In some possible implementation manners, if step S901 carries downlink data, steps S906 to S909 do not need to be performed. After S903 or S905, steps S910 to S913 are directly executed, or S911 to S913 are directly executed.

S906: The first access network device requests a path switch (path switch) from the MME.

S907: The MME and the S-GW exchange a bearer modification message.

S908: The MME sends a path switch response message to the first access network device.

S909: The S-GW sends downlink data to the first access network device.

S910. After the first access network device obtains the UE context from the second access network device, the first access network device may send the UE Context release to the second access network device to indicate the second access network device. The network access device releases the context of the UE.

S911: After the first access network device receives the downlink data sent from the S-GW or the MME, the first access network device activates or restores the context of the UE, and the first access network device sends Uu Paging to the UE.

Optionally, Uu Paging may include indication information used to instruct the terminal device to receive downlink data. The indication information can be a display indication or an implicit indication.

Specifically, the way of displaying the indication, for example, the Uu Paging message contains 1 bit to indicate that the terminal device receives downlink data.

The way of implicit indication, for example, the Uu Paging message may include radio network temporary identifier (RNTI) and/or physical random access channel (PRACH) resources related to receiving downlink data. parameter. After receiving the parameters related to the received downlink data, the terminal device can learn that downlink data will arrive.

Optionally, when the first access network device acquires the context of the UE, or when it receives downlink data from the S-GW, or when it receives a paging message from the MME, or, When an access network device learns that downlink data has arrived, or when the first access network device receives an indication of early transmission of downlink data, or when the first access network device receives the first information, the first access network device The device restores the UE context and activates the security context in the UE context. If the first access network device receives the downlink data sent from the S-GW or MME, the first access network device uses the activated UE security information (security context) to encrypt the downlink data.

S912: The UE restores or activates the context according to the Uu Paging message. Specifically, the UE restores the SRB and DRB configuration, and activates security information (security context).

Optionally, the Uu Paging message includes the Resume ID.

Optionally, the Uu Paging message may also include the identification of the terminal device.

Optionally, the Uu Paging message carries an RNTI for receiving downlink early transmission data.

Optionally, the Uu Paging message carries time-frequency resource configuration for early transmission of downlink data.

In a possible implementation manner, the UE restores or activates the context according to the Uu Paging message, which may specifically include one of the following methods:

If the Uu Paging message includes the Resume ID, the UE resumes or activates the context;

If the Uu Paging message carries the RNTI used to receive downlink early transmission data, the UE restores or activates the context;

If the Uu Paging message carries the time-frequency resource configuration for early transmission of downlink data, the UE restores or activates the context.

S913: The UE receives downlink data sent by the first access network device.

Optionally, if the downlink data sent by the first access network device is encrypted using the security context in the context, the UE uses the security context to decrypt the downlink data.

Optionally, if the Uu Paging message includes the downlink data, step S913 is not required.

Optionally, after the steps shown in FIG. 16 are executed, for example, after the downlink data is sent, the first access network device determines that the terminal device has no uplink and downlink data, it may also perform the suspension shown in FIG. 15 Steps in the context of the UE. The embodiments of the application are not limited here.

In the method for information transmission provided in this application, the core network device notifies the first access network device of first information for the first access network device to determine the context of the terminal device, and the first access network device may Information, determine (restore or activate) the context of the terminal device, so that when the downlink data sent by the core network device is received, the downlink data can be sent to the terminal device according to the context, so that the downlink data can be sent to the terminal device earlier (For example, the downlink data can be sent to the terminal device before Msg4 or Msg3), which improves the efficiency and reliability of downlink data transmission, thereby improving communication efficiency.

It should be understood that in the various embodiments of the present application, the first, the second, etc. are only used to indicate that multiple objects are different. For example, the first access network device and the second access network device are only used to indicate different access network devices. It should not have any influence on the access network equipment itself, and the above-mentioned first, second, etc. should not cause any limitation to the embodiments of the present application.

It should also be understood that the foregoing is only to help those skilled in the art to better understand the embodiments of the present application, and is not intended to limit the scope of the embodiments of the present application. Those skilled in the art can obviously make various equivalent modifications or changes based on the above examples given. For example, some steps in the various embodiments of the above methods may not be necessary, or some new steps may be added. . Or a combination of any two or any of the above embodiments. Such a modified, changed or combined solution also falls within the scope of the embodiments of the present application.

It should also be understood that the above description of the embodiments of the present application focuses on emphasizing the differences between the various embodiments, and the same or similarities that are not mentioned can be referred to each other, and for the sake of brevity, details are not repeated here.

It should also be understood that the size of the sequence numbers of the aforementioned processes does not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

It should also be understood that in the embodiments of the present application, "pre-set" and "pre-defined" can be pre-stored in the equipment (for example, including terminal equipment and access network equipment) by pre-saving corresponding codes, tables or other information that can be used to indicate related This application does not limit the specific implementation method.

It should also be understood that the methods, situations, categories, and embodiments in the embodiments of the present application are only for convenience of description and should not constitute special limitations. The various methods, categories, situations, and features in the embodiments are not contradictory. The circumstances can be combined.

It should also be understood that, in the various embodiments of the present application, if there are no special instructions and logical conflicts, the terms and/or descriptions between the different embodiments are consistent and can be mutually cited. The technical features in the different embodiments According to its inherent logical relationship, it can be combined to form a new embodiment.

The information transmission method of the embodiment of the present application has been described in detail above with reference to FIGS. 1 to 16. Hereinafter, the communication device according to the embodiment of the present application will be described in detail with reference to FIGS. 17 to 24.

FIG. 17 shows a schematic block diagram of a communication device 1000 according to an embodiment of the present application. The device 1000 may correspond to the first access network device described in the foregoing method 700 to method 900, or may be applied to the first access network device The chip or component of the device 1000, and each module or unit in the device 1000 is used to execute each action or process performed by the first access network device in the above method 700 to method 900. As shown in FIG. 17, the device 1000 It may include a transceiving unit 1010 and a processing unit 1020. The transceiver unit 1010 is configured to perform specific signal transceiver under the driving of the processing unit 1020.

The transceiver unit 1010 is configured to receive first information from a core network device, the first information is used by the communication device to determine the context of the terminal device, and the context is used by the communication device to send downlink data to the terminal device; wherein the context is Pending

The processing unit 1020 is configured to determine the context according to the first information;

The transceiver unit 1010 is further configured to: according to the context, send the downlink data to the terminal device.

In the communication device provided in this application, the core network device notifies the communication device of the first information used for the communication device to determine the context of the terminal device. Among them, the context of the terminal device has been suspended. The communication apparatus can determine (restore or activate) the context of the terminal device according to the first information, so that when receiving downlink data sent by the core network device, it can send the downlink data to the terminal device according to the context. The downlink data can be sent to the terminal device earlier. For example, the downlink data can be sent to the terminal device before Msg4 or Msg3, which reduces the power consumption overhead of the terminal receiving downlink data and improves the efficiency and reliability of downlink data transmission. Improve communication efficiency.

Optionally, in some embodiments of the present application, the context includes a security context; the processing unit 1020 is specifically configured to: perform encryption and/or integrity protection on the downlink data according to the security context; the transceiver unit 1010 is further configured to: Send the encrypted and/or integrity-protected downlink data to the terminal device.

Optionally, in some embodiments of the present application, the transceiver unit 1010 is specifically configured to: according to the context, send second information to the terminal device, where the second information includes the downlink data.

Optionally, in some embodiments of the present application, the transceiver unit 1010 is specifically configured to: send second information to the terminal device at the paging occasion of sending a paging message, and the second information is used to schedule the downlink data; or , Sending second information to the terminal device, where the second information includes scheduling information, and the scheduling information is used to schedule the downlink data.

Optionally, in some embodiments of the present application, the second information is the paging message, the paging message further includes scheduling information, and the scheduling information is used to schedule the downlink data, or the second information is scheduling Information, the scheduling information is used to schedule the downlink data.

Optionally, in some embodiments of the present application, the first information includes a first identifier of the terminal device and the context, and the first identifier is allocated by the core network device; or, the first information includes the terminal device The second identifier is assigned by the communication device, and the second identifier is used to identify the context; or, the first information includes the second identifier of the terminal device and the context.

Optionally, in some embodiments of the present application, the transceiver unit 1010 is further configured to send a first request to the core network device, where the first request is used to request suspension or deactivation of the context, and the first request includes the first request. Three information, the third information is used by the communication device to determine the context of the terminal device; a first response message in response to the first request is received from the core network device, and the first response message is used to instruct the communication device to suspend Or deactivate the context of the terminal device; the processing unit 1020 is further configured to: suspend or deactivate the context of the terminal device according to the first response message.

Optionally, in some embodiments of the present application, the third information includes the first identifier of the terminal device and the context, and the first identifier is allocated by the core network device; or, the third information includes the terminal device's A second identifier, where the second identifier is allocated by the first access network device, and the second identifier is used to identify the context; or, the third information includes the second identifier of the terminal device and the context.

Optionally, in some embodiments of the present application, the first information further includes first indication information, and the first indication information is used to indicate that the downlink data will trigger the terminal device to send uplink data, and the downlink data will not trigger The terminal device sends uplink data and the downlink data only includes at least one of a data packet.

Optionally, in some embodiments of the present application, the first identifier is the system architecture evolution temporary mobile equipment identifier S-TMSI or the international mobile subscriber identity IMSI of the terminal device; the second identifier is the recovery of the terminal device Identifies the resume ID.

Further, the device 1000 may further include a storage unit 1030. The transceiver unit 1010 may be a transceiver or an input/output interface or an interface circuit or the like. The storage unit 1030 is used to store instructions executed by the transceiver unit 1010 and the processing unit 1020. The transceiving unit 1010, the processing unit 1020, and the storage unit 1030 are coupled to each other. The storage unit 1030 stores instructions. The processing unit 1020 is used to execute the instructions stored in the storage unit 1030. The transceiving unit 1010 is used to perform specific signal transceiving under the driving of the processing unit 1020. .

It should be understood that, for the specific process of each unit in the apparatus 1000 performing the above-mentioned corresponding steps, please refer to the first access network device or eNB-related description in the foregoing in conjunction with the related embodiments in the methods shown in FIGS. 10 to 16. For brevity, here Do not repeat it.

Optionally, the transceiving unit 1010 may include a receiving unit (module) and a sending unit (module), which are used to execute each embodiment of the foregoing method 700 to method 900 and the first access in the embodiments shown in FIG. 10 to FIG. The steps of network equipment or eNB receiving information and sending information.

It should be understood that the transceiver unit 1010 may be a transceiver, an input/output interface, or an interface circuit. The storage unit 1030 may be a memory. The processing unit 1010 may be implemented by a processor. As shown in FIG. 18, the communication device 1100 may include a processor 1110, a memory 1120, and a transceiver 1130.

The communication device 1000 shown in FIG. 17 or the communication device 1100 shown in FIG. 18 can implement various embodiments of the foregoing method 700 to method 900 and the execution performed by the first access network device in the embodiments shown in FIG. 10 to FIG. 16 step. For similar description, please refer to the description in the corresponding method. To avoid repetition, I won’t repeat them here.

It should also be understood that the communication apparatus 1000 shown in FIG. 17 or the communication apparatus 1100 shown in FIG. 18 may be an access network device.

FIG. 19 shows a schematic block diagram of a communication device 1200 according to an embodiment of the present application. The device 1200 may correspond to the core network equipment described in the foregoing methods 700 to 900, or may be a chip or component applied to the core network equipment, and , Each module or unit in the device 1200 is used to execute each action or processing procedure performed by the core network device in the above method 700 to method 900, as shown in FIG. 19, the device 1200 may include a processing unit 1210 and a transceiver unit 1220 . The transceiver unit 1220 is configured to perform specific signal transceiver under the driving of the processing unit 1210.

The processing unit 1210 is configured to determine first information, where the first information is used by the first access network device to determine the context of the terminal device, and the context is used by the first access network device to send downlink data to the terminal device, where: The context is pending;

The transceiver unit 1220 is configured to send the first information to the first access network device.

The communication device provided in this application notifies the communication device of the context related information of the suspended terminal device through the access network device, so that when the communication device has downlink data of the terminal device, the communication device can use the terminal The context related information of the device is notified to the access network device, so that when the access network device receives the downlink data, the access network device can obtain the context of the terminal device according to the context related information, and then according to the context Send the downlink data to the terminal device. The downlink data can be sent to the terminal device before Msg4 or Msg3, which reduces the power consumption of the terminal receiving downlink data, improves the efficiency and reliability of downlink data transmission, and thereby improves communication efficiency.

Optionally, in some embodiments of the present application, the first information includes the first identifier of the terminal device and the context, and the first identifier is allocated by the communication device; or, the first information includes the terminal device's A second identifier, where the second identifier is allocated by the first access network device, and the second identifier is used to identify the context; or, the first information includes the second identifier of the terminal device and the context.

Optionally, in some embodiments of the present application, the transceiver unit 1220 is further configured to: receive a first request from the first access network device, where the first request is used to request suspension or deactivation of the context, and the second A request includes third information, and the third information is used by the first access network device to determine the context of the terminal device; and a first response message in response to the first request is sent to the first access network device. A response message is used to instruct the first access network device to suspend or deactivate the context.

It should be understood that for the specific process of each unit in the apparatus 1200 performing the above corresponding steps, please refer to the description of the core network equipment in the relevant embodiments in the method 700 to method 900 shown in FIG. 10 to FIG. 16. For brevity, here Do not repeat it.

Optionally, the transceiving unit 1220 may include a receiving unit (module) and a sending unit (module), which are used to execute each embodiment of the aforementioned method 700 to method 900 and the access network device in the embodiment shown in FIG. 10 to FIG. 16 The steps of receiving and sending information. Optionally, the communication device 1200 may further include a storage unit 1230 for storing instructions executed by the processing unit 1210 and the transceiver unit 1220. The processing unit 1210, the transceiving unit 1220, and the storage unit 1230 are in communication connection. The storage unit 1230 stores instructions. The processing unit 1210 is used to execute the instructions stored in the storage unit 1230. The transceiving unit 1220 is used to perform specific signal transceiving under the driving of the processing unit 1210. .

It should be understood that the transceiver unit 1220 may be a transceiver, an input/output interface, or an interface circuit. The storage unit 1230 may be a memory. The processing unit 1210 may be implemented by a processor. As shown in FIG. 20, the communication device 1300 may include a processor 1310, a memory 1320, and a transceiver 1330.

The communication device 1200 shown in FIG. 19 or the communication device 1300 shown in FIG. 20 can implement various embodiments of the aforementioned method 700 to method 900 and the steps performed by the core network device in the embodiments shown in FIG. 10 to FIG. 19. For similar description, please refer to the description in the corresponding method. To avoid repetition, I won’t repeat them here.

It should also be understood that the communication apparatus 1200 shown in FIG. 19 or the communication apparatus 1300 shown in FIG. 20 may be a core network device. For example, the core network equipment may be S-GW, or MME, or SMF, or AMF, or UPF, or the like.

FIG. 21 shows a schematic block diagram of a communication device 1400 according to an embodiment of the present application. The device 1400 may correspond to the terminal device described in the above method 700 to method 900, or may be a chip or component applied to the terminal device, and Each module or unit in the apparatus 1400 is respectively used to execute each action or processing procedure performed by the terminal device in the foregoing method 700 to method 900. As shown in FIG. 21, the apparatus 1400 may include a transceiver unit 1410 and a processing unit 1420 and 1420. The transceiving unit 1410 is configured to perform specific signal transceiving under the driving of the processing unit 1420.

The transceiver unit 1410 is configured to receive second information from a first access network device, the second information includes second indication information, and the second indication information is used to instruct the terminal device to restore the context of the terminal device, wherein the context Is pending

The processing unit 1420 is configured to restore the context according to the second information;

The transceiver unit 1410 is further configured to receive downlink data from the first access network device according to the restored context.

The communication device provided by the present application can restore the context according to the second information sent by the access network device, and receive the downlink data sent by the access network device according to the restored context section, so that the downlink data can be sent to The communication device, for example, the communication device may receive the downlink data before Msg4 or Msg3 according to the context, thereby reducing the power consumption of the communication device for receiving downlink data, and improving the efficiency and reliability of downlink data transmission, thereby improving Communication efficiency.

Optionally, in some embodiments of the present application, the context includes a security context, and the processing unit 1420 is further configured to: according to the security context in the context, perform processing on the downlink data received from the first access network device Decrypt.

Optionally, in some embodiments of the present application, the second information is a paging message, and the paging message includes the downlink data.

Optionally, in some embodiments of the present application, the transceiving unit 1410 is specifically configured to: receive the second information from the first access network device at the paging timing of receiving the paging message, and the second information further includes scheduling Information, the scheduling information is used to schedule the downlink data.

Optionally, in some embodiments of the present application, the second information is a paging message, and the paging message further includes scheduling information, and the scheduling information is used to schedule the downlink data.

Optionally, in some embodiments of the present application, the second information is scheduling information, and the scheduling information is used to schedule the downlink data.

It should be understood that, for the specific process of each unit in the device 1400 performing the above-mentioned corresponding steps, please refer to the description of the terminal device in the relevant embodiments of the method 700 to the method 900 shown in FIG. 10 to FIG. Repeat.

Optionally, the transceiving unit 1420 may include a receiving unit (module) and a sending unit (module), which are used to execute each embodiment of the foregoing method 700 to method 900 and the access network device in the embodiment shown in FIG. 10 to FIG. 16 The steps of receiving and sending information. Optionally, the communication device 1400 may further include a storage unit 1430 configured to store instructions executed by the processing unit 1410 and the transceiver unit 1420. The processing unit 1410, the transceiving unit 1420 and the storage unit 1430 are in communication connection. The storage unit 1430 stores instructions. The processing unit 1410 is used to execute the instructions stored in the storage unit 1430. The transceiving unit 1420 is used to perform specific signal transceiving under the driving of the processing unit 1410. .

It should be understood that the transceiver unit 1420 may be a transceiver, an input/output interface, or an interface circuit. The storage unit 1430 may be a memory. The processing unit 1410 may be implemented by a processor. As shown in FIG. 22, the communication device 1500 may include a processor 1510, a memory 1520, and a transceiver 1530.

The communication device 1400 shown in FIG. 21 or the communication device 1500 shown in FIG. 22 can implement various embodiments of the foregoing method 700 to method 900 and the steps performed by the terminal device in the embodiments shown in FIG. 10 to FIG. 19. For similar description, please refer to the description in the corresponding method. To avoid repetition, I won’t repeat them here.

It should also be understood that the communication device 1400 shown in FIG. 21 or the communication device 1500 shown in FIG. 22 may be a terminal device.

FIG. 23 is a schematic structural diagram of a terminal device 1700 provided by this application. The foregoing apparatus 1400 or 1500 may be configured in the terminal device 1700, or the apparatus 1400 or 1500 itself may be the terminal device 1700. In other words, the terminal device 1700 can execute the actions performed by the terminal device in the foregoing methods 700 to 900.

For ease of description, FIG. 23 only shows the main components of the terminal device. As shown in FIG. 23, the terminal device 1700 includes a processor, a memory, a control circuit, an antenna, and an input and output device.

The processor is mainly used to process the communication protocol and communication data, and to control the entire terminal device, execute the software program, and process the data of the software program, for example, to support the terminal device to execute the above-mentioned transmission precoding matrix instruction method embodiment The described action. The memory is mainly used to store software programs and data, for example, to store the codebook described in the above embodiments. The control circuit is mainly used for the conversion of baseband signal and radio frequency signal and the processing of radio frequency signal. The control circuit and the antenna together can also be called a transceiver, which is mainly used to send and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, and keyboards, are mainly used to receive data input by users and output data to users.

When the terminal device is turned on, the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then sends the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.

Those skilled in the art can understand that, for ease of description, FIG. 23 only shows a memory and a processor. In actual terminal devices, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, etc., which is not limited in the embodiment of the present application.

For example, the processor may include a baseband processor and a central processing unit. The baseband processor is mainly used to process communication protocols and communication data. The central processing unit is mainly used to control the entire terminal device, execute software programs, and process software programs. data. The processor in FIG. 23 integrates the functions of the baseband processor and the central processing unit. Those skilled in the art can understand that the baseband processor and the central processing unit may also be independent processors and are interconnected by technologies such as buses. Those skilled in the art can understand that the terminal device may include multiple baseband processors to adapt to different network standards, the terminal device may include multiple central processors to enhance its processing capabilities, and various components of the terminal device may be connected through various buses. The baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit can also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and communication data can be built in the processor, or can be stored in the storage unit in the form of a software program, and the processor executes the software program to realize the baseband processing function.

Exemplarily, in the embodiment of the present application, the antenna and control circuit with the transceiving function can be regarded as the transceiving unit 1701 of the terminal device 1700, and the processor with the processing function can be regarded as the processing unit 1702 of the terminal device 1700. As shown in FIG. 23, the terminal device 1700 includes a transceiving unit 1701 and a processing unit 1702. The transceiver unit may also be called a transceiver, a transceiver, a transceiver, and so on. Optionally, the device for implementing the receiving function in the transceiving unit 1701 can be regarded as the receiving unit, and the device for implementing the sending function in the transceiving unit 1701 as the sending unit, that is, the transceiving unit 1701 includes a receiving unit and a sending unit. Exemplarily, the receiving unit may also be called a receiver, a receiver, a receiving circuit, etc., and the sending unit may be called a transmitter, a transmitter, or a transmitting circuit, etc.

FIG. 24 is a schematic structural diagram of an access network device 1800 provided by an embodiment of the application, which may be used to implement the functions of the access network device in the foregoing method. The access network equipment 1800 includes one or more radio frequency units, such as a remote radio unit (RRU) 1801 and one or more baseband units (BBU) (also referred to as digital units, digital units, DU) 1802. The RRU 1801 may be called a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc., and it may include at least one antenna 18011 and a radio frequency unit 18012. The RRU 1801 part is mainly used for the transmission and reception of radio frequency signals and the conversion between radio frequency signals and baseband signals, for example, for sending the signaling message in the foregoing embodiment to the terminal device. The 1802 part of the BBU is mainly used for baseband processing and control of the base station. The RRU 1801 and the BBU 1802 may be physically set together, or may be physically separated, that is, a distributed base station.

The BBU 1802 is the control center of the base station, and can also be called a processing unit, which is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, and spreading. For example, the BBU (processing unit) 1802 may be used to control the base station 180 to execute the operation procedure of the access network device in the foregoing method embodiment.

In an example, the BBU 1802 can be composed of one or more single boards, and multiple single boards can jointly support a radio access network of a single access standard (such as an LTE system or a 5G system), and can also support different connections. Enter the standard wireless access network. The BBU 1802 also includes a memory 18021 and a processor 18022. The memory 18021 is used to store necessary instructions and data. For example, the memory 18021 stores the codebook in the above-mentioned embodiment and the like. The processor 18022 is configured to control the base station to perform necessary actions, for example, to control the base station to execute the operation procedure of the access network device in the foregoing method embodiment. The memory 18021 and the processor 18022 may serve one or more boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.

In a possible implementation manner, with the development of system-on-chip (SoC) technology, all or part of the functions of part 1802 and part 1801 can be implemented by SoC technology, for example, a base station function chip Realization, the base station function chip integrates a processor, a memory, an antenna interface and other devices, the program of the base station related functions is stored in the memory, and the processor executes the program to realize the related functions of the base station. Optionally, the base station function chip can also read a memory external to the chip to implement related functions of the base station.

It should be understood that the structure of the access network device illustrated in FIG. 24 is only a possible form, and should not constitute any limitation in the embodiment of the present application. This application does not exclude the possibility of other base station structures that may appear in the future.

According to the method provided in the embodiment of the present application, the embodiment of the present application also provides a communication system, which includes the aforementioned access network equipment, core network equipment, and terminal equipment.

It should be understood that in this embodiment of the application, the processor may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), and dedicated integration Circuit (application specific integrated circuit, ASIC), ready-made programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.

It should also be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of random access memory (RAM) are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (DRAM), and synchronous dynamic random access memory (DRAM). Access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory Take memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

The foregoing embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented by software, the above-mentioned embodiments may be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on the computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a dedicated computer, a computer network, or other programmable devices. The computer instruction 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 instruction may be transmitted from a website, computer, server, or data center through a cable (Such as infrared, wireless, microwave, etc.) to another website site, 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 or a data center that includes one or more sets of available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium may be a solid state drive.

An embodiment of the present application also provides a communication system, which includes: the aforementioned terminal device, the aforementioned access network device, and the aforementioned core network device.

The embodiment of the present application also provides a computer-readable medium for storing computer program code. The computer program includes instructions for executing the information transmission method of the foregoing method 700 to method 900 in the embodiment of the present application. The readable medium may be read-only memory (ROM) or random access memory (RAM), which is not limited in the embodiment of the present application.

This application also provides a computer program product. The computer program product includes instructions. When the instructions are executed, the terminal device, the access network device, and the core network device respectively execute the terminal device and the interface corresponding to the above method. Operation of network access equipment and core network equipment.

The embodiment of the present application also provides a system chip. The system chip includes a processing unit and a communication unit. The processing unit may be, for example, a processor, and the communication unit may be, for example, an input/output interface, a pin, or a circuit. The processing unit can execute computer instructions so that the chip in the communication device executes any of the information transmission methods provided in the foregoing embodiments of the present application.

Optionally, any one of the communication devices provided in the foregoing embodiments of the present application may include the system chip.

Optionally, the computer instructions are stored in a storage unit.

Optionally, the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit can also be a storage unit in the terminal located outside the chip, such as a ROM or other storage units that can store static information and instructions. Types of static storage devices, RAM, etc. Wherein, the processor mentioned in any one of the above may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits used to control the program execution of the feedback information transmission method described above. The processing unit and the storage unit can be decoupled, respectively set on different physical devices, and connected in a wired or wireless manner to realize the respective functions of the processing unit and the storage unit, so as to support the system chip to implement the above embodiments Various functions in. Alternatively, the processing unit and the memory may also be coupled to the same device.

It can be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of random access memory (RAM) are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (DRAM), and synchronous dynamic random access memory (DRAM). Access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory Take memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

The terms "system" and "network" in this article are often used interchangeably in this article. The term "and/or" in this article is only an association relationship describing the associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations. In addition, the character "/" in this text generally indicates that the associated objects before and after are in an "or" relationship.

The terms "uplink" and "downlink" appearing in this application are used to describe the direction of data/information transmission in a specific scenario. For example, the "uplink" direction generally refers to the direction or distribution of data/information from the terminal to the network side. The direction of transmission from the central unit to the centralized unit. The "downlink" direction generally refers to the direction in which data/information is transmitted from the network side to the terminal, or the direction from the centralized unit to the distributed unit. It can be understood that "uplink" and "downlink" "It is only used to describe the direction of data/information transmission. The specific start and end equipment of the data/information transmission is not limited.

In this application, various objects such as various messages/information/equipment/network elements/systems/devices/actions/operations/processes/concepts that may appear are assigned names. It is understandable that these specific names are not It constitutes a limitation on related objects, and the assigned name can be changed according to factors such as the scene, context or usage habits. The understanding of the technical meaning of the technical terms in this application should mainly be based on the function embodied/performed in the technical solution And technical effects to determine.

A person of ordinary skill in the art may be aware that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which is not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiment described above is only illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not implemented. In addition, 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, and may be in electrical, mechanical or other forms.

The unit described as a separate component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or may be distributed to multiple network units . Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), and random access.

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method of information transmission, characterized in that it comprises:

The first access network device receives first information from the core network device, where the first information is used by the first access network device to determine the context of the terminal device, and the context is used by the first access network device to send The terminal device sends downlink data; wherein, the context is suspended;

The first access network device determines the context according to the first information;

The first access network device sends the downlink data to the terminal device according to the context.
The method according to claim 1, wherein the context includes a security context;

The sending, by the first access network device, the downlink data to the terminal device according to the context includes:

Performing, by the first access network device, encryption and/or integrity protection on the downlink data according to the security context;

The first access network device sends the encrypted and/or integrity-protected downlink data to the terminal device.
The method according to claim 1 or 2, wherein the first access network device sending the downlink data to the terminal device according to the context comprises:

The first access network device sends second information to the terminal device according to the context, where the second information includes the downlink data.
The method according to claim 1 or 2, wherein the method further comprises:

The first access network device sends second information to the terminal device at a paging occasion for sending a paging message, where the second information is used to schedule the downlink data; or,

The first access network device sends second information to the terminal device, the second information includes scheduling information, and the scheduling information is used to schedule the downlink data.
The method according to any one of claims 1 to 4, wherein the first information comprises:

The first identifier of the terminal device and the context, where the first identifier is allocated by the core network device; or,

The second identifier of the terminal device, the second identifier is allocated by the first access network device, and the second identifier is used to identify the context; or,

The second identifier of the terminal device and the context.
The method according to any one of claims 1 to 5, wherein the method further comprises:

The first access network device sends a first request to the core network device. The first request is used to request suspension or deactivation of the context. The first request includes third information. The information is used by the first access network device to determine the context of the terminal device;

The first access network device receives a first response message in response to the first request from the core network device, where the first response message is used to instruct the first access network device to suspend or deactivate The context of the terminal device;

The first access network device suspends or deactivates the context of the terminal device according to the first response message.
The method according to any one of claims 1 to 6, wherein the first information further comprises first indication information, and the first indication information is used to indicate that the downlink data will trigger the terminal device Sending uplink data, the downlink data does not trigger the terminal device to send uplink data, and the downlink data only includes at least one of a data packet.
The method according to claim 5, wherein the first identifier is the system architecture evolution temporary mobile equipment identifier S-TMSI or the international mobile subscriber identity IMSI of the terminal device;

The second identifier is the resume ID of the terminal device.
An information transmission method, characterized by comprising:

The core network device determines first information, where the first information is used by the first access network device to determine the context of the terminal device, and the context is used by the first access network device to send downlink data to the terminal device, where , The context is suspended;

The core network device sends the first information to the first access network device.
The method according to claim 9, wherein the first information comprises:

The first identifier of the terminal device and the context, where the first identifier is allocated by the core network device; or,

The second identifier of the terminal device, the second identifier is allocated by the first access network device, and the second identifier is used to identify the context; or,

The second identifier of the terminal device and the context.
[Corrected according to Rule 91 01.07.2019]

The method according to claim 9 or 10, wherein the method further comprises:

The core network device receives a first request from the first access network device, the first request is used to request to suspend or deactivate the context, the first request includes third information, and the third The information is used by the first access network device to determine the context of the terminal device;

The core network device sends a first response message in response to the first request to the first access network device, where the first response message is used to instruct the first access network device to suspend or deactivate The context.
The method according to claim 10 or 11, wherein the first information further comprises first indication information, and the first indication information is used to indicate that the downlink data will trigger the terminal device to send uplink data, The downlink data does not trigger the terminal device to send uplink data, and the downlink data only includes at least one of a data packet.
The method according to claim 10, wherein the first identifier is the system architecture evolution temporary mobile equipment identifier S-TMSI or the international mobile subscriber identity IMSI of the terminal device;

The second identifier is the resume ID of the terminal device.
A method of information transmission, characterized in that it comprises:

The terminal device receives second information from the first access network device, the second information includes second indication information, and the second indication information is used to instruct the terminal device to restore the context of the terminal device, wherein the The context is pending;

The terminal device restores the context according to the second information;

The terminal device receives downlink data from the first access network device according to the restored context.
The method according to claim 14, wherein the context includes a security context, and the method further comprises:

The terminal device decrypts the downlink data received from the first access network device according to the security context in the context.
The method according to claim 14 or 15, wherein the second information is a paging message, and the paging message includes the downlink data.
The method according to claim 14 or 15, wherein the terminal device receiving the second information from the first access network device comprises:

The terminal device receives the second information from the first access network device at a paging occasion of receiving a paging message, the second information further includes scheduling information, and the scheduling information is used to schedule the downlink data Or, the second information is the scheduling information.
The method according to claim 14 or 15, wherein the second information is a paging message, and the paging message further includes scheduling information, and the scheduling information is used to schedule the downlink data.
A communication device, characterized by comprising a unit for executing each step of the method according to any one of claims 1 to 8, or 9 to 13, or 14 to 18.
A communication device, characterized by comprising at least one processor and an interface circuit, the at least one processor being used to execute the method according to any one of claims 1 to 8, or 9 to 13, or 14 to 18 .
A storage medium, characterized in that a program is stored in the storage medium, and when the program is run by a processor, the method according to any one of claims 1 to 18 is executed.
A computer program product, including instructions, which, when run on a device for transmitting data, causes a communication device to execute the method described in any one of claims 1 to 18.