WO2020034229A1 - 一种信息传输方法及装置、通信设备 - Google Patents

一种信息传输方法及装置、通信设备 Download PDF

Info

Publication number
WO2020034229A1
WO2020034229A1 PCT/CN2018/101204 CN2018101204W WO2020034229A1 WO 2020034229 A1 WO2020034229 A1 WO 2020034229A1 CN 2018101204 W CN2018101204 W CN 2018101204W WO 2020034229 A1 WO2020034229 A1 WO 2020034229A1
Authority
WO
WIPO (PCT)
Prior art keywords
rrc
message
release message
terminal
base station
Prior art date
Application number
PCT/CN2018/101204
Other languages
English (en)
French (fr)
Inventor
王淑坤
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN201880074947.3A priority Critical patent/CN111373783A/zh
Priority to EP18930082.5A priority patent/EP3731552B1/en
Priority to AU2018437006A priority patent/AU2018437006A1/en
Priority to PCT/CN2018/101204 priority patent/WO2020034229A1/zh
Priority to CN202010560354.7A priority patent/CN111787525A/zh
Priority to SG11202008494PA priority patent/SG11202008494PA/en
Priority to JP2020545294A priority patent/JP2022501842A/ja
Priority to KR1020207024551A priority patent/KR20210045349A/ko
Priority to TW108129380A priority patent/TW202021323A/zh
Publication of WO2020034229A1 publication Critical patent/WO2020034229A1/zh
Priority to US16/936,244 priority patent/US20200351977A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H04W12/037—Protecting confidentiality, e.g. by encryption of the control plane, e.g. signalling traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/041—Key generation or derivation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/106—Packet or message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the embodiments of the present application relate to the field of mobile communication technologies, and in particular, to an information transmission method and device, and a communication device.
  • the network side configures a radio access network (RAN, Radio Access Network) paging area for user equipment (UE) in an inactive state.
  • RAN Radio Access Network
  • UE user equipment
  • the UE needs to perform periodic location update according to the period configured by the network.
  • RRC Radio Resource Control
  • the UE needs to resume radio resource control (RRC, Radio Resource Control) connection.
  • RRC Radio Resource Control
  • the network side may not migrate the terminal context (UE context) to the target base station, which can reduce the signaling load inside the network side.
  • the original base station that originally stored the UE context requests the terminal context failure message, and then passes the encapsulated RRC release message to the target base station, and the target base station forwards the encapsulated message to the UE.
  • the target base station delivers the encapsulated RRC release message to the UE is a problem that needs to be solved.
  • the embodiments of the present application provide an information transmission method and device, and a communication device.
  • the first base station After receiving the RRC recovery request message sent by the terminal, the first base station sends a terminal context request message to the second base station;
  • a request terminal context failure message sent by the second base station receives, by the first base station, a request terminal context failure message sent by the second base station, the request terminal context failure message including an RRC release message and associated information of the RRC release message, and the associated information of the RRC release message includes transmission Information and / or safety information;
  • a first receiving unit configured to receive an RRC recovery request message sent by a terminal
  • a first sending unit configured to send a request for a terminal context request message to a second base station
  • a second receiving unit is configured to receive a request terminal context failure message sent by the second base station, where the request terminal context failure message includes an RRC release message and association information of the RRC release message, and the association information of the RRC release message Including transmission and / or security information;
  • a second sending unit is configured to send the RRC release message to the terminal based on the associated information of the RRC release message.
  • the communication device provided in the embodiment of the present application includes 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 stored in the memory to execute the foregoing information transmission method.
  • the chip provided in the embodiment of the present application is used to implement the foregoing information transmission method.
  • the chip includes a processor for invoking and running a computer program from a memory, so that a device installed with the chip executes the foregoing information transmission method.
  • the computer-readable storage medium provided in the embodiments of the present application is used to store a computer program, and the computer program causes a computer to execute the foregoing information transmission method.
  • the computer program product provided in the embodiment of the present application includes computer program instructions, and the computer program instructions cause a computer to execute the foregoing information transmission method.
  • the computer program provided in the embodiment of the present application when run on a computer, causes the computer to execute the foregoing information transmission method.
  • the RRC recovery process is implemented without the terminal context being transferred.
  • the target base station that is, the first base station
  • FIG. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a RAN paging area according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of an information transmission method according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of an RRC recovery process performed between nodes according to an embodiment of the present application.
  • FIG. 5 is a schematic structural composition diagram of an information transmission device according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a communication system according to an embodiment of the present application.
  • GSM Global System for Mobile
  • CDMA Code Division Multiple Access
  • Wideband Code Division Multiple Access Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or a communication terminal or a terminal).
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located within the coverage area.
  • the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system.
  • BTS Base Transceiver Station
  • NodeB NodeB
  • the network device may be a mobile switching center, relay station, access point, vehicle equipment, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in public land mobile networks (PLMN) that will evolve in the future.
  • PLMN public land mobile networks
  • the communication system 100 further includes at least one terminal device 120 located within a coverage area of the network device 110.
  • terminal equipment used herein includes, but is not limited to, connection via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection ; And / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and / or another terminal device configured to receive / transmit communication signals; and / or Internet of Things (IoT) devices.
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Line
  • WLAN Wireless Local Area Networks
  • DVB-H Digital Video Broadband
  • satellite networks satellite networks
  • AM- FM broadcast transmitter AM- FM broadcast transmitter
  • IoT Internet of Things
  • a terminal device configured to communicate through a wireless interface may be referred to as a “wireless communication terminal”, a “wireless terminal”, or a “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular phones; personal communications systems (PCS) terminals that can combine cellular radiotelephones with data processing, facsimile, and data communications capabilities; can include radiotelephones, pagers, Internet / internal PDA with network access, web browser, notepad, calendar, and / or Global Positioning System (GPS) receiver; and conventional laptop and / or palm-type receivers or others including radiotelephone transceivers Electronic device.
  • PCS personal communications systems
  • GPS Global Positioning System
  • a terminal device can refer to an access terminal, user equipment (User Equipment), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or User device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Processing (PDA), and wireless communication.
  • terminal devices 120 may perform terminal direct device (D2D) communication.
  • D2D terminal direct device
  • the 5G system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.
  • NR New Radio
  • FIG. 1 exemplarily shows one network device and two terminal devices.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. The embodiment does not limit this.
  • the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like in this embodiment of the present application is not limited thereto.
  • network entities such as a network controller, a mobility management entity, and the like in this embodiment of the present application is not limited thereto.
  • the device having a communication function in the network / system in the embodiments of the present application may be referred to as a communication device.
  • the communication device may include a network device 110 and a terminal device 120 having a communication function, and the network device 110 and the terminal device 120 may be specific devices described above, and are not described herein again.
  • the communication device may also include other devices in the communication system 100, such as other network entities such as a network controller, a mobile management entity, and the like, which is not limited in the embodiments of the present application.
  • 3GPP 3rd Generation Partnership Project 3rd Generation Partnership Project international standard organization began Five (5G, 5 th Generation) mobile communication technology.
  • the technical solution of the embodiment of the present invention is mainly applied to a 5G mobile communication system.
  • the technical solution of the embodiment of the present invention is not limited to the 5G mobile communication system, and can also be applied to other types of mobile communication systems.
  • eMBB targets users to obtain multimedia content, services, and data, and its business demand is growing rapidly. Because eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., and its service capabilities and requirements vary widely, it is necessary to analyze services in conjunction with specific deployment scenarios.
  • URLLC scenario Typical applications of URLLC include: industrial automation, electric power automation, telemedicine operations, and traffic safety assurance.
  • mMTC scenario The typical characteristics of URLLC include: high connection density, small amount of data, delay-insensitive services, low cost of modules, and long service life.
  • RRC_INACTIVE a new RRC state is defined, that is, the RRC_INACTIVE state. This state is different from the RRC_IDLE and RRC_ACTIVE (that is, RRC_CONNECTED) states.
  • RRC_IDLE Mobility is UE-based cell selection reselection, paging is initiated by the CN, and paging area is configured by the CN. There is no UE AS context on the base station side. There is no RRC connection.
  • RRC_CONNECTED There is an RRC connection, and there is a UE AS context between the base station and the UE. The network knows that the location of the UE is at a specific cell level. Mobility is the mobility controlled by the network side. Unicast data can be transmitted between the UE and the base station.
  • Mobility is UE-based cell selection reselection, there is a connection between CN-NR, UE AS context exists on a certain base station, paging is triggered by RAN, RAN-based paging area is managed by RAN, network side knows The location of the UE is based on the paging area level of the RAN.
  • the network side configures the UE with a paging area of the RAN through dedicated signaling, and the RAN paging area may be one cell or multiple cells.
  • the RAN paging area may be one cell or multiple cells.
  • the UE moves in the area, it does not need to notify the network side, and follows the mobility behavior under idle, that is, the cell selection reselection principle.
  • the UE moves out of the paging area configured by the RAN, the UE will be triggered to resume the RRC connection and reacquire the paging area configured by the RAN.
  • the gNB maintaining the connection between the RAN and the CN for the UE will trigger all cells in the RAN paging area to send a paging message to the UE, so that the UE in the INACTIVCE state can restore the RRC connection for data reception.
  • the UE enters the RRC_CONNECTED state from the RRC_IINACTIVE state. There are three cases:
  • the network side initiates the initial paging of the RAN, prompting the UE to enter the connected state.
  • the UE itself initiates RAN location area update, such as periodic RAN location update or cross-region location update.
  • RAN location area update such as periodic RAN location update or cross-region location update.
  • the third is that the UE has an uplink data sending demand, which prompts the UE to enter a connected state.
  • the UE in the inactive state is configured with a RAN paging area.
  • the UE needs to perform periodic location update according to the period configured by the network.
  • the UE resumes the RRC connection.
  • the network side may not migrate the UE context to the target base station, which reduces the signaling load inside the network side.
  • FIG. 3 is a schematic flowchart of an information transmission method according to an embodiment of the present application. As shown in FIG. 3, the information transmission method includes the following steps:
  • Step 301 After receiving the RRC recovery request message sent by the terminal, the first base station sends a terminal context request message to the second base station.
  • the first base station refers to the target base station
  • the second base station refers to the original base station storing the terminal context.
  • the types of the first base station and the second base station may be the same or different.
  • the first base station is an LTE base station
  • the second base station is an NR base station
  • both the first base station and the second base station are NR base stations.
  • the first base station after receiving the RRC recovery request message sent by the terminal, the first base station addresses the second base station according to the first user identifier carried in the RRC recovery request message, and sends the second base station to the second base station.
  • the base station sends a request terminal context request message.
  • the first user identifier carried in the RRC recovery request message is the I-RNTI allocated by the second base station to the terminal.
  • the request terminal context request message carries at least one of the following:
  • First indication information where the first indication information is used to indicate that the purpose of the current RRC recovery process is periodic location update.
  • the requesting terminal context request message is used to verify the MAC-I carried in the requesting terminal context request message after the second base station receives the requesting terminal context request message. Based on the first information, it is determined whether to perform the RRC recovery process without terminal context transfer, and in the case of determining the RRC recovery process without terminal context transfer, sending a request for terminal context failure message to the first base station.
  • the first information includes at least one of the following:
  • the first indication information carried in the request terminal context request message where the first indication information is used to indicate that the purpose of the current RRC recovery process is a periodic location update
  • Step 302 The first base station receives a request terminal context failure message sent by the second base station, where the request terminal context failure message includes an RRC release message and association information of the RRC release message, and the association of the RRC release message Information includes transmission information and / or security information.
  • the information included in the request terminal context failure message may have the following situations:
  • the requesting terminal context failure message includes: an RRC release message, a secret key, an algorithm, configuration information of SRB1, and indication information for indicating an RRC state to be entered by the terminal;
  • the requesting terminal context failure message includes: an RRC release message, a PDCP PDU corresponding to the RRC release message, configuration information of SRB1, and indication information for indicating an RRC status of the terminal to be entered;
  • the requesting terminal context failure message includes: an RRC release message, a TB block corresponding to the RRC release message, and indication information used to indicate an RRC state to be entered by the terminal.
  • Step 303 The first base station sends the RRC release message to the terminal based on the associated information of the RRC release message.
  • the first base station sends the RRC release message to the terminal based on the associated information of the RRC release message, which may have the following situations:
  • Case 1 The first base station establishes SRB1 based on the configuration information of SRB1, and performs encryption and integrity protection processing on the RRC release message based on the secret key and algorithm, and sends the RRC release message using the SRB1;
  • Case 2 the first base station establishes SRB1 based on the configuration information of SRB1, and uses the SRB1 to send a PDCP PDU corresponding to the RRC release message;
  • Case 3 The first base station sends an TB block corresponding to the RRC release message by using SRB0.
  • the terminal decodes the recovered SRB1 to obtain an RRC release message, and according to the configuration information in the RRC release message Update the configuration and enter the corresponding RRC state; 2) If the RRC release message is sent on the SRB0 as a container, the terminal obtains the TB data in the container on the SRB0 and restores the The SRB1 configuration information of the RRC release message decodes the RRC release message, updates the configuration and enters the corresponding RRC state according to the configuration information in the RRC release message.
  • the key on the second node side is generated based on the following methods:
  • the new key is generated based on the PCI and ARFCN of the second base station; or the new key is generated based on the PCI and ARFCN of the first base station.
  • the input parameters may be the PCI and ARFCN of the second base station, or the PCI and ARFCN of the first base station.
  • the second base station after the second base station generates a new key, it may be carried in the above request terminal context failure message and sent to the first base station, corresponding to the above case 1, that the request terminal context failure message includes: an RRC release message, a secret key, Algorithm, configuration information of SRB1, and indication information used to indicate the RRC state to be entered by the terminal.
  • the second base station uses the new key to encrypt the RRC release message, and then sends the message to the first base station by requesting the terminal context failure message.
  • the RRC connection restoration process of the UE context not being migrated includes:
  • the UE initiates an RRC connection recovery process, and initiates an RRC Recovery Request (RRCResumeRequest) message to the target base station.
  • RRC Recovery Request RRCResumeRequest
  • the key on the UE side can be updated in the following ways:
  • Method 1 The UE calculates a new key based on the physical cell identifier (PCI) of the target base station and the absolute radio channel number (ARFCN, Absolute Radio Frequency Channel Number).
  • PCI physical cell identifier
  • ARFCN Absolute Radio Frequency Channel Number
  • the new key can be used for MSG3 and MSG4. Or just for MSG4.
  • Method 2 The UE calculates a new key based on the PCI and ARFCN of the original base station (anchor base station).
  • the new key can be used for MSG3 and MSG4, or only used for MSG4.
  • the target base station After receiving the RRCResumeRequest message, the target base station addresses the original base station according to the I-RNTI carried in the message, and initiates the UE context request process to the original base station, that is, the target base station sends a request terminal context request message to the original base station .
  • the RETRIEVE UE CONTEXT REQUEST message carries a reason value for initiating the RRC recovery process, or adds an indication information, which is used to indicate that the purpose of the current RRC recovery process is a periodic location update.
  • the original base station After receiving the RETRIEVE UE CONTEXT REQUEST message, the original base station first determines the legitimacy of the UE according to the MAC-I information. Then, it is judged whether or not to perform the RRC connection recovery process in which the UE context is not transferred. The basis of the decision may be the indication or cause value in RETRIEVE UE CONTEXT REQUEST, or the location update timer timeout information, or whether there is downlink data arrival. The original base station decides not to transfer the UE context, then updates the secret key, and generates an RRC Recovery (RRCRelease) message to the UE. The original base station returns a RETRIEVE UE CONTEXT FAILURE message to the target base station, and carries the RRCRelease message.
  • RRCRelease RRC Recovery
  • the content contained in the RETRIEVE UE CONTEXT FAILURE message can be implemented in the following ways:
  • Method 1 Include the RRCRelease message and the configuration information of the key, algorithm, and SRB1. Further, it includes a command indicating a future RRC state of the UE;
  • Method 2 including the PDCP PDU corresponding to the RRCRelease message, and the SRB1 configuration information (or RLC and MAC, physical channel configuration information); further, a command indicating the RRC state that the UE will enter in the future;
  • Method 3 Include a Transport Block (TB) block corresponding to the RRCRelease message; further, include a command indicating the RRC state that the UE will enter in the future.
  • TB Transport Block
  • the target base station After receiving the RRCRelease message related information contained in the RETRIEVE UE CONTEXT FAILURE message, the target base station knows that the UE has performed a location update process without context transfer. Then the target base station: (corresponds to the first, second, and third methods in the above steps)
  • Method 1 Establish SRB1, encrypt and protect the RRCRelease message, and send RRC release message using SRB1.
  • Method 2 Establish SRB1, and use the SRB1 to transmit the PDCP PDU data of the RRCRelease message.
  • the TB data is transmitted through SRB0.
  • the SRB0 message may be an RRCrelease message or an RRCReject message.
  • the UE decodes the data on the recovered SRB1 to obtain an RRC Release message, and updates the configuration and enters the corresponding RRC state according to the configuration information in the message.
  • the UE receives a message on SRB0 and the message contains a container containing the RRCRelease message generated by the original base station, the UE obtains the TB data in the container and decodes the RRCRelease according to the restored SRB1 configuration information And according to the configuration information in the message, update the configuration and enter the corresponding RRC state.
  • the original base station can actively initiate an NCC and NH requesting updates from the AMF.
  • FIG. 5 is a schematic structural composition diagram of an information transmission device according to an embodiment of the present application. As shown in FIG. 5, the device includes:
  • a first receiving unit 501 configured to receive an RRC recovery request message sent by a terminal
  • a first sending unit 502 configured to send a terminal context request message to a second base station
  • a second receiving unit 503 is configured to receive a request terminal context failure message sent by the second base station, where the request terminal context failure message includes an RRC release message and association information of the RRC release message, and the association of the RRC release message Information includes transmission information and / or security information;
  • a second sending unit 504 is configured to send the RRC release message to the terminal based on the associated information of the RRC release message.
  • the first sending unit 502 addresses the first receiving unit according to the first user identifier carried in the RRC recovery request message. Two base stations, and sending a request terminal context request message to the second base station.
  • the request terminal context request message carries at least one of the following:
  • First indication information where the first indication information is used to indicate that the purpose of the current RRC recovery process is periodic location update.
  • the requesting terminal context request message is used to verify the MAC-I carried in the requesting terminal context request message after the second base station receives the requesting terminal context request message, and verify Based on the first information, it is determined whether to perform the RRC recovery process without terminal context transfer, and in the case of determining the RRC recovery process without terminal context transfer, sending a request for terminal context failure message to the first base station.
  • the first information includes at least one of the following:
  • the first indication information carried in the request terminal context request message where the first indication information is used to indicate that the purpose of the current RRC recovery process is a periodic location update
  • the requesting terminal context failure message includes:
  • RRC release message secret key, algorithm, configuration information of SRB1, and indication information used to indicate the RRC status of the terminal to enter;
  • RRC release message PDCP PDU corresponding to RRC release message, configuration information of SRB1, and indication information used to indicate the RRC status of the terminal to enter;
  • the RRC release message, the TB block corresponding to the RRC release message, and indication information used to indicate the RRC state to be entered by the terminal are the RRC release message, the TB block corresponding to the RRC release message, and indication information used to indicate the RRC state to be entered by the terminal.
  • the device further includes an establishment unit and / or a security processing unit;
  • the establishment unit establishes SRB1 based on the configuration information of SRB1, the security processing unit performs encryption and integrity protection processing on the RRC release message based on the key and algorithm, and the second sending unit 504 sends the SRB1 using the SRB1 RRC release message; or,
  • the establishing unit establishes SRB1 based on the configuration information of SRB1, and the second sending unit 504 uses the SRB1 to send a PDCP PDU corresponding to the RRC release message; or,
  • the second sending unit 504 sends the TB block corresponding to the RRC release message by using SRB0.
  • the RRC release message is used by the terminal after receiving the RRC release message
  • the terminal decodes the recovered SRB1 to obtain an RRC release message, and updates the configuration and enters the corresponding RRC state according to the configuration information in the RRC release message;
  • the terminal obtains the TB data in the container on the SRB0, and decodes the RRC release message according to the restored SRB1 configuration information.
  • the configuration information in the RRC release message updates the configuration and enters the corresponding RRC state.
  • the key on the second node side is generated based on the following methods:
  • the new key is generated based on the PCI and ARFCN of the second base station; or the new key is generated based on the PCI and ARFCN of the first base station.
  • FIG. 6 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application.
  • the communication device may be a terminal device or a network device (such as the target base station or the original base station described in the embodiment of the present application).
  • the communication device 600 shown in FIG. A computer program is run to implement the method in the embodiment of the present application.
  • the communication device 600 may further include a memory 620.
  • the processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.
  • the memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.
  • the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and specifically, may send information or data to other devices, or receive other Information or data sent by the device.
  • the processor 610 may control the transceiver 630 to communicate with other devices, and specifically, may send information or data to other devices, or receive other Information or data sent by the device.
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include antennas, and the number of antennas may be one or more.
  • the communication device 600 may specifically be a network device according to the embodiment of the present application, and the communication device 600 may implement a corresponding process implemented by the network device in each method of the embodiment of the present application. For brevity, details are not described herein again. .
  • the communication device 600 may specifically be a mobile terminal / terminal device according to the embodiment of the present application, and the communication device 600 may implement a corresponding process implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, for simplicity , Will not repeat them here.
  • FIG. 7 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 700 shown in FIG. 7 includes a processor 710, and the processor 710 may call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the chip 700 may further include a memory 720.
  • the processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.
  • the memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.
  • the chip 700 may further include an input interface 730.
  • the processor 710 may control the input interface 730 to communicate with other devices or chips. Specifically, the processor 710 may obtain information or data sent by the other devices or chips.
  • the chip 700 may further include an output interface 740.
  • the processor 710 may control the output interface 740 to communicate with other devices or chips. Specifically, the processor 710 may output information or data to the other devices or chips.
  • the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding process implemented by the mobile terminal / terminal device in each method of the embodiments of the present application. For simplicity, here No longer.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-level chip, a system chip, a chip system or a system-on-chip.
  • FIG. 8 is a schematic block diagram of a communication system 900 according to an embodiment of the present application. As shown in FIG. 8, the communication system 900 includes a terminal device 910 and a network device 920.
  • the terminal device 910 may be used to implement the corresponding functions implemented by the terminal device in the foregoing method
  • the network device 920 may be used to implement the corresponding functions implemented by the network device in the foregoing method.
  • details are not described herein again. .
  • the processor in the embodiment of the present application may be an integrated circuit chip and has a signal processing capability.
  • each step of the foregoing method embodiment may be completed by using an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the above processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (Field, Programmable Gate Array, FPGA), or other Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • Various methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like.
  • the storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the foregoing method in combination with its hardware.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), and an electronic memory. Erase programmable read-only memory (EPROM, EEPROM) or flash memory.
  • the volatile memory may be Random Access Memory (RAM), which is used as an external cache.
  • RAM Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • Synchronous Dynamic Random Access Memory Synchronous Dynamic Random Access Memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double SDRAM, DDR SDRAM enhanced synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM synchronous connection dynamic random access memory
  • Synchronous DRAM Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM Enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory Synchrobus RAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (Double SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct RAMbus RAM, DR RAM) and so on. That is, the memories in the embodiments of the present application are intended to include, but not limited to, these and any other suitable types of memories.
  • An embodiment of the present application further provides a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application. For simplicity, here No longer.
  • the computer-readable storage medium may be applied to the mobile terminal / terminal device in the embodiment of the present application, and the computer program causes the computer to execute a corresponding process implemented by the mobile terminal / terminal device in each method in the embodiment of the present application For the sake of brevity, I won't repeat them here.
  • An embodiment of the present application further provides a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instruction causes the computer to execute a corresponding process implemented by the network device in each method in the embodiment of the present application. More details.
  • the computer program product can be applied to a mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute a corresponding process implemented by the mobile terminal / terminal device in each method in the embodiments of the present application, For brevity, I will not repeat them here.
  • the embodiment of the present application also provides a computer program.
  • the computer program may be applied to a network device in the embodiment of the present application.
  • the computer program When the computer program is run on a computer, the computer is caused to execute a corresponding process implemented by the network device in each method in the embodiment of the present application. , Will not repeat them here.
  • the computer program may be applied to a mobile terminal / terminal device in the embodiment of the present application.
  • the computer program When the computer program is run on a computer, the computer executes each method in the embodiment of the application by the mobile terminal / terminal device. The corresponding processes are not repeated here for brevity.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of this application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory) ROM, random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes .

Landscapes

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

Abstract

本申请实施例提供一种信息传输方法及装置、通信设备，包括：第一基站接收到终端发送的RRC恢复请求消息后，向第二基站发送索要终端上下文请求消息；所述第一基站接收所述第二基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息包括RRC释放消息以及所述RRC释放消息的关联信息，所述RRC释放消息的关联信息包括传输信息和/或安全信息；所述第一基站基于所述RRC释放消息的关联信息，向所述终端发送所述RRC释放消息。

Description

一种信息传输方法及装置、通信设备 技术领域
本申请实施例涉及移动通信技术领域，具体涉及一种信息传输方法及装置、通信设备。
背景技术
网络侧对处于非激活(inactive)状态的用户设备(UE，User Equipment)，配置了无线接入网(RAN，Radio Access Network)寻呼区域，在该RAN区域内为了保证UE的可达性，UE需要按照网络配置的周期进行周期性位置更新。当进行周期位置更新时，UE需要恢复无线资源控制(RRC，Radio Resource Control)连接，此时网络侧可能不迁移终端上下文(UE上下文)到目标基站，从而可以降低网络侧内部的信令负荷。
原来存储UE上下文的原基站通过索要终端上下文失败消息，将封装好的RRC释放消息传递给目标基站，目标基站转发该封装好的消息给UE。但是，目标基站如何下发该封装好的RRC释放消息给UE是需要解决的问题。
发明内容
本申请实施例提供一种信息传输方法及装置、通信设备。
本申请实施例提供的信息传输方法，包括：
第一基站接收到终端发送的RRC恢复请求消息后，向第二基站发送索要终端上下文请求消息；
所述第一基站接收所述第二基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息包括RRC释放消息以及所述RRC释放消息的关联信息，所述RRC释放消息的关联信息包括传输信息和/或安全信息；
所述第一基站基于所述RRC释放消息的关联信息，向所述终端发送所述RRC释放消息。
本申请实施例提供的信息传输装置，包括：
第一接收单元，用于接收到终端发送的RRC恢复请求消息后；
第一发送单元，用于向第二基站发送索要终端上下文请求消息；
第二接收单元，用于接收所述第二基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息包括RRC释放消息以及所述RRC释放消息的关联信息，所述RRC释放消息的关联信息包括传输信息和/或安全信息；
第二发送单元，用于基于所述RRC释放消息的关联信息，向所述终端发送所述RRC释放消息。
本申请实施例提供的通信设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述的信息传输方法。
本申请实施例提供的芯片，用于实现上述的信息传输方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安 装有该芯片的设备执行上述的信息传输方法。
本申请实施例提供的计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述的信息传输方法。
本申请实施例提供的计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述的信息传输方法。
本申请实施例提供的计算机程序，当其在计算机上运行时，使得计算机执行上述的信息传输方法。
通过上述技术方案，实现了在终端上下文不进行转移的情况下进行RRC恢复过程，在这个过程中，目标基站(也即第一基站)基于RRC释放消息的关联信息，向所述终端发送所述RRC释放消息，从而保证了终端的配置信息安全可靠的进行更新。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1为本申请实施例提供的一种通信系统架构的示意性图；
图2为本申请实施例提供的RAN寻呼区域的示意图；
图3为本申请实施例提供的信息传输方法的流程示意图；
图4为本申请实施例提供的各节点间执行RRC恢复过程的示意图；
图5为本申请实施例提供的信息传输装置的结构组成示意图；
图6为本申请实施例提供的一种通信设备示意性结构图；
图7为本申请实施例的芯片的示意性结构图；
图8为本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统或5G系统等。
示例性的，本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110，网络设备110可以是与终端设备120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。可选地，该网络设备110可以是GSM系统或CDMA系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网 络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
该通信系统100还包括位于网络设备110覆盖范围内的至少一个终端设备120。作为在此使用的“终端设备”包括但不限于经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network，WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一终端设备的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线接口通信的终端设备可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话；可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System，PCS)终端；可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System，GPS)接收器的PDA；以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端设备可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
可选地，终端设备120之间可以进行终端直连(Device to Device，D2D)通信。
可选地，5G系统或5G网络还可以称为新无线(New Radio，NR)系统或NR网络。
图1示例性地示出了一个网络设备和两个终端设备，可选地，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
可选地，该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端设备120，网络设备110和终端设备120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
为了满足人们对业务的速率、延迟、高速移动性、能效的追求，以及未来生活中业务的多样性、复杂性，第三代合作伙伴计划(3GPP，3rd Generation Partnership Project)国际标准组织开始研发第五代(5G，5 th Generation)移动通信技术。
本发明实施例的技术方案主要应用于5G移动通信系统，当然，本发明实施例的技术方案并不局限于5G移动通信系统，还可以应用于其他类型的移动通信系统。以下对 5G移动通信系统中的主要应用场景进行说明：
1)eMBB场景：eMBB以用户获得多媒体内容、服务和数据为目标，其业务需求增长十分迅速。由于eMBB可能部署在不同的场景中，例如室内、市区、农村等，其业务能力和需求的差别也比较大，所以必须结合具体的部署场景对业务进行分析。
2)URLLC场景：URLLC的典型应用包括：工业自动化、电力自动化、远程医疗操作、交通安全保障等。
3)mMTC场景：URLLC的典型特点包括：高连接密度、小数据量、时延不敏感业务、模块的低成本和长使用寿命等。
5G网络环境中为了降低空口信令和快速恢复无线连接，快速恢复数据业务的目的，定义一个新的RRC状态，即RRC_INACTIVE状态。这种状态有别于RRC_IDLE和RRC_ACTIVE(也即RRC_CONNECTED)状态。
RRC_IDLE：移动性为基于UE的小区选择重选，寻呼由CN发起，寻呼区域由CN配置。基站侧不存在UE AS上下文。不存在RRC连接。
RRC_CONNECTED：存在RRC连接，基站和UE存在UE AS上下文。网络侧知道UE的位置是具体小区级别的。移动性是网络侧控制的移动性。UE和基站之间可以传输单播数据。
RRC_INACTIVE：移动性为基于UE的小区选择重选，存在CN-NR之间的连接，UE AS上下文存在某个基站上，寻呼由RAN触发，基于RAN的寻呼区域由RAN管理，网络侧知道UE的位置是基于RAN的寻呼区域级别的。
参照图2，当UE处于RRC_INACTIVE状态，网络侧会通过专用信令给UE配置RAN的寻呼区域，该RAN寻呼区域可以是一个小区或者多个小区。当UE在该区域内移动时不用通知网络侧，遵循idle下移动性行为，即小区选择重选原则。当UE移动出RAN配置的寻呼区域时，会触发UE恢复RRC连接并重新获取RAN配置的寻呼区域。当UE有下行数据到达时，为UE保持RAN和CN之间连接的gNB会触发RAN寻呼区域内的所有小区发送寻呼消息给UE，使得INACTIVCE状态的UE能够恢复RRC连接，进行数据接收。
UE从RRC_IINACTIVE状态进入RRC_CONNECTED状态，有三种情况：
一是，UE有下行数据到达，网络侧发起RAN初始的寻呼，促使UE进入连接状态。
二是，UE自身发起RAN位置区域更新，例如周期性RAN位置更新或者跨区域位置更新。
三是，UE有上行数据发送需求，促使UE进入连接状态。
处于inactive状态的UE，配置了RAN寻呼区域，在该区域内为了保证UE的可达性，UE需要按照网络配置的周期进行周期性位置更新。当进行周期位置更新时，UE恢复RRC连接，此时网络侧可能不迁移UE上下文到目标基站，这样降低了网络侧内部的信令负荷。
图3为本申请实施例提供的信息传输方法的流程示意图，如图3所示，所述信息传输方法包括以下步骤：
步骤301：第一基站接收到终端发送的RRC恢复请求消息后，向第二基站发送索要终端上下文请求消息。
本申请实施例中，第一基站是指目标基站，第二基站是指存储终端上下文的原基站，第一基站和第二基站的类型可以相同，也可以不同。例如第一基站为LTE基站，第二基站为NR基站，或者，第一基站和第二基站都是NR基站。
本申请实施例中，所述第一基站接收到终端发送的RRC恢复请求消息后，根据所述RRC恢复请求消息中携带的第一用户标识寻址所述第二基站，并向所述第二基 站发送索要终端上下文请求消息。
这里，所述RRC恢复请求消息中携带的第一用户标识，该第一用户标识为第二基站为终端分配的I-RNTI。
在一实施方式中，所述索要终端上下文请求消息中携带以下至少之一：
发起RRC恢复过程的原因值；
第一指示信息，所述第一指示信息用于指示当前RRC恢复过程的目的是周期性位置更新。
本申请实施例中，所述索要终端上下文请求消息用于在所述第二基站接收到所述索要终端上下文请求消息后，对所述索要终端上下文请求消息中携带的MAC-I进行验证，验证通过后基于第一信息确定是否进行终端上下文不转移的RRC恢复过程，在确定进行终端上下文不转移的RRC恢复过程情况下，向所述第一基站发送索要终端上下文失败消息。
进一步，所述第一信息包括以下至少之一：
所述索要终端上下文请求消息中携带的发起RRC恢复过程的原因值；
所述索要终端上下文请求消息中携带的第一指示信息，所述第一指示信息用于指示当前RRC恢复过程的目的是周期性位置更新；
位置更新定时器超时信息；
是否存在下行数据到达的指示信息。
步骤302：所述第一基站接收所述第二基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息包括RRC释放消息以及所述RRC释放消息的关联信息，所述RRC释放消息的关联信息包括传输信息和/或安全信息。
本申请实施例中，所述索要终端上下文失败消息中所包括的信息可以具有如下几种情况：
情况一：所述索要终端上下文失败消息包括：RRC释放消息、秘钥、算法、SRB1的配置信息、用于指示终端待进入的RRC状态的指示信息；
情况二：所述索要终端上下文失败消息包括：RRC释放消息、RRC释放消息对应的PDCP PDU、SRB1的配置信息、用于指示终端待进入的RRC状态的指示信息；
情况三：所述索要终端上下文失败消息包括：RRC释放消息、RRC释放消息对应的TB块、用于指示终端待进入的RRC状态的指示信息。
步骤303：所述第一基站基于所述RRC释放消息的关联信息，向所述终端发送所述RRC释放消息。
本申请实施例中，所述第一基站基于所述RRC释放消息的关联信息，向所述终端发送所述RRC释放消息，可以具有如下几种情况：
情况一：所述第一基站基于SRB1的配置信息建立SRB1，并基于所述秘钥和算法对RRC释放消息进行加密和完整性保护处理，利用所述SRB1发送所述RRC释放消息；
情况二：所述第一基站基于SRB1的配置信息建立SRB1，并利用所述SRB1发送所述RRC释放消息对应的PDCP PDU；
情况三：所述第一基站利用SRB0发送所述RRC释放消息对应的TB块。
本申请实施例的上述方案中，1)如果所述RRC释放消息是利用所述SRB1发送，则所述终端在恢复的SRB1上解码获得RRC释放消息，并按照所述RRC释放消息中的配置信息更新配置以及进入对应的RRC状态；2)如果所述RRC释放消息以容器container的方式在所述SRB0上发送，则所述终端在所述SRB0上获得所述container中的TB数据，并按照恢复的SRB1配置信息解码RRC释放消息，按照所述RRC释放消息中的配置信息更新配置以及进入对应的RRC状态。
本申请实施例的上述方案中，所述第二节点侧的秘钥基于以下方式生成：
1)基于原秘钥衍生新秘钥；
2)基于新NCC对应的NH生成新秘钥，其中，所述NCC为所述第二节点向核心网主动索要获得。
进一步，所述新秘钥基于所述第二基站的PCI和ARFCN生成；或者，所述新秘钥基于所述第一基站的PCI和ARFCN生成。这里，在通过以上任意一种方式生成新秘钥时，输入的参数可以是第二基站的PCI和ARFCN，也可以是第一基站的PCI和ARFCN。
这里，第二基站生成新秘钥后，可以携带在上述索要终端上下文失败消息中发送给第一基站，对应上述情况一，即：所述索要终端上下文失败消息包括：RRC释放消息、秘钥、算法、SRB1的配置信息、用于指示终端待进入的RRC状态的指示信息。或者，第二基站利用新秘钥对RRC释放消息进行加密，再通过索要终端上下文失败消息发送给所述第一基站。
以下参照图4所示的网络架构对本申请实施例的技术方案进行举例说明。
参照图4，UE上下文不迁移的RRC连接恢复过程包括：
1、UE发起RRC连接恢复过程，向目标基站发起RRC恢复请求(RRCResumeRequest)消息。
本步骤中，UE侧的秘钥可以通过以下方式更新：
方式一：UE基于目标基站的物理小区标识(PCI，Physical Cell Identifier)和绝对无线频道编号(ARFCN，Absolute Radio Frequency Channel Number)计算新的秘钥，该新的秘钥可以用于MSG3和MSG4，或者只用于MSG4。
方式二：UE基于原基站(锚点基站)的PCI和ARFCN计算新的秘钥，该新的秘钥可以用于MSG3和MSG4，或者只用于MSG4。
2、目标基站收到RRCResumeRequest消息之后，根据该消息中携带的I-RNTI寻址原基站，并向原基站发起UE上下文索要过程，即目标基站向原基站发送索要终端上下文请求(RETRIEVE UE CONTEXT REQUEST)消息。
可选地，RETRIEVE UE CONTEXT REQUEST消息中携带发起RRC恢复过程的原因值，或者添加一个指示信息，该指示信息用于指示当前RRC恢复过程的目的是周期性位置更新。
3、原基站收到RETRIEVE UE CONTEXT REQUEST消息之后，首先根据MAC-I信息判断UE的合法性。然后，判决是否进行UE上下文不转移的RRC连接恢复过程。判决的依据可以是RETRIEVE UE CONTEXT REQUEST中的指示或者原因值，或者位置更新定时器超时信息，或者是否存在下行数据到达。原基站判决不转移UE上下文，则更新秘钥，并产生给UE的RRC恢复(RRCRelease)消息。原基站给目标基站回复索要终端上下文失败(RETRIEVE UE CONTEXT FAILURE)消息，并携带该RRCRelease消息。
其中，RETRIEVE UE CONTEXT FAILURE消息中包含的内容可以通过以下方式实现：
方式一：包括RRCRelease消息以及秘钥、算法和SRB1的配置信息。进一步，包括指示UE的未来进入的RRC状态的命令；
方式二：包括RRCRelease消息对应的PDCP PDU，以及SRB1配置信息(或者RLC和MAC，物理信道配置信息)；进一步，包括指示UE的未来进入的RRC状态的命令；
方式三：包括RRCRelease消息对应的传输块(TB，Transport Block)块；进一步，包括指示UE的未来进入的RRC状态的命令。
4、目标基站收到RETRIEVE UE CONTEXT FAILURE消息中包含的RRCRelease消息相关信息后，知道UE进行了不进行上下文转移的位置更新过程。则目标基站：(对应上述步骤中的方式一、方式二、方式三)
方式一：建立SRB1，并对RRCRelease消息进行加密和完整性保护，利用SRB1发送RRC release消息。
方式二：建立SRB1，利用SRB1传输RRCRelease消息的PDCP PDU数据。
方式三：通过SRB0传输TB数据，该SRB0的消息可以是RRCrelease消息或者RRCReject消息。
5、UE收到RRC Release消息之后。
对应步骤4中的方式一和方式二，UE在恢复的SRB1上解码数据获取RRC Release消息，并按照消息中的配置信息更新配置和进入对应的RRC状态。
对应步骤4中的方式三，如果UE在SRB0上收到消息，且消息中含有包含原基站生成的RRCRelease消息container，则UE获取container中的TB数据，并按照恢复的SRB1配置信息，解码RRCRelease，并按照消息中的配置信息更新配置和进入对应的RRC状态。
6、原基站执行完UE的RRC连接恢复过程中，例如没有上下文获取，不触发路径变更(Path switch)过程，则原基站可以主动发起向AMF索要更新的NCC以及NH。
图5为本申请实施例提供的信息传输装置的结构组成示意图，如图5所示，所述装置包括：
第一接收单元501，用于接收到终端发送的RRC恢复请求消息后；
第一发送单元502，用于向第二基站发送索要终端上下文请求消息；
第二接收单元503，用于接收所述第二基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息包括RRC释放消息以及所述RRC释放消息的关联信息，所述RRC释放消息的关联信息包括传输信息和/或安全信息；
第二发送单元504，用于基于所述RRC释放消息的关联信息，向所述终端发送所述RRC释放消息。
在一实施方式中，所述第一接收单元501接收到终端发送的RRC恢复请求消息后，所述第一发送单元502根据所述RRC恢复请求消息中携带的第一用户标识寻址所述第二基站，并向所述第二基站发送索要终端上下文请求消息。
在一实施方式中，所述索要终端上下文请求消息中携带以下至少之一：
发起RRC恢复过程的原因值；
第一指示信息，所述第一指示信息用于指示当前RRC恢复过程的目的是周期性位置更新。
在一实施方式中，所述索要终端上下文请求消息用于在所述第二基站接收到所述索要终端上下文请求消息后，对所述索要终端上下文请求消息中携带的MAC-I进行验证，验证通过后基于第一信息确定是否进行终端上下文不转移的RRC恢复过程，在确定进行终端上下文不转移的RRC恢复过程情况下，向所述第一基站发送索要终端上下文失败消息。
在一实施方式中，所述第一信息包括以下至少之一：
所述索要终端上下文请求消息中携带的发起RRC恢复过程的原因值；
所述索要终端上下文请求消息中携带的第一指示信息，所述第一指示信息用于指示当前RRC恢复过程的目的是周期性位置更新；
位置更新定时器超时信息；
是否存在下行数据到达的指示信息。
在一实施方式中，所述索要终端上下文失败消息包括：
RRC释放消息、秘钥、算法、SRB1的配置信息、用于指示终端待进入的RRC状态的指示信息；或者，
RRC释放消息、RRC释放消息对应的PDCP PDU、SRB1的配置信息、用于指示终端待进入的RRC状态的指示信息；或者，
RRC释放消息、RRC释放消息对应的TB块、用于指示终端待进入的RRC状态的指示信息。
在一实施方式中，所述装置还包括建立单元和/或安全处理单元；
所述建立单元基于SRB1的配置信息建立SRB1，所述安全处理单元基于所述秘钥和算法对RRC释放消息进行加密和完整性保护处理，所述第二发送单元504利用所述SRB1发送所述RRC释放消息；或者，
所述建立单元基于SRB1的配置信息建立SRB1，所述第二发送单元504利用所述SRB1发送所述RRC释放消息对应的PDCP PDU；或者，
所述第二发送单元504利用SRB0发送所述RRC释放消息对应的TB块。
在一实施方式中，所述RRC释放消息用于所述终端在收到所述RRC释放消息后，
如果所述RRC释放消息是利用所述SRB1发送，则所述终端在恢复的SRB1上解码获得RRC释放消息，并按照所述RRC释放消息中的配置信息更新配置以及进入对应的RRC状态；
如果所述RRC释放消息以容器container的方式在所述SRB0上发送，则所述终端在所述SRB0上获得所述container中的TB数据，并按照恢复的SRB1配置信息解码RRC释放消息，按照所述RRC释放消息中的配置信息更新配置以及进入对应的RRC状态。
在一实施方式中，所述第二节点侧的秘钥基于以下方式生成：
1)基于原秘钥衍生新秘钥；
2)基于新NCC对应的NH生成新秘钥，其中，所述NCC为所述第二节点向核心网主动索要获得。
进一步，所述新秘钥基于所述第二基站的PCI和ARFCN生成；或者，所述新秘钥基于所述第一基站的PCI和ARFCN生成。
本领域技术人员应当理解，本申请实施例的上述信息传输装置的相关描述可以参照本申请实施例的信息传输方法的相关描述进行理解。
图6是本申请实施例提供的一种通信设备600示意性结构图。该通信设备可以是终端设备，也可以是网络设备(如本申请实施例上述的目标基站或原基站)，图6所示的通信设备600包括处理器610，处理器610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图6所示，通信设备600还可以包括存储器620。其中，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器620可以是独立于处理器610的一个单独的器件，也可以集成在处理器610中。
可选地，如图6所示，通信设备600还可以包括收发器630，处理器610可以控制该收发器630与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备600具体可为本申请实施例的网络设备，并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再 赘述。
可选地，该通信设备600具体可为本申请实施例的移动终端/终端设备，并且该通信设备600可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
图7是本申请实施例的芯片的示意性结构图。图7所示的芯片700包括处理器710，处理器710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图7所示，芯片700还可以包括存储器720。其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
可选地，该芯片700还可以包括输入接口730。其中，处理器710可以控制该输入接口730与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片700还可以包括输出接口740。其中，处理器710可以控制该输出接口740与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的移动终端/终端设备，并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图8是本申请实施例提供的一种通信系统900的示意性框图。如图8所示，该通信系统900包括终端设备910和网络设备920。
其中，该终端设备910可以用于实现上述方法中由终端设备实现的相应的功能，以及该网络设备920可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random  Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的移动终端/终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (25)

  1. 一种信息传输方法，所述方法包括：
    第一基站接收到终端发送的RRC恢复请求消息后，向第二基站发送索要终端上下文请求消息；
    所述第一基站接收所述第二基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息包括RRC释放消息以及所述RRC释放消息的关联信息，所述RRC释放消息的关联信息包括传输信息和/或安全信息；
    所述第一基站基于所述RRC释放消息的关联信息，向所述终端发送所述RRC释放消息。
  2. 根据权利要求1所述的方法，其中，所述第一基站接收到终端发送的RRC恢复请求消息后，向第二基站发送索要终端上下文请求消息，包括：
    所述第一基站接收到终端发送的RRC恢复请求消息后，根据所述RRC恢复请求消息中携带的第一用户标识寻址所述第二基站，并向所述第二基站发送索要终端上下文请求消息。
  3. 根据权利要求1或2所述的方法，其中，所述索要终端上下文请求消息中携带以下至少之一：
    发起RRC恢复过程的原因值；
    第一指示信息，所述第一指示信息用于指示当前RRC恢复过程的目的是周期性位置更新。
  4. 根据权利要求3所述的方法，其中，所述索要终端上下文请求消息用于在所述第二基站接收到所述索要终端上下文请求消息后，对所述索要终端上下文请求消息中携带的MAC-I进行验证，验证通过后基于第一信息确定是否进行终端上下文不转移的RRC恢复过程，在确定进行终端上下文不转移的RRC恢复过程情况下，向所述第一基站发送索要终端上下文失败消息。
  5. 根据权利要求4所述的方法，其中，所述第一信息包括以下至少之一：
    所述索要终端上下文请求消息中携带的发起RRC恢复过程的原因值；
    所述索要终端上下文请求消息中携带的第一指示信息，所述第一指示信息用于指示当前RRC恢复过程的目的是周期性位置更新；
    位置更新定时器超时信息；
    是否存在下行数据到达的指示信息。
  6. 根据权利要求1至5任一项所述的方法，其中，所述索要终端上下文失败消息包括：
    RRC释放消息、秘钥、算法、SRB1的配置信息、用于指示终端待进入的RRC状态的指示信息；或者，
    RRC释放消息、RRC释放消息对应的PDCP PDU、SRB1的配置信息、用于指示终端待进入的RRC状态的指示信息；或者，
    RRC释放消息、RRC释放消息对应的TB块、用于指示终端待进入的RRC状态的指示信息。
  7. 根据权利要求6所述的方法，其中，所述第一基站基于所述RRC释放消息的关联信息，向所述终端发送所述RRC释放消息，包括：
    所述第一基站基于SRB1的配置信息建立SRB1，并基于所述秘钥和算法对RRC释放消息进行加密和完整性保护处理，利用所述SRB1发送所述RRC释放消息；或者，
    所述第一基站基于SRB1的配置信息建立SRB1，并利用所述SRB1发送所述RRC释放消息对应的PDCP PDU；或者，
    所述第一基站利用SRB0发送所述RRC释放消息对应的TB块。
  8. 根据权利要求7所述的方法，其中，所述RRC释放消息用于所述终端在收到所述RRC释放消息后，
    如果所述RRC释放消息是利用所述SRB1发送，则所述终端在恢复的SRB1上解码获得RRC释放消息，并按照所述RRC释放消息中的配置信息更新配置以及进入对应的RRC状态；
    如果所述RRC释放消息以容器container的方式在所述SRB0上发送，则所述终端在所述SRB0上获得所述container中的TB数据，并按照恢复的SRB1配置信息解码RRC释放消息，按照所述RRC释放消息中的配置信息更新配置以及进入对应的RRC状态。
  9. 根据权利要求1至8任一项所述的方法，其中，所述第二节点侧的秘钥基于以下方式生成：
    基于原秘钥衍生新秘钥；或者，
    基于新NCC对应的NH生成新秘钥，其中，所述NCC为所述第二节点向核心网主动索要获得。
  10. 根据权利要求9所述的方法，其中，
    所述新秘钥基于所述第二基站的PCI和ARFCN生成；或者，
    所述新秘钥基于所述第一基站的PCI和ARFCN生成。
  11. 一种信息传输装置，所述装置包括：
    第一接收单元，用于接收到终端发送的RRC恢复请求消息后；
    第一发送单元，用于向第二基站发送索要终端上下文请求消息；
    第二接收单元，用于接收所述第二基站发送的索要终端上下文失败消息，所述索要终端上下文失败消息包括RRC释放消息以及所述RRC释放消息的关联信息，所述RRC释放消息的关联信息包括传输信息和/或安全信息；
    第二发送单元，用于基于所述RRC释放消息的关联信息，向所述终端发送所述RRC释放消息。
  12. 根据权利要求11所述的装置，其中，所述第一接收单元接收到终端发送的RRC恢复请求消息后，所述第一发送单元根据所述RRC恢复请求消息中携带的第一用户标识寻址所述第二基站，并向所述第二基站发送索要终端上下文请求消息。
  13. 根据权利要求11或12所述的装置，其中，所述索要终端上下文请求消息中携带以下至少之一：
    发起RRC恢复过程的原因值；
    第一指示信息，所述第一指示信息用于指示当前RRC恢复过程的目的是周期性位置更新。
  14. 根据权利要求13所述的装置，其中，所述索要终端上下文请求消息用于在所述第二基站接收到所述索要终端上下文请求消息后，对所述索要终端上下文请求消息中携带的MAC-I进行验证，验证通过后基于第一信息确定是否进行终端上下文不转移的RRC恢复过程，在确定进行终端上下文不转移的RRC恢复过程情况下，向所述第一基站发送索要终端上下文失败消息。
  15. 根据权利要求14所述的装置，其中，所述第一信息包括以下至少之一：
    所述索要终端上下文请求消息中携带的发起RRC恢复过程的原因值；
    所述索要终端上下文请求消息中携带的第一指示信息，所述第一指示信息用于指 示当前RRC恢复过程的目的是周期性位置更新；
    位置更新定时器超时信息；
    是否存在下行数据到达的指示信息。
  16. 根据权利要求11至15任一项所述的装置，其中，所述索要终端上下文失败消息包括：
    RRC释放消息、秘钥、算法、SRB1的配置信息、用于指示终端待进入的RRC状态的指示信息；或者，
    RRC释放消息、RRC释放消息对应的PDCP PDU、SRB1的配置信息、用于指示终端待进入的RRC状态的指示信息；或者，
    RRC释放消息、RRC释放消息对应的TB块、用于指示终端待进入的RRC状态的指示信息。
  17. 根据权利要求16所述的装置，其中，所述装置还包括建立单元和/或安全处理单元；
    所述建立单元基于SRB1的配置信息建立SRB1，所述安全处理单元基于所述秘钥和算法对RRC释放消息进行加密和完整性保护处理，所述第二发送单元利用所述SRB1发送所述RRC释放消息；或者，
    所述建立单元基于SRB1的配置信息建立SRB1，所述第二发送单元利用所述SRB1发送所述RRC释放消息对应的PDCP PDU；或者，
    所述第二发送单元利用SRB0发送所述RRC释放消息对应的TB块。
  18. 根据权利要求17所述的装置，其中，所述RRC释放消息用于所述终端在收到所述RRC释放消息后，
    如果所述RRC释放消息是利用所述SRB1发送，则所述终端在恢复的SRB1上解码获得RRC释放消息，并按照所述RRC释放消息中的配置信息更新配置以及进入对应的RRC状态；
    如果所述RRC释放消息以容器container的方式在所述SRB0上发送，则所述终端在所述SRB0上获得所述container中的TB数据，并按照恢复的SRB1配置信息解码RRC释放消息，按照所述RRC释放消息中的配置信息更新配置以及进入对应的RRC状态。
  19. 根据权利要求11至18任一项所述的装置，其中，所述第二节点侧的秘钥基于以下方式生成：
    基于原秘钥衍生新秘钥；或者，
    基于新NCC对应的NH生成新秘钥，其中，所述NCC为所述第二节点向核心网主动索要获得。
  20. 根据权利要求19所述的装置，其中，
    所述新秘钥基于所述第二基站的PCI和ARFCN生成；或者，
    所述新秘钥基于所述第一基站的PCI和ARFCN生成。
  21. 一种通信设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至10中任一项所述的方法。
  22. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至10中任一项所述的方法。
  23. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至10中任一项所述的方法。
  24. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机 执行如权利要求1至10中任一项所述的方法。
  25. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至10中任一项所述的方法。
PCT/CN2018/101204 2018-08-17 2018-08-17 一种信息传输方法及装置、通信设备 WO2020034229A1 (zh)

Priority Applications (10)

Application Number Priority Date Filing Date Title
CN201880074947.3A CN111373783A (zh) 2018-08-17 2018-08-17 一种信息传输方法及装置、通信设备
EP18930082.5A EP3731552B1 (en) 2018-08-17 2018-08-17 Information transmission method and apparatus, and communication device
AU2018437006A AU2018437006A1 (en) 2018-08-17 2018-08-17 Information transmission method and apparatus, and communication device
PCT/CN2018/101204 WO2020034229A1 (zh) 2018-08-17 2018-08-17 一种信息传输方法及装置、通信设备
CN202010560354.7A CN111787525A (zh) 2018-08-17 2018-08-17 一种信息传输方法及装置、通信设备
SG11202008494PA SG11202008494PA (en) 2018-08-17 2018-08-17 Information transmission method and apparatus, and communication device
JP2020545294A JP2022501842A (ja) 2018-08-17 2018-08-17 情報伝送方法、装置及び通信デバイス
KR1020207024551A KR20210045349A (ko) 2018-08-17 2018-08-17 정보 전송 방법, 장치 및 통신 디바이스
TW108129380A TW202021323A (zh) 2018-08-17 2019-08-16 一種訊息傳輸方法及裝置、通信設備
US16/936,244 US20200351977A1 (en) 2018-08-17 2020-07-22 Information transmission method and apparatus, and communication device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/101204 WO2020034229A1 (zh) 2018-08-17 2018-08-17 一种信息传输方法及装置、通信设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/936,244 Continuation US20200351977A1 (en) 2018-08-17 2020-07-22 Information transmission method and apparatus, and communication device

Publications (1)

Publication Number Publication Date
WO2020034229A1 true WO2020034229A1 (zh) 2020-02-20

Family

ID=69524550

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/101204 WO2020034229A1 (zh) 2018-08-17 2018-08-17 一种信息传输方法及装置、通信设备

Country Status (9)

Country Link
US (1) US20200351977A1 (zh)
EP (1) EP3731552B1 (zh)
JP (1) JP2022501842A (zh)
KR (1) KR20210045349A (zh)
CN (2) CN111787525A (zh)
AU (1) AU2018437006A1 (zh)
SG (1) SG11202008494PA (zh)
TW (1) TW202021323A (zh)
WO (1) WO2020034229A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114828158A (zh) * 2021-01-22 2022-07-29 大唐移动通信设备有限公司 信息传输方法、装置、基站及介质

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107295578B (zh) * 2016-03-30 2020-01-21 中兴通讯股份有限公司 一种无线通信方法和设备
US11805453B2 (en) * 2020-07-02 2023-10-31 Qualcomm Incorporated Security key in layer 1 (L1) and layer 2 (L2) based mobility
CN113905457B (zh) * 2020-07-06 2023-08-08 维沃移动通信有限公司 消息发送方法、接收方法、装置及通信设备
CN116210336A (zh) * 2020-07-31 2023-06-02 Oppo广东移动通信有限公司 一种密钥生成方法及装置、终端设备、网络设备
CN114126046B (zh) * 2020-08-31 2023-02-24 大唐移动通信设备有限公司 用于基站的通信控制方法、装置、基站及存储介质
CN113132924B (zh) * 2021-04-19 2022-01-21 北京达源环保科技有限公司 用于高部署密度的污泥厌氧消化监测终端的信息传输方法及系统
CN114051288B (zh) * 2021-09-28 2023-07-18 浪潮软件科技有限公司 终端状态变更控制方法及装置
WO2023146357A1 (en) * 2022-01-29 2023-08-03 Samsung Electronics Co., Ltd. Method, base station, electronic apparatus and storage medium for supporting multicast transmission
CN117014790A (zh) * 2022-04-29 2023-11-07 华为技术有限公司 通信方法以及通信装置
CN115397040A (zh) * 2022-08-12 2022-11-25 西安广和通无线通信有限公司 数据链路恢复方法、装置、电子设备、存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107295515A (zh) * 2016-04-01 2017-10-24 北京三星通信技术研究有限公司 一种支持基站间用户设备ue上下文恢复的方法及装置
CN107959953A (zh) * 2018-01-08 2018-04-24 创新维度科技（北京）有限公司 跨接窄带物联网基站的rrc连接恢复方法、基站、终端和系统
CN108307452A (zh) * 2016-08-12 2018-07-20 展讯通信（上海）有限公司 连接恢复方法及装置、基站、用户终端

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11201956B2 (en) * 2017-01-05 2021-12-14 Nokia Technologies Oy Inactive state security support in wireless communications system
US10624150B2 (en) * 2017-01-30 2020-04-14 FG Innovation Company Limited Radio resource control connection resume method of wireless communication system
CN110249703B (zh) * 2017-02-03 2023-08-08 瑞典爱立信有限公司 无上下文取得的无线电资源控制恢复

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107295515A (zh) * 2016-04-01 2017-10-24 北京三星通信技术研究有限公司 一种支持基站间用户设备ue上下文恢复的方法及装置
CN108307452A (zh) * 2016-08-12 2018-07-20 展讯通信（上海）有限公司 连接恢复方法及装置、基站、用户终端
CN107959953A (zh) * 2018-01-08 2018-04-24 创新维度科技（北京）有限公司 跨接窄带物联网基站的rrc连接恢复方法、基站、终端和系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
See also references of EP3731552A4 *
VIVO: "Security aspects in RRC re-establishment procedure", 3GPP TSG-RAN WG2 MEETING #103 R2-1811771, vol. RAN WG2, 10 August 2018 (2018-08-10), XP051521410 *
ZTE ET AL.: "Consideration on periodic RAN area update procedure", 3GPP TSG-RAN WG2 MEETING#100 R2-172615, 1 December 2017 (2017-12-01), XP051371192 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114828158A (zh) * 2021-01-22 2022-07-29 大唐移动通信设备有限公司 信息传输方法、装置、基站及介质
CN114828158B (zh) * 2021-01-22 2024-04-05 大唐移动通信设备有限公司 信息传输方法、装置、基站及介质

Also Published As

Publication number Publication date
CN111787525A (zh) 2020-10-16
SG11202008494PA (en) 2020-10-29
TW202021323A (zh) 2020-06-01
AU2018437006A1 (en) 2020-09-24
KR20210045349A (ko) 2021-04-26
US20200351977A1 (en) 2020-11-05
EP3731552B1 (en) 2022-08-03
JP2022501842A (ja) 2022-01-06
EP3731552A1 (en) 2020-10-28
EP3731552A4 (en) 2021-07-07
CN111373783A (zh) 2020-07-03

Similar Documents

Publication Publication Date Title
WO2020034229A1 (zh) 一种信息传输方法及装置、通信设备
US11304054B2 (en) Communication method and device
WO2021203310A1 (zh) 一种数据传输方法及装置、终端设备
WO2021000331A1 (zh) 一种数据传输方法及装置、通信设备
US20220061075A1 (en) Information transmission method and apparatus, and network device
US20220015177A1 (en) Method of connection reestablishment, terminal device, and non-transitory computer-readable storage medium
JP7213950B2 (ja) 情報構成方法および装置、端末、ネットワーク機器
US11805563B2 (en) Wireless communication method and base station
WO2022061872A1 (zh) 一种小数据传输方法及装置、终端设备
CN113796118A (zh) 一种切换方法及装置、通信设备
WO2020082247A1 (zh) 一种安全算法的处理方法及装置、终端
US11653407B2 (en) Information transmission method and apparatus, and terminal and network device
CN112715038B (zh) 一种参数配置方法及装置、网络设备
WO2020034125A1 (zh) 一种恢复rrc连接的方法及装置、终端
CN112313979B (zh) 一种信息传输方法及装置、网络设备
WO2020155157A1 (zh) 切换过程中安全信息的处理方法及装置、网络设备、终端
WO2020223972A1 (zh) 一种无线资源控制消息的处理方法、设备及存储介质
WO2021203400A1 (zh) 一种传输策略的配置方法及装置、网络设备、终端设备
WO2020258182A1 (zh) 数据传输方法、装置和通信设备
WO2021062756A1 (zh) 无线通信方法、装置和网络设备

Legal Events

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

Ref document number: 18930082

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018930082

Country of ref document: EP

Effective date: 20200721

ENP Entry into the national phase

Ref document number: 2020545294

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018437006

Country of ref document: AU

Date of ref document: 20180817

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE