WO2022147671A1 - 一种通信方法和装置 - Google Patents

一种通信方法和装置 Download PDF

Info

Publication number
WO2022147671A1
WO2022147671A1 PCT/CN2021/070385 CN2021070385W WO2022147671A1 WO 2022147671 A1 WO2022147671 A1 WO 2022147671A1 CN 2021070385 W CN2021070385 W CN 2021070385W WO 2022147671 A1 WO2022147671 A1 WO 2022147671A1
Authority
WO
WIPO (PCT)
Prior art keywords
context information
information
message
rrc
rrc connection
Prior art date
Application number
PCT/CN2021/070385
Other languages
English (en)
French (fr)
Inventor
冯淑兰
刘俊
常俊仁
张亮亮
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2021/070385 priority Critical patent/WO2022147671A1/zh
Priority to CN202180086394.5A priority patent/CN116648992A/zh
Publication of WO2022147671A1 publication Critical patent/WO2022147671A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • 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 present application relates to the field of communication, and more particularly, to a communication method and apparatus.
  • the terminal device in order to transmit data, the terminal device needs to establish a radio resource control (RRC) connection with the access network device to realize data transmission.
  • RRC radio resource control
  • the access network device will temporarily delete the context information related to the terminal data transmission.
  • the terminal device needs to transmit data packets, it needs to re-establish the RRC connection and re-establish the context information related to the terminal data transmission. , a large amount of signaling needs to be transmitted to establish a new connection, and the transmission efficiency is reduced.
  • the present application provides a communication method and apparatus for saving system overhead.
  • a communication method comprising: a second device acquiring first context information of the second device from a first device, where the first context information includes a first context information between the first device and the second device All or part of the configuration information of the RRC connection, the first device is the serving cell of the second device; the second device receives the RRC message; in response to the RRC message, the second device maintains the first context information; the second device The device sends an RRC connection establishment request message, where the RRC connection establishment request message includes first indication information, where the first indication information is used to instruct the second device to keep the first context information; and/or the second device receives the RRC configuration message , the RRC configuration message includes second indication information, and the second indication information is used to instruct the second device to establish a second RRC connection according to the first context information, and the RRC configuration message includes an RRC connection establishment message and an RRC connection re-establishment message. , at least one of the RRC connection reconfiguration messages.
  • the second device receives the indication information sent by the first device, and the second device saves the first context information according to the indication information, that is to say, the second device can keep the first context information according to the RRC message.
  • a context information, the first context information can also be maintained according to a separate indication information.
  • the second device obtains the first context information of the connection between the second device and the first device (that is, all or part of the configuration information when the first device and the second device establish the first RRC connection), and the first The second device and the first device maintain the first context information when releasing or updating the connection, and the second device and the device to be accessed can perform an RRC process through the first context information.
  • the RRC process here includes but is not limited to the RRC establishment process, One or more of the RRC reestablishment process, the RRC reconfiguration process, the RRC recovery process, the RRC redirection process, the handover process, and the RRC reset process), thereby avoiding the need to transmit relevant context information and consuming a lot of signaling when the RRC process is repeated. , to improve transmission efficiency.
  • the second device stores first context information, where the first context information includes part or all of the first RRC connection between the first device and the second device configuration information; the second device releases or reconfigures the first RRC connection; the second device establishes a second RRC connection with the first device according to the first configuration information; The configuration information establishes a third RRC connection with the third device.
  • the second device may send indication information to the first device, where the indication information is used to instruct the first device to save the first context information and release or reconfigure it RRC connection.
  • the context information may be part or all of the configuration information that the first device instructs the second device to save when the second device historically accesses the first device, or the second device determines to keep the current context information and notifies the first device Keep current context information.
  • the second device ie, the terminal device
  • the first device can save the first context information and release or reconfigure the RRC connection, that is to say, the action of saving the first context information can be initiated by the terminal device, or can be Initiated by the access network device, thereby instructing the second device and the first device to keep the first context information when releasing or updating the connection, and the second device and the device to be accessed can perform an RRC process through the first context information, where the The RRC process includes but is not limited to one or more of the RRC setup process, the RRC re-establishment process, the RRC reconfiguration process, the RRC recovery process, the RRC redirection process, the handover process, and the RRC reset process), so that it is possible to avoid re-performing the RRC process When it is necessary to transmit relevant context information, a large amount of signaling is consumed and the transmission efficiency is improved.
  • the second device in response to the RRC message, maintains the first context information, including: the RRC message is an RRC connection release message, and in response to the RRC connection release message, the second device keeps the first context information and the second device enters an idle state; or, the RRC message is an RRC connection reconfiguration message, and in response to the RRC connection reconfiguration message, the second device keeps the first context information and the second device leaves the first device.
  • the second device obtains the first context information when the first device is in a connected state, and the second device receives the RRC message sent by the first device.
  • the received RRC message may be an RRC connection release message, or may be a RRC connection reconfiguration message, when receiving the RRC connection release message, after the second device keeps the first context information, the second device disconnects the RRC connection with the first device and enters the idle state; when receiving the RRC connection reconfiguration message message, after the second device keeps the first context information, the second device disconnects the connection with the first device and leaves the current serving cell, and may access other cells.
  • the first context information includes a cell identity of the first device, a device identity of the second device, a radio access network area (RAN) of the first device At least one of the Area) identifier and the information identifier of the first context.
  • RAN radio access network area
  • the method before the second device sends the RRC connection establishment request message, the method further includes: the second device determines whether the second device is based on the cell identifier of the first device The first context information of the first device is retained; the second device sends an RRC connection establishment request message to the first device.
  • the first device and the second device after the first device and the second device retain the first context information, they can determine whether to retain the context information of the first device according to the cell identity of the first device in the first context information, so as to ensure that the first device retains the context information.
  • the RRC connection establishment request information is sent, so as to ensure that the first device must keep the context information, further ensuring that the context information is effective when performing the RRC process, and improving the efficiency of the RRC process.
  • the method further includes: the second device reporting third indication information to the first device, where the third indication information is used to indicate that the second device has an The ability to keep the first context information in an idle state or after leaving the first device.
  • the second device before reporting the third indication information to the first device, the second device further includes: the second device receives request information sent by the first device, where the request information is used to request the second device to report that the device is in an idle state and/or Or the ability to retain the first context information after leaving the first device.
  • the method further includes: receiving, by the second device, fourth indication information sent by the first device, where the fourth indication information is used to indicate whether the first device is It has the ability of the second device to keep the first context information in an idle state and or after the second device leaves the first device.
  • the first device confirms whether the second device has the ability to keep the first context information in an idle state or after leaving the first device, and when it is determined that the second device has the storage capability, performs the first context information save and use the context information for the RRC process.
  • the method before the second device retains the first context information in response to the RRC message, the method further includes: the second device determines that the second device is the The resident device of the first device.
  • the second device determines that the second device is a resident device of the first device according to a first condition, where the first condition, for example, the dwell time of the second device accessing the first device is greater than a certain threshold. For another example, the number of times or the frequency that the second device accesses the first device. For another example, the second device once accessed the first device.
  • the first condition may be determined by the first device or the second device or by a predefined rule.
  • the second device is the resident terminal device of the first device, that is, the access network device and the terminal device perform identification access
  • the access network device only saves the context information of the resident terminal device
  • the resident terminal device Only the context information of the resident access network device is saved, which further saves the storage overhead of the network device and the terminal device.
  • receiving the RRC configuration message by the second device further includes: the first device determines second context information according to the first context information, and the second context information is the same as the second context information.
  • the first context information is at least partially the same; the second device determines the context information of the second RRC connection according to the second context information.
  • the second context information determined by the first device is partially or completely the same as the first context information, and the first indication information may include parts of different information, and the second device does not need to perform all context information with the first device.
  • the context information for the second RRC connection is determined according to the different parts included in the first indication information and the first context information saved by itself, which saves the signaling overhead caused by the context information exchange in the RRC process.
  • a communication method including: a first device acquiring first context information, where the first context information includes all or part of configuration information of a first RRC connection between the first device and the second device, the The first device is the serving cell of the second device; the first device sends an RRC message and retains the first context information, the RRC message is used to instruct the second device to retain the first context information; the first device from the The second device receives an RRC connection establishment request message, where the RRC connection establishment request message includes first indication information, where the first indication information is used to indicate that the second device maintains the first context information; and/or the first device sends RRC configuration message, the RRC configuration message includes second indication information, the second indication information is used to instruct the second device to establish a second RRC connection according to the first context information, the RRC configuration message includes an RRC connection establishment message, an RRC connection At least one of a re-establishment message and an RRC connection reconfiguration message.
  • the first device may send indication information to the second device, where the indication information is used to instruct the second device to save the first context information, that is, the second device may keep the first context information according to the RRC message , the first context information can also be maintained according to a separate indication information.
  • the first device acquires the first context information (that is, all or part of the configuration information when the first device and the second device establish the first RRC connection), and the second device and the first device release or The first context information is maintained when the connection is updated, and the first device and the second device can perform an RRC process through the first context information.
  • the RRC process here includes but is not limited to the RRC establishment process, the RRC reestablishment process, the RRC reconfiguration process, and the RRC process.
  • One or more of the recovery process, the RRC redirection process, and the handover process thereby avoiding the need to transmit relevant context information and consuming a large amount of signaling when re-performing the RRC process, thereby improving transmission efficiency.
  • the first device receives the indication information sent by the second device, and the first device saves the first context information and releases or reconfigures the RRC according to the indication information connect.
  • the context information may be part or all of the configuration information that the first device instructs the second device to save when the second device historically accesses the first device, or the second device determines to keep the current context information and notifies the first device Keep current context information.
  • the RRC message is used to instruct the second device to keep the first context information, including: the RRC message is an RRC connection release message, and the RRC connection release message uses to instruct the second device to keep the first context information and enter an idle state; or, the RRC message is an RRC connection reconfiguration message, and the RRC connection reconfiguration message is used to instruct the second device to keep the first context information and leave the the first device.
  • the RRC message sent by the first device may be an RRC connection release message or an RRC connection reconfiguration message.
  • the second device When receiving the RRC connection release message, after the second device maintains the first context information, the second device The device disconnects the RRC connection with the first device and enters the idle state; when receiving the RRC connection reconfiguration message, after the second device maintains the first context information, the second device disconnects from the first device and leaves the current state. Serving cell, possibly accessing other cells.
  • the first context information includes a cell identifier of the first device, a device identifier of the second device, a radio access network area identifier of the first device, At least one of the information identifiers of the first context.
  • the method before the first device sends the RRC configuration message, the method further includes: the first device according to the device identification of the second device, the information of the first context At least one of the identifications determines whether the first device maintains first context information for the second device.
  • the first device and the second device may determine whether to retain the first context of the second device according to at least one of the device identification of the second device or the information identification of the first context information to ensure that the context information of the second device is retained before sending the RRC configuration message, thereby ensuring that the second device must retain the context information, and further ensuring that the context information is used for the RRC process.
  • RRC process efficiency after the first device and the second device retain the first context information, they may determine whether to retain the first context of the second device according to at least one of the device identification of the second device or the information identification of the first context information to ensure that the context information of the second device is retained before sending the RRC configuration message, thereby ensuring that the second device must retain the context information, and further ensuring that the context information is used for the RRC process.
  • the method further includes: receiving, by the first device, third indication information reported by the second device, where the third indication information is used to indicate that the second device has The ability to retain the first context information in an idle state and or after leaving the first device.
  • the first device before receiving the third indication information reported by the second device, the first device further includes: the first device sends request information to the second device, where the request information is used to request the second device to report that the information is in an idle state and or The ability to retain the first context information after leaving the first device.
  • the method further includes: the first device sending fourth indication information to the second device, where the fourth indication information is used to indicate whether the first device has The ability to maintain the first context information of the second device in an idle state and/or after leaving the first device.
  • the first device confirms whether the second device has the ability to keep the first context information in an idle state or after leaving the first device, and when it is determined that the second device has the storage capability, performs the first context information save and use the context information for the RRC process.
  • the method before the first device retains the first context information, the method includes: the first device determines the second device according to a first condition or a storage capability of the first device is the resident device of the first device.
  • the second device is the resident terminal device of the first device, that is, the access network device and the terminal device perform identification access
  • the access network device only saves the context information of the resident terminal device
  • the resident terminal device Only the context information of the resident access network device is saved, which further saves the storage overhead of the network device and the terminal device.
  • sending the RRC configuration message by the first device further includes: the first device determines second context information according to the first context information, and the second context information is the same as the second context information.
  • the first context information is at least partially the same; the first device determines the context information of the second RRC connection according to the second context information.
  • the second context information determined by the first device is partially or completely the same as the first context information, and the first indication information may include parts of different information, and the second device does not need to perform all context information with the first device.
  • the context information for the second RRC connection is determined according to the different parts included in the first indication information and the first context information saved by itself, which saves the signaling overhead caused by the context information exchange in the RRC process.
  • a communication method including: a third device receiving an RRC connection establishment request message from the second device, where the RRC connection establishment request message includes first indication information, where the first indication information is used to indicate the first indication information
  • the second device maintains the first context information
  • the third device sends an RRC configuration message, where the RRC configuration message includes second indication information, and the second indication information is used to instruct the second device to establish the first context information according to the first context information.
  • the RRC configuration message includes at least one of an RRC connection establishment message, an RRC connection re-establishment message, and an RRC connection reconfiguration message;
  • the first context information includes the first RRC connection between the first device and the second device All or part of the configuration information of the connection, the first device is the historical serving cell of the second device.
  • the first context information of the third device may be stored by the third device, may be acquired from the first device, or may be stored on a server and available for acquisition.
  • the third device can perform an RRC process with the second device through the first context information (the RRC process here includes but is not limited to the RRC establishment process, the RRC reestablishment process, and the RRC reconfiguration process. process, RRC recovery process, RRC redirection process, handover process, and RRC reset process), so as to avoid the need to transmit relevant context information and consume a lot of signaling when re-performing the RRC process, and improve transmission efficiency.
  • the RRC process here includes but is not limited to the RRC establishment process, the RRC reestablishment process, and the RRC reconfiguration process. process, RRC recovery process, RRC redirection process, handover process, and RRC reset process
  • the method before the third device sends the RRC configuration message, the method further includes: the third device according to the first device identifier, the device identifier of the second device, At least one of the radio access network area identifier of the first device and the information identifier of the first context determines the first context information of the second device.
  • the third device sends an RRC configuration message, and the method further includes: the third device determines third context information according to the first context information, the third context The information is at least partially the same as the first context information; the third device determines the context information of the third RRC connection according to the third context information.
  • the third context information determined by the third device is partially or completely the same as the first context information, and the first indication information may include parts of different information, and the third device does not need to perform all context information with the second device.
  • the interaction of the third RRC connection is determined according to the different parts included in the first indication information and the first context information saved or obtained by itself, which saves the signaling caused by the interaction of the context information in the RRC process. overhead.
  • a communication device that executes the elements of the method of the first aspect or various implementations thereof.
  • a communication device that executes the means of the method of the second aspect or various implementations thereof.
  • a communication device that executes the elements of the method of the third aspect or various implementations thereof.
  • a communication device comprising, a processor, and a memory, where 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 communication device executes the first or second or Communication methods in the third aspect and various possible implementations thereof.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • a communication system including one of the above-mentioned first device, second device and third device.
  • a computer program product comprising: a computer program (also referred to as code, or instructions), when the computer program is executed, causes the computer to execute the above-mentioned first aspect, the first The method in any of the possible implementations of the second aspect or the third aspect.
  • a computer-readable medium stores a computer program (also referred to as code, or instruction), when it runs on a computer, causing the computer to execute the above-mentioned first aspect, the first The method in any of the possible implementations of the second aspect or the third aspect.
  • a computer program also referred to as code, or instruction
  • a circuit system including a memory and a processor, the memory is used for storing a computer program, the processor is used for calling and running the computer program from the memory, so that a communication device installed with the circuit system executes
  • the method in any possible implementation manner of the first aspect, the second aspect or the third aspect.
  • the circuit system may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.
  • a twelfth aspect provides a circuit system for executing the method in any possible implementation manner of the first aspect, the second aspect or the third aspect.
  • FIG. 1 shows a schematic diagram of a wireless communication system 100 suitable for an embodiment of the present application.
  • FIG. 2 shows a schematic diagram of another wireless communication system 200 suitable for this embodiment of the present application.
  • FIG. 3 shows a schematic block diagram of a communication method applicable to the embodiment of the present application.
  • FIG. 4 shows a schematic flowchart of a method applicable to the communication provided by this embodiment of the present application.
  • FIG. 5 shows a schematic flowchart of a method suitable for communication provided by another embodiment of the present application.
  • FIG. 6 shows a schematic block diagram of a communication device applicable to the embodiment of the present application.
  • FIG. 7 shows a schematic structural diagram of a communication device applicable to the embodiment of the present application.
  • the wireless communication systems mentioned in the embodiments of the present application include but are not limited to: Long Term Evolution (Long Term Evolution, LTE) system, LTE Frequency Division Duplex (Frequency Division Duplex, FDD) system, LTE Time Division Duplex (Time Division Duplex, TDD) system ), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th Generation (5G) system or New Radio (NR) ), or future communication systems, etc.
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • 5G 5th Generation
  • NR New Radio
  • computer readable media may include, but are not limited to: magnetic storage devices (eg, hard disks, floppy disks, or magnetic tapes, etc.), optical disks (eg, compact discs (CDs), digital versatile discs (DVDs) etc.), smart cards and flash memory devices (eg, erasable programmable read-only memory (EPROM), card, stick or key drives, etc.).
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • 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.
  • FIG. 1 shows a schematic diagram of a wireless communication system 100 according to an embodiment of the present application.
  • the wireless communication system 100 may include at least one configuration node, such as the network device 111 shown in FIG. 1 , and the wireless communication system 100 may also include at least one configured node, such as the terminal device shown in FIG. 1 . 121 to terminal equipment 123. Both the network device and the terminal device can be configured with multiple antennas, and the network device and the terminal device can communicate using the multi-antenna technology.
  • the network device when the network device communicates with the terminal device, the network device can manage one or more cells, and there can be an integer number of terminal devices in one cell.
  • the network device 111 and the terminal device 121 to the terminal device 123 form a single-cell communication system, and without loss of generality, the cell is denoted as cell #1.
  • the network device 111 may be a network device in cell #1, or in other words, the network device 111 may serve a terminal device (eg, terminal device 121) in cell #1.
  • a cell can be understood as an area within the coverage range of a wireless signal of a network device.
  • FIG. 2 shows another schematic diagram of a wireless communication system 200 according to an embodiment of the present application.
  • the wireless communication system 200 may include at least one configuration node, such as the terminal device 211 shown in FIG. 2, and the wireless communication system 200 may also include at least one configured node, such as the terminal device shown in FIG. 2. 221 to terminal equipment 223.
  • Both the network device and the terminal device can be configured with multiple antennas, and the network device and the terminal device can communicate using the multi-antenna technology.
  • the configuration node in the wireless communication system can be any device that has a wireless configuration function to generate wireless resource configuration information for the configuration node, the device can be a network device, or the device can also be a terminal device with a configuration function .
  • the network equipment includes but is not limited to: next generation Node B (gNB) evolved Node B (evolved Node B, eNB), radio network controller (Radio Network Controller, RNC), Node B (Node B, NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (for example, Home evolved NodeB, or Home Node B, HNB), Base Band Unit (BBU) ), access point (Access Point, AP), wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (transmission and reception) in a wireless fidelity (Wireless Fidelity, WIFI) system point, TRP), etc., can also be 5G, such as, NR, gNB in the system, or, transmission
  • the configured node in the wireless communication system may be any device that receives radio resource configuration information sent by the configuration node, and the device may be a terminal device or a configured network device.
  • the terminal equipment may also be referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, User Agent or User Device.
  • UE user equipment
  • the terminal device in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, transportation security ( Wireless terminals in transportation safety), wireless terminals in smart cities, wireless terminals in smart homes, and so on.
  • the embodiments of the present application do not limit application scenarios.
  • the network device and the terminal device restore the RRC connection according to the configuration information.
  • the configuration information is part or all of the configuration information of cell #1 configured by the network device for the terminal device in the RRC connection state.
  • the specific content can be pre-agreed by the network device and the terminal device.
  • the configuration information can be the security-related context of the terminal device, the ROHC (Robust Header Compression) state, and the QoS flow used for the DRB (Data Radio Bear) mapping rule.
  • the service The cell Identity of the PCell of cell #1, the physical layer ID of the serving base station #1, the public configuration of the PSCell Serving Cell Config Common, the serving cell #1 broadcast message Serving Cell Config Common SIB, the serving cell #1 is the terminal
  • the dedicated configuration of the device configuration, Serving Cell Config, etc., is not limited in this embodiment.
  • the access network device #1 is an example of a network device as a configuration node
  • UE#1 is an example of a terminal device as a configured node.
  • the coverage of each network device may be divided into one or more cells, and a cell may be an area within the wireless network coverage of the network device.
  • different network devices may correspond to different cells, such as , the access network device #1 and the access network device #2 manage different cell #1 and cell #2.
  • the configuration node can also be other network elements of the network device or a terminal device with a configuration function
  • the configured node can also be another device of the terminal device or a network device that can be configured.
  • a wireless communication system may include UEs that have the ability to store configuration information and UEs that do not have the ability to store configuration information.
  • the access network device It can be queried whether the UE has the ability to store configuration information.
  • the access network device #1 sends a request message #a to the UE#1, where the request message #a is used to request the UE#1 to report whether it has the capability of storing configuration information.
  • the access network device #1 sends a request message #a to the UE #1, where the request message #a is used to confirm whether the UE has the capability of storing configuration information.
  • the access network device #1 may also send a capability message #b (an example of the fourth indication information) to the UE #1, where the capability message #b is used to indicate to the UE #1 that the access network device #1 has The capability of the UE#1 to store configuration information in an idle state or after the UE#1 leaves the access network device #1, the capability message #b and the request message #a may be the same message or different messages.
  • the access network device #1 may notify the UE #1 that the access network device #1 has the capability of storing configuration information by means of a broadcast message or a multicast message.
  • UE#1 receives request message #a and/or capability message #b, confirms whether it has the ability to store configuration information, and sends a report message #c (an example of third indication information) to access network device #1, the report message # c is used to inform the access network device #1 whether the UE #1 has the capability of storing configuration information in an idle state or after leaving the access network device #1.
  • report message #c an example of third indication information
  • UE#1 may actively send a report message #c (an example of the third indication information) to access network device #1 to inform access network device #1 that UE#1 is in an idle state or leaves access network device #1 Whether it has the ability to store configuration information.
  • a report message #c an example of the third indication information
  • the request message #a may also be referred to as a capability query message.
  • the access network device #1 sends the capability query message to request the UE#1 to report all or part of the capability information of the UE#1.
  • the report message #c is also called capability report information, and includes all or part of the capabilities supported by UE#1. Particularly, for this application, the report message #c may include that the UE #1 has the capability to store configuration information in an idle state or after leaving the access network device #1. If the report message #c does not include that UE#1 has the ability to store configuration information in the idle state or after leaving the access network device #1, it is considered that the UE#1 does not support the storage configuration information in the idle state or after leaving the access network device #1. The ability to configure information.
  • the report message #c may further include that UE#1 has the storage capability of N sets of configuration information, where N is a positive integer greater than or equal to 1, and each set of configuration information corresponds to an access network device to send to the UE# 1 configuration information.
  • Whether the UE#1 has the capability of storing configuration information may further include, among the storage capabilities of N sets of configuration information, remaining storage capabilities. For example, UE#1 has the storage capability to store 5 sets of configuration information. If UE#1 has stored the configuration information of two access network devices, such as the configuration information of access network device #a and the configuration of access network device #b information, access network device #a and access network device #b are different access network devices from access network device #1, then the UE#1 can report that the UE#1 also has 3 sets of configuration information storage ability.
  • Whether the UE#1 has the capability of storing configuration information further, it may indicate whether the UE#1 has the capability of storing the configuration information. For example, UE#1 has the storage capability to store two sets of configuration information. If UE#1 has stored the configuration information of access network device #a and the configuration information of access network device #b, access network device #a and access network device #b have The network device #b is an access network device different from the access network device #1, and then the UE#1 may report that the UE#1 does not have the capability of storing configuration information. For another example, UE#1 has the storage capability of storing two sets of configuration information.
  • access network device #a and Access network device #b is a different access network device from access network device #1, but UE#1 can determine that access network device #1 has a higher priority for storing configuration information than access network device #a or access network device #1. If the storage priority of the configuration information of any one of the devices #b is higher, then UE #1 can report that UE #1 has the ability to store configuration information.
  • RRC procedures including but not limited to RRC establishment procedure, RRC reestablishment procedure, RRC reconfiguration procedure, RRC recovery procedure, RRC redirection procedure, handover procedure, RRC reset procedure one or more of
  • the following mainly performs the RRC process (including but not limited to one of the RRC establishment process, the RRC reestablishment process, the RRC reconfiguration process, the RRC recovery process, the RRC redirection project, the handover process, and the RRC reset process) for the UE with the ability to store configuration information. or more) are described in detail.
  • the terminal device may be a terminal device capable of storing the configuration information, or may be a terminal device that does not have the capability of storing the configuration information.
  • the configuration information may be a terminal device capable of storing the configuration information
  • the capable terminal device is used as the configuration information of the resident terminal device in the resident serving cell, that is to say, the resident network device and the resident terminal device save the configuration information during the RRC connection.
  • the following method may be used as an example:
  • the access network device #1 confirms whether the UE#1 is a resident terminal device. In a possible implementation manner, after the access network device #1 confirms that the UE#1 has the ability to store configuration information, the access network device #1 confirms that the UE#1 is capable of storing configuration information. Whether UE#1 satisfies the first condition is confirmed whether UE#1 is a resident terminal device.
  • the first condition is the rules and parameters determined by the access network device #1. Specifically, the access network device #1 may determine the rules and parameters by counting the dwell time of the UE #1 in the access network device #1.
  • the rule is specifically the time that UE#1 counts on the access network device #1, the dwell time is greater than a certain threshold, and the threshold can be used as a parameter, that is, when UE#1 counts on the device #1.
  • the dwell time of a certain access network device #1 is greater than a certain threshold value, that is, the access network device #1 confirms that the UE#1 satisfies the first condition, then the UE#1 and the access network device #1 are mutually normal Resident terminal equipment and resident network equipment.
  • the rule may also be the access time or frequency at which UE#1 resides on access network device #1, that is, the time or frequency at which the RRC connection is established between UE#1 and access network device #1, or,
  • the rule may also be the number or frequency of data packets transmitted between the UE#1 and the access network device #1, and the rule may also be the number of times the UE#1 accesses the access network device #1 or Frequency
  • the rules and parameters may be pre-specified, such as those defined by the protocol, or may be empirical values determined by the network device according to historical communication conditions. This application does not limit this.
  • the access network device #1 may store configuration information for the UE#1 when releasing or updating the RRC connection
  • the UE#1 may store the access network device #1 when releasing or updating the RRC connection Assigned configuration information.
  • Method 4 The access network device #1 sends a message #d to the UE, where the message #d is used for the UE to determine whether the first condition is met, and the UE that meets the first condition is a resident terminal device.
  • Message #d also includes the following information: Rules and parameters for the first condition.
  • the message #d may be a broadcast message, a multicast message sent to a group of UEs, or a UE-specific message sent to a UE.
  • the message #d also includes a terminal identifier.
  • the UE that has received the message #d determines whether the UE satisfies the first condition according to the rules and parameters of the first condition indicated by the message #d.
  • access network device #1 sends message #d through a broadcast message; or, after access network device #1 confirms that UE #1 has the ability to store configuration information, it sends message #d to UE that has the ability to store configuration information #1, UE#1 confirms whether UE#1 is a resident terminal device by confirming whether UE#1 satisfies the first condition.
  • the access network device #1 sends a message #d to UE#1, the message #d includes the rules and parameters of the first condition, UE#1 confirms whether the first condition is met, and if the first condition is met, the UE#1 is determined is a resident terminal device, in this case, the access network device #1 can store configuration information for the UE#1 when releasing or updating the RRC connection, and the UE#1 can store the access network when releasing or updating the RRC connection Configuration information allocated by network device #1.
  • the first condition is the rules and parameters determined by the access network device #1, and the rules and parameters may be determined by the access network device #1.
  • the rules and parameters are determined by means of the dwell time of access network device #1.
  • the rule is specifically for UE#1 to count the time that UE#1 resides in access network device #1.
  • the dwell time is greater than a certain threshold, and the threshold value can be used as parameter, that is to say, when UE#1 counts that the dwell time of a certain access network device #1 is greater than a certain threshold, that is, the UE#1 confirms that the first condition is met, then the UE#1 and the access network Network access device #1 is a resident terminal device and a resident network device for each other.
  • the rule can also be the access time when UE#1 is camped on the access network device #1, that is, the time when the RRC connection is established between UE#1 and the access network device #1, or the rule can also be is the number or frequency of data packets transmitted between the UE#1 and the access network device #1, the rule can also be the number or frequency of the UE#1 accessing the access network device #1, the rule and
  • the parameters may be pre-specified, such as those defined by the protocol, or may be empirical values determined by the network device according to historical communication conditions. This application does not limit this.
  • the access network device #1 When UE#1 satisfies the first condition, in this case, when releasing or updating the RRC connection, the access network device #1 saves the configuration information of the UE#1, and the UE#1 saves the access network device #1 configuration information, so that the overhead required for storing configuration information can be saved. Further, UE#1 confirms that the first condition is met and sends a report message #e to the access network device #1, where the report message #e is used to report to the access network device #1 that the UE#1 meets the first condition.
  • Method 5 UE#1 confirms whether it is a resident terminal device.
  • UE#1 confirms whether UE#1 is a resident terminal device by judging whether UE#1 satisfies the first condition.
  • the first condition is that the dwell time of UE#1 in the access network device #1 is greater than a first-class threshold.
  • the first condition is the time when the RRC connection is established between UE#1 and access network device #1.
  • the first condition is determined by UE#1 according to a predetermined rule, or determined by UE#1 autonomously.
  • the access network device #1 When UE#1 satisfies the first condition, in this case, when releasing or updating the RRC connection, the access network device #1 saves the configuration information of the UE#1, and the UE#1 saves the access network device #1 configuration information, so that the overhead required for storing configuration information can be saved. Further, UE#1 confirms that the first condition is met and sends a report message #e to the access network device #1, where the report message #e is used to report to the access network device #1 that the UE#1 meets the first condition.
  • Access network device #1 confirms whether UE#1 is a resident terminal device. In a possible implementation manner, access network device #1 confirms whether UE#1 is a resident terminal device according to its own capabilities. Specifically, after confirming that UE#1 has the capability to store configuration information, the access network device #1 determines whether its own storage capability is sufficient, and if it is sufficient, confirms that the UE#1 is a resident terminal. If its own storage capacity is insufficient, it is confirmed that the UE#1 is not a resident terminal. For another example, after confirming that UE#1 has the capability to store configuration information, the access network device #1 determines whether its storage capability is sufficient, and if it is sufficient, confirms that the UE#1 is a resident terminal.
  • the priority of the UE#1 is higher than the priority of any one or more UEs previously stored, and if the priority of the UE#1 is higher than any one or more previously stored UEs If the priority is high, it is confirmed that the UE#1 is a resident terminal, otherwise, it is confirmed that the UE#1 is not a resident terminal.
  • the access network device #1 confirms that the UE#1 is a resident terminal and sends an identification code to the UE#1, the identification code is used to indicate the configuration information allocated by the access network device #1 to the UE#1 .
  • the access network device #1 After receiving the report message #d of UE#1, the access network device #1 confirms that the UE#1 is a resident terminal device, and can store configuration information for the UE#1, The access network device #1 may also assign an identification code to the UE #1.
  • the identification code is used to indicate the configuration information of the RRC connection between the resident network that satisfies the first condition and the resident terminal equipment, or the identification code is used to index the relationship between the resident network that satisfies the first condition and the resident terminal equipment.
  • the identification code may be H-RNTI (History Radio Network Tempory Identity), and the code length of the identification code may be determined according to the storage capability of the access network device #1.
  • the code length of the identification code is greater than or equal to the length of the C-RNTI (Cell RNTI) allocated by the access network device #1 for UE #1 (usually 16 bits), Less than or equal to the length of the I-RNTI (Inactive RNTI) allocated by the access network device #1 for UE #1.
  • H-RNTI is greater than or equal to C-RNTI, considering that the number of first configurations actually stored by access network device #1 will be more than the number of UEs that access network device #1 is in the connected state at the same time, H-RNTI is less than or equal to I-RNTI mainly The consideration is to reduce the length of the H-RNTI to improve the reliability of the transmission.
  • the H-RNTI bit length is between 48 and 56 bits, including 48 and 56 bits. If the access network device #1 has a weak storage capacity in order to save costs, the H-RNTI can be determined according to the actual storage capacity of the access network device #1. If the access network device #1 can only store 128 configuration information , the H-RNTI may be 7 bits. In addition, the access network device #1 can also be determined according to the number of serving terminals. For example, if the access network device can serve 200 terminals at the same time, the code length of the H-RNTI can be close to 200. For example, the H-RNTI can take 8 bits (corresponding to 256 terminals).
  • the access network device #1 and the UE#1 are not in a permanent relationship.
  • the access network device #1 determines that the UE#1 no longer meets the first condition, or the storage of the access network device #1
  • the resident relationship of the low-priority UE#1 can be released, or, when the UE#1 has access network device #1 that is more suitable for storage, the network device #1 is no longer the resident of the terminal device.
  • the network device, or UE#1 is no longer the resident terminal of the access network device #1, UE#1 may not save the configuration information allocated by the access network device, and the access network device #1 may not save the UE#1 configuration information.
  • the terminal equipment and the access network equipment are identified, and the access network equipment can store the configuration information for the resident terminal equipment when releasing or updating the RRC connection, and the resident terminal equipment can store the configuration information when releasing or updating the RRC connection
  • the configuration information allocated by the access network device saves the system overhead caused by the parameter determination in the RRC process of the access network device and the terminal device.
  • FIG. 3 shows a schematic block diagram of a communication method provided by a specific embodiment of the present application.
  • Method 300 may include the following steps.
  • the access network device #1 confirms that the UE#1 has the ability to store configuration information in an idle state or after leaving the access network device #1;
  • access network device #1 confirms whether UE#1 is a resident terminal device
  • the access network device #1 and UE#1 keep the configuration information when releasing or reconfiguring the RRC connection;
  • steps S301 and S302 are optional steps, and the execution of any step or the non-execution of any step does not affect the specific implementation of the embodiments of the present application.
  • step S301 and step S302 Before or after step S301 and step S302, it also includes that the access network device #1 and UE#1 establish a first RRC connection.
  • the terminal device after the terminal device establishes the first RRC connection with the access network device, it maintains the configuration information of the access network device when releasing or updating the connection, regardless of whether the terminal device is disconnected from the access network device
  • the RRC process here includes but is not limited to the RRC establishment process, the RRC reestablishment process, the RRC reconfiguration process, and the RRC recovery process. , one or more of the RRC redirection process, the handover process, and the RRC reset process), the retained configuration information can be used, so the system overhead caused by parameter configuration can be saved.
  • FIG. 4 shows a schematic flowchart of a communication method provided by a specific embodiment of the present application. The method can be applied to the communication systems shown in FIG. 1 and FIG. 2 .
  • the access network device #1 confirms that the UE#1 has the capability of storing configuration information.
  • the access network device #1 confirms whether the UE#1 is a resident terminal device.
  • steps S401 and S402 are optional steps, and the execution of any step or the non-execution of any step does not affect the specific implementation of the embodiments of the present application.
  • step S401 and step S402 Before or after step S401 and step S402, it also includes that the access network device #1 and UE#1 establish a first RRC connection.
  • the access network device #1 and UE#1 keep the configuration information when releasing or reconfiguring the RRC connection. There are two ways to save the configuration information. The first way is as follows:
  • UE#1 acquires configuration information #A (an example of first context information) of UE#1 from access network device #1, where the configuration information #A includes the configuration information #A between the access network device #1 and UE#1 Part or all of the configuration information included in the first RRC connection includes part or all of the configuration information configured for the UE#1 when the access network device #1 establishes the first RRC connection with the UE#1, or the access network device #1 Part or all of the configuration information configured for UE#1 when the first RRC connection is reconfigured with UE#1.
  • the configuration information #A refers to the latest configuration of the first RRC connection.
  • the configuration information #A refers to the configuration of the first RRC connection at a certain time. The first implementation method assumes that the latest configuration is maintained, and the second implementation method assumes that the commonly used configuration is maintained.
  • the configuration information #A includes at least one of the cell identity of the access network device #1, the terminal identity of the UE#1, or the information identity of the configuration information #A.
  • the access network device #1 (an example of the first device) sends indication information #A to UE#1 (an example of the second device), where the indication information #A is used to indicate that the UE #1 is communicating with the access network.
  • the network access device #1 releases or reconfigures the RRC connection, it saves the configuration information #A before the release or reconfiguration.
  • the indication information #A may be used to instruct UE#1 to retain all configuration information of the first RRC connection between access network device #1 and UE#1; or, the indication The information #A can also be used to indicate which specific configuration information or types or types of configuration information of the first RRC connection between the access network device #1 and the UE #1 is reserved by the UE #1. Retention here refers to the preservation of information for subsequent use.
  • the indication information #A may be used to instruct UE#1 to retain all or part of the current configuration information of the first RRC between the access network device #1 and UE#1; or, The indication information #A may also be used to instruct UE#1 to reserve all or part of the configuration information for a specific time of the first RRC between the access network device #1 and UE#1.
  • the reconfiguration RRC connection here refers to instructing the UE#1 to disconnect or leave the RRC connection with the access network device #1 through the RRC reconfiguration message, and to access other access network devices, that is, in the usual sense. switch.
  • the indication information #A further includes the identification information allocated by the access network device #1 for the UE.
  • the identification information may be an identification code, which is used to indicate the reserved configuration information #A of the first RRC connection between the access network device #1 and the UE #1, and is used to reserve multiple UEs in the access network device #1
  • the identification code is retained at the same time, and the access network device #1 uses the identification code to index the configuration information #A corresponding to one or more UEs currently accessing cell #1, that is, access network device #1 Using the identification code, the network device #1 can index the configuration information #A of the corresponding UE #1.
  • the identification code The code length can be greater than or equal to the length of the C-RNTI allocated by the access network device #1 for UE#1, but it should also be considered that reducing the length of the H-RNTI can improve the reliability of transmission, so the length of the H-RNTI can be less than It is equal to the length of the I-RNTI allocated by the access network device #1 for UE#1.
  • the H-RNTI bit length may conservatively be between 48 and 56 bits, including 48 and 56 bits.
  • the H-RNTI can be determined according to the actual storage capacity of the access network device #1. If the access network device #1 can only store 128 configuration information , the H-RNTI may be 7 bits. In addition, the access network device #1 can also be determined according to the number of serving terminals. For example, if the access network device can serve 200 terminals at the same time, the code length of the H-RNTI can be close to 200. For example, the H-RNTI can take 8 bits (corresponding to 256 terminals).
  • the identification information may also be other identifications of UE#1, which is an example and not a limitation, for example, the device identification of UE#1.
  • the configuration information #A of multiple UEs saved by an access network device #1 has repeated parts, only one copy of the repeated parts can be stored, and different parts are stored separately according to the index identification code such as H-RNTI, thereby The storage space of the access network device #1 can be saved.
  • the sending manner of the indication information can be in the following two manners:
  • the access network device #1 may carry the indication information #A in the current RRC connection release message or the RRC connection reconfiguration message indicating the access network device #1, and send it to the UE #1.
  • UE#1 When carrying the RRC connection release message, UE#1 responds to the RRC connection release message, UE#1 keeps the configuration information #A and the UE#1 enters the idle state, and when carrying the RRC connection reconfiguration message, responds to The RRC connection reconfiguration message, the UE#1 keeps the configuration information #A and leaves the cell #1 of the access network device #1.
  • a message indicating RRC connection release or reconfiguration is an example but not a limitation, for example, RRC release message RRC release, RRC reconfiguration message RRC reconfiguration, handover information, switch to non-NR command message Mobility From NRCommand, redirection information, etc.
  • UE#1 saves the configuration information #A of the current access network device #1 according to the instruction of the indication information #A, and releases or reconfigures the RRC connection with the access network device #1, enters the idle state or communicates with other The access network device establishes an RRC connection.
  • "keep” can also be expressed as "save” or "reservation”.
  • the RRC connection reconfiguration message here refers to instructing the UE#1 to disconnect or leave the RRC connection with the access network device #1 and access other access network devices through the RRC reconfiguration message, which is the usual meaning switch on.
  • the access network device #1 can directly send the indication information #A to the UE #1 as an independent piece of information.
  • the indication information #A instructs the UE#1 to save the part of the cell #1 configured by the access network device #1 for the UE#1 when releasing or reconfiguring the RRC connection with the access network device #1
  • all configuration information that is, it is not necessary to release or reconfigure the RRC connection between the UE#1 and the access network device #1, and the access network device #1 only informs the UE# through the indication information #A 1.
  • the configuration information #A of cell #1 when releasing or reconfiguring the RRC connection.
  • reconfiguring the RRC connection between the UE#1 and the access network device #1 refers to instructing the UE#1 to disconnect or leave the RRC connection with the access network device #1 through an RRC reconfiguration message, and then connect to the access network device #1. into other access network equipment, that is, handover in the usual sense.
  • the access network device #1 stores the configuration information #A.
  • the access network device #1 keeps the configuration information #A when releasing or reconfiguring the RRC connection with the access network device #1.
  • the reconfiguration here refers to the RRC connection with the access network device #1, which means that through the RRC reconfiguration message, the UE#1 is instructed to disconnect or leave the RRC connection with the access network device #1 and access other access devices.
  • Network equipment that is, handover in the usual sense.
  • step S404 and step S405 have no order, and whether S404 is performed first or S405 is performed first, does not affect the specific implementation of the embodiments of the present application.
  • UE#1 receives the indication information #A sent by the access network device #1, and stores the configuration information #A according to the indication information #A. According to the indication information #A, the UE #1 can keep the configuration information #A when releasing or reconfiguring the RRC connection with the access network device #1.
  • “reconfiguring the RRC connection with the access network device #1” refers to instructing the UE#1 to disconnect or leave the RRC connection with the access network device #1 through the RRC reconfiguration message, and access other Access network equipment, that is, handover in the usual sense.
  • the access network device #1 may also update the RRC parameters of the configuration information #A of the UE #1 before sending the indication information #A or when sending the indication information #A.
  • UE#1 may also be instructed in the indication information #A to retain the updated parameters this time and use the updated parameter information as the configuration information #A of the access network device #1. That is to say, when the access network device #1 is repeatedly accessed next time, the UE#1 and the access network device #1 use the updated parameter configuration to restore the RRC connection.
  • parameter update refers to that when there are many RRC configuration parameters, some parameters may change and need to be adjusted.
  • the saving of the configuration information may also be initiated and executed by the terminal device of the configured node.
  • UE#1 sends indication information #B to access network device #1, where indication information #B is used to instruct access network device #1 to save configuration information #A when releasing or reconfiguring the RRC connection with UE#1,
  • the configuration information #A includes part or all of the configuration information configured by the access network device #1 for the UE #1.
  • the "reconfigure RRC connection” here refers to instructing the UE#1 to disconnect or leave the RRC connection with the access network device #1 through the RRC reconfiguration message, access other access network devices, and also It's a switch in the usual sense.
  • the indication information #B may instruct the access network device #1 to retain all configuration information; alternatively, the indication information #B may also instruct the access network device #1 to retain which specific one or which ones. Or what kind of configuration message.
  • UE#1 saves configuration information #A.
  • the corresponding UE#1 keeps the configuration information #A when releasing or reconfiguring the RRC connection with the access network device #1.
  • “reconfiguring the RRC connection with the access network device #1” refers to instructing the UE#1 to disconnect or leave the RRC connection with the access network device #1 through the RRC reconfiguration message, and access other Access network equipment, that is, handover in the usual sense.
  • step S404 and step S405 have no order, and whether S404 is performed first or S405 is performed first, does not affect the specific implementation of the embodiments of the present application.
  • the access network device #1 receives the indication information #B sent by the UE #1, and stores the configuration information #A according to the indication information #B. According to the indication information #B, the access network device #1 can keep the configuration information #A when releasing or reconfiguring the RRC connection with the UE #1.
  • “reconfiguring the RRC connection with UE#1” refers to instructing UE#1 to disconnect or leave the RRC connection with the access network device #1 through the RRC reconfiguration message, and access other access networks Device, that is, handover in the usual sense.
  • the access network device #1 when the access network device #1 reserves its independent configuration information #A for multiple UEs #1, after receiving the indication information #B, the access network device #1 can also send UE#1 sends indication information #B, where indication information #B includes identification information for indicating configuration information #A allocated by access network device #1 for UE#1.
  • the identification information is used to indicate the configuration information that the access network device #1 allocates separately for the UE #1, and may be an identification code.
  • the identification code is also retained.
  • the access network device #1 uses the identification code to index the configuration information #A corresponding to the currently connected UE #1, that is, the access network device #1 can use the identification code to index the configuration information # of the UE #1 A.
  • the code of the identification code can be greater than or equal to the length of the C-RNTI allocated by the access network device #1 for UE#1, but it should also be considered that reducing the length of the H-RNTI can improve the reliability of transmission, so the length of the H-RNTI can be less than or equal to The length of the I-RNTI allocated by the access network device #1 for UE#1.
  • the H-RNTI bit length may conservatively be between 48 and 56 bits, including 48 and 56 bits.
  • the H-RNTI can be determined according to the actual storage capacity of the access network device #1. If the access network device #1 can only store 128 configuration information , the H-RNTI may be 7 bits. In addition, the access network device #1 can also be determined according to the number of serving terminals. For example, if the access network device can serve 200 terminals at the same time, the code length of the H-RNTI can be close to 200. For example, the H-RNTI can take 8 bits (corresponding to 256 terminals).
  • the identification information may also be other identifications of UE#1, which is an example and not a limitation, for example, the device identification of UE#1.
  • the configuration information #A of multiple UEs stored by an access network device #1 has repeated parts, only one copy of the repeated parts can be stored, and different parts can be stored separately according to the index identification code, so that access can be saved.
  • the storage space of network device #1 is not limited to
  • the sending manner of the indication information #B can be in the following two manners:
  • UE#1 may carry indication information #B in UE#1 assistance information user equipment auxiliary information indicating RRC connection release or RRC connection reconfiguration request, and send it to access network device #1.
  • the access network device #1 saves the current configuration information according to the indication of the indication information #B, and releases or reconfigures the RRC connection with the UE #1.
  • the RRC connection reconfiguration request means that UE#1 requests to disconnect or leave the RRC connection with the access network device #1 and access other access network devices, that is, a handover request in the usual sense.
  • the UE#1 may directly send indication information #B as independent information to access network device #1.
  • the indication information #B instructs the access network device #1 to save part or all of the configuration information configured by the access network device #1 for the UE #1 when releasing or reconfiguring the RRC connection with the UE #1, that is, It is said that currently, it is not necessary to release or reconfigure the RRC connection between UE#1 and access network device #1, and UE#1 just informs access network device #1 to save the RRC connection when releasing or reconfiguring the RRC connection through indication #B.
  • Configuration information #A is provided to save part or all of the configuration information configured by the access network device #1 for the UE #1 when releasing or reconfiguring the RRC connection with the UE #1.
  • the access network device #1 receives the indication information #B sent by the UE #1, and according to the indication information #B, saves the configuration information #A when releasing or reconfiguring the RRC connection.
  • UE#1 saves configuration information #A before releasing or updating the RRC connection with the access network device #1.
  • the access network device #1 can also update the RRC parameters in the configuration information of the UE#1, and send the information to UE#1 1.
  • Send indication information #C in which indication information #C instructs UE#1 to retain the updated parameters this time and use the updated parameter information as configuration information #A of the access network device #1. That is to say, when the access network device #1 is repeatedly accessed next time, the UE#1 and the access network device #1 use the updated parameter configuration to restore the RRC connection.
  • parameter update refers to that when there are many RRC configuration parameters, some parameters may change and need to be adjusted.
  • the configuration information #A of UE#1 may also be stored in other network nodes. For example, other access network equipment, or core network equipment.
  • the access network device #1 may keep the configuration information #A of the UE #1 in the access network device #1, or other access network devices, or core network devices according to a predetermined rule. If it is determined to be stored in other devices other than the access network device #1, it further includes that the access network device #1 sends the configuration information #A of the UE #1 to other devices, where the configuration information #A at least includes the access network device #1. At least one of the cell identifier of the network device #1, the device identifier of the UE#1, the radio access network area identifier of the access network device #1, and the information identifier H-RNTI of the configuration information #A.
  • Access network device #1 and UE#1 save configuration information #A and release the RRC connection between access network device #1 and UE#1, UE#1 enters the idle state or directly leaves the access network device #1, In this case, when the UE#1 needs to access the access network device #1 again, the saved configuration information #A can be used to determine the parameters in the RRC process to restore the RRC connection, realize data transmission, and save signaling Transmission redundancy.
  • UE#1 sends indication information #D (an example of the first indication information) to access network device #1, where indication information #D is used to indicate that access network device #1 has configuration information stored in UE#1 #A, the configuration information #A includes part or all of the configuration information configured by the access network device #1 for the UE #1.
  • indication information #D an example of the first indication information
  • the configuration information #A includes part or all of the configuration information configured by the access network device #1 for the UE #1.
  • the indication information #D may further include at least one of the equipment identification of UE #1 and the information identification H-RNTI of configuration information #A.
  • the access network device #1 receives the information #D, and determines that the UE #1 has the configuration information #A according to the indication information #D.
  • the access network device #1 determines whether to save the configuration information #A and determines the configuration information #B (an example of the second context information), where the configuration information #B is the re-establishment between the access network device #1 and the UE #1 Configuration information for RRC connection.
  • the access network device #1 queries the saved configuration information #A of the UE #1 according to the device identifier of the UE #1 in the access request information, and determines whether to save the configuration of the UE #1 Information #A, the configuration information #B is determined according to the configuration information #A.
  • the access network device #1 may also directly match the configuration information #A of the UE#1 according to the information identifier of the saved configuration information #A, and determine the configuration information #B according to the configuration information #A. .
  • UE#1 may first confirm whether there is configuration information #A, and UE#1 may determine whether there is configuration information #A according to the access network device #1.
  • the cell identifier of the device #1 determines whether the configuration information #A of the access network device #1 is stored.
  • the access network device #1 may send the cell identification information by means of broadcast or multicast.
  • the configuration information #A may be part or all of the configuration information that the access network device #1 instructs the UE #1 to save when the UE #1 historically accesses the access network device #1, for example, the access network Part or all of the configuration information saved by the device #1 and UE#1 in the recent RRC connection release or reconfiguration process; or, the network device considers the current configuration information to be a better configuration for UE#1, such as a relatively stable configuration, and notify UE#1 to save the current RRC configuration as configuration information #A; or, the configuration information #A is the configuration information independently determined by the UE#1 when the UE#1 historically accesses the access network device #1, such as UE#1 #1 actively determines that the current configuration is a better configuration and saves it as configuration information #A, and notifies access network device #1 to keep the current configuration as configuration information #A.
  • the indication information #D may instruct the access network device that the UE#1 retain the configuration information #A; or, the indication information #D may also be used to confirm the access network device Whether #1 retains the configuration information #A of the UE#1, that is, the access network device #1 may not save or lose the saved configuration information #A when disconnecting from the UE#1; or, the indication information #D may also include identification information.
  • the identification information in the above implementation manner may be that when the access network device #1 reserves its independent configuration information #A for multiple UEs, the access network device #1 allocates it to the UE #1 to indicate the access network device #1.
  • the configuration information #A allocated separately for UE#1, that is, the access network device #1 can use the identification information to index the saved configuration information #A of the UE#1.
  • the identification information is, for example, H-RNTI. It can also be the UE ID, or other terminal identifiers.
  • the sending manner of the indication information can be in the following two manners:
  • UE#1 may carry the indication information #D in the RRC connection establishment request or RRC connection reestablishment request or RRC connection reconfiguration request information, that is, UE#1 is sending the RRC connection establishment request or RRC connection reestablishment to access network device #1 When requesting or requesting RRC connection reconfiguration, the indication information #D is sent.
  • UE#1 may directly send indication information #D as independent information to access network device #1.
  • UE#1 may not necessarily initiate an RRC connection establishment request or an RRC connection reestablishment request or an RRC connection reconfiguration request, but may also be initiated by the access network device #1.
  • UE#1 may not send indication information #D or indicate in indication information #D that UE#1 does not save the access network device #1 as Configuration information #A configured by the UE#1.
  • the access network device #1 receives the indication information #D sent by the UE#1, and can know that the UE#1 is the UE#1 that saves the configuration information #A, and the access network device #1 can further determine whether the UE# is reserved. 1 configuration information #A. Further, if the access network device #1 saves configuration information #A for multiple UEs #1, the indication information includes an identification code, and the access network device #1 can use the identification code as an index to match the corresponding configuration. Information #A.
  • the determination of configuration information #B can be in the following situations:
  • the access network device #1 determines that the configuration information #A (configuration one) of the UE #1 exists, the access network device #1 further determines whether to use the configuration information #A as the initial configuration of this connection. details as follows:
  • the access network device #1 determines that it can obtain the configuration information (configuration 2) before the handover or before the reconfiguration, and the access network device #1 can further determine to use the configuration 1 and configuration Which configuration of configuration 2 is used to save signaling, so that the configuration that saves more signaling is selected as configuration information #B;
  • the access network device #1 If the access network device #1 is resuming the RRC connection, if the access network device #1 determines that it can obtain the configuration information stored by the UE#1 before the RRC suspension (configuration 3), the access network device #1 can further determine to use the configuration The first and third configuration saves more signaling, so the configuration that saves more signaling is selected as configuration information #B.
  • the access network device #1 determines that the configuration information #A of the UE #1 is not saved or the configuration information #A of the UE #1 is not found, the access network device #1 can use the default configuration (configuration zero) as the configuration information #B;
  • the access network device #1 determines whether the configuration information #A of the UE#1 can be obtained, and if the configuration information #A of the UE#1 can be obtained, the access network device #1 can use the configuration information #A as the configuration information# B establishes an RRC connection with UE#1, which is an example but not a limitation. For example, access network device #1 may obtain configuration information #A of this UE#1 from other network nodes;
  • the access network device #1 determines that the configuration information #A of the UE #1 can be obtained, and during the handover or reconfiguration, the access network device #1 determines that the configuration information before the handover or the reconfiguration can be obtained (configuration 2 ), the access network device #1 can further judge which configuration is more signaling-saving by using configuration one and using configuration two, so as to select the configuration that is more signaling-saving as configuration information #B;
  • the access network device #1 determines that the configuration information #A of the UE #1 can be obtained, and when the RRC connection is restored, the access network device #1 determines that the configuration information stored by the UE #1 before the RRC suspension can be obtained (Configuration 3), the access network device #1 can further determine which configuration uses configuration 1 and configuration 3 to save signaling, and thus selects the configuration that saves more signaling as configuration information #B.
  • the access network device #1 may further perform RRC reconfiguration on the basis of the configuration information #A.
  • Network device #1 configures a new value for a parameter, and sends the value of the reconfigured parameter to UE#1, and does not send parameters that have not been reconfigured in configuration information #A.
  • configuration information #A includes parameters A and parameter B.
  • the values of parameter A and parameter B are A1 and B1 respectively.
  • Access network device #1 reconfigures parameter A as A2, and access network device #1 sends parameter A2 to UE #1. Therefore, the configuration signaling load sent by the access network device #1 to the UE #1 can be reduced.
  • access network device #1 sends indication information #E (an example of the second indication information) to UE #1, where indication information #E is used to instruct UE #1 to communicate with the access network device according to configuration information #B #1 establishes a second RRC connection.
  • indication information #E an example of the second indication information
  • the indication information #E may be an RRC configuration message sent by the access network device #1, where the RRC configuration message includes at least one of an RRC connection establishment message, an RRC connection reestablishment message, and an RRC connection reconfiguration message.
  • the indication information #E includes the configuration information #B determined by the access network device #1, specifically which configuration is used as the configuration information #B.
  • the indication information #E further includes parameter values that the access network device #1 reconfigures some parameters on the basis of the configuration information #B, that is, the access network device # 1.
  • the reconfigured parameter values should also be sent to UE#1. It should be understood that parameters that are not reconfigured will not be sent.
  • UE#1 determines to use the configuration information #B as the initial configuration parameter according to the configuration information #B included in the received indication information #E.
  • the configuration information #B may be configuration one, or configuration two, or configuration three, or configuration zero.
  • UE#1 can use configuration information #A as the initial configuration of the configuration for parameter configuration; if it is configuration 2, UE#1 can use the configuration information before handover or before reconfiguration as configuration If it is configuration 3, UE#1 can use the configuration information stored before RRC suspend as the initial configuration of the configuration for parameter configuration; if it is configuration 0, UE#1 can use the default configuration Configure the parameters as the initial configuration of the configuration.
  • UE#1 may also receive the value of the reconfiguration parameter included in the indication information #E, and UE#1 determines the value of the corresponding parameter according to the value of the parameter, and adopts the reset parameter Configure the parameters as the initial configuration of the configuration.
  • UE#1 receives indication information #E, and UE#1 establishes a second RRC connection with access network device #1 according to indication information #E.
  • the RRC process (including but not limited to the RRC establishment process, the RRC reconstruction process, and the RRC reconfiguration process) can be performed according to the configuration information retained by the terminal device and the access network device. , one or more of the RRC recovery process, the RRC redirection process, the handover process, and the RRC reset process), there is no need to send all configuration information, which saves system overhead.
  • FIG. 5 shows another example of a schematic flowchart of a communication method provided by a specific embodiment of the present application. The method can be applied to the communication systems shown in FIG. 1 and FIG. 2 .
  • the access network device #1 is an example of the network device as one of the configuration nodes
  • the access network device #2 is the network device as an example of the other configuration node
  • the UE #1 is an example of a terminal device as a configured node.
  • the coverage of each network device may be abstracted into one or more cells, and a cell may be an area within the wireless network coverage of the network device.
  • different network devices may correspond to different cells, such as , the network coverage area of access network device #1 is cell #1, and the network coverage area of access network device #2 is cell #2.
  • access network device #1 and access network device #2 are different network devices in the same radio access network notification area (RAN-Based Notification Area, also referred to as RAN Area for short), and the RAN Area is a RAN-based notification area , which can cover one cell or multiple cells, and is within the scope of the registration area configured by the core network.
  • RAN-Based Notification Area also referred to as RAN Area for short
  • the configuration node may also be other network elements of the network device or a terminal device with a configuration function, and the configured node may also be another device of the terminal device or a network device that can be configured.
  • Method 500 may include the following steps.
  • step S501-step S506 relates to a specific implementation method, which is the same as step S401-step S406 in the first embodiment, and details are not repeated here.
  • step S501-step S506 is basically the same as step S401-step S406 in the first embodiment, the difference is that in the first embodiment, the access network device #1 and UE#1 are releasing or releasing The configuration information #A is saved when reconfiguring the RRC connection between the access network device #1 and the UE #1. In the second implementation method of the second embodiment, the access network device #1 and the UE #1 disconnect the RRC connection and the UE #1 is disconnected.
  • UE#1 When #1 leaves the current RAN Area, RAN Area#1, UE#1 saves the configuration information #A* of the access network device #1 (which can be used as an example of the first context information), and the configuration information #A* is in the RAN Area Part or all of the configuration information configured by the access network device #1 for the UE#1 at #1, that is, the access network device #1 is the last serving cell for the UE#1 to leave the RAN Area #1.
  • the access network device #1 and UE#1 save the configuration information #A* and release the RRC connection.
  • the configuration information #A* of UE#1 can be stored in the access network device# 1 or other network nodes. For example, other access network equipment, or core network equipment.
  • the access network device #1 may keep the configuration information #A of the UE #1 in the access network device #1, or other access network devices, or core network devices according to a predetermined rule. If it is determined to be stored in other devices other than the access network device #1, it further includes that the access network device #1 sends the configuration information #A of the UE #1 to the other devices, where the configuration information #A at least includes the access network device #1.
  • any access network device in RAN Area#1 can save the configuration information #A*.
  • UE#1 re-enters the RAN Area#1, UE#1 and the accessed access network equipment can use the saved configuration information #A* to restore the RRC connection to realize data transmission and save signaling overhead.
  • the UE#1 can access any access network equipment of a cell in the RAN Area. It should be understood that the beneficial effect of the second embodiment is that if a UE is , the RRC configuration information of different cells in the same RAN Area is basically the same, therefore, the UE#1 can access the access network equipment of any cell in the RAN Area, and restore the RRC using the saved configuration information of the historical access network equipment connect.
  • the access network device and the UE only need to save the historical configuration information of one RRC connection in one RAN Area, compared to saving the configuration information of RRC connections of multiple different access network devices in the same RAN Area
  • a RAN Area only needs to store the configuration information of one RRC connection, which reduces the storage overhead of the access network and the UE.
  • the method to restore the RRC connection is as follows.
  • UE#1 sends indication information #F (an example of the first indication information) to access network device #2, where indication information #F is used to indicate that UE#1 has configuration information #A of RAN Area#1 *, the configuration information #A* includes part or all of the configuration information configured for the UE#1 by the access network device #1 of the RAN Area#.
  • indication information #F is used to indicate that UE#1 has configuration information #A of RAN Area#1 *
  • the configuration information #A* includes part or all of the configuration information configured for the UE#1 by the access network device #1 of the RAN Area#.
  • Access network device #2 and access network device #1 are in the same RAN-Based Notification Area of UE#1.
  • UE#1 Before UE#1 sends the indication information #F to access network device #2, in S507, UE#1 needs to confirm whether there is configuration information #A*, and UE#1 can determine whether there is configuration information #A* according to access network device #2 Determines whether the configuration information #A* of the RAN Area#1 is stored.
  • the access network device #2 may send the RAN Area identification information of the access network device #2 by broadcasting or multicasting.
  • the configuration information #A* may be the part stored by the UE#1 indicated by the access network device #1 when the UE#1 historically accesses the access network device #1 in the RAN-Based Notification Area or All configuration information, such as part or all of the configuration information saved by the access network device #1 and UE#1 in the recent RRC connection release or update process;
  • the configuration information determined by the UE#1 autonomously, for example, UE#1 actively determines that the current configuration is a better configuration and saves it as configuration information #A*, and notifies the access Network device #1 retains the current configuration as configuration information #A*.
  • the indication information #F may indicate that the UE#1 retains the configuration information #A* when accessing the RAN Area#1.
  • the indication information #F can also be used to confirm whether the access network device #2 retains the configuration information #A* of the UE#1.
  • the access network device #2 has historical access to the RAN Area#1
  • the access network equipment of any cell in the RAN area, UE#1 may save the configuration information #A* between the access network equipment #1 and UE#1 of the historical access cell #1 in the RAN Area#1.
  • Access network device #2 that is, in this case, the access network device #2 stores configuration information #A*.
  • the access network device #2 may not store the configuration information #A*, and the configuration information #A* stores the access network cell that UE#1 accessed in the RAN Area #1 for the last time, that is, the access network device. #1, or configuration information #A* is stored in access network devices or core network devices other than access network device #2 and access network device #1.
  • the indication information #F can also be used to indicate that the access network device storing the configuration information #A* is the access network device #0, and the indication information includes the serving cell #0PCell of the access network device #0 cell Identity.
  • the indication information #F may also include identification information, such as an identification code, the identification code is when the access network device #1 in the current RAN Area #1 reserves its independent configuration information #A* for multiple UEs, the access network device Configuration information #A* allocated by #1 to UE#1 and used to indicate that access network device #1 is allocated separately for UE#1, that is, any access network device in the current RAN Area#1 wireless network area uses
  • the identification code may index into the saved configuration information #A* of the UE#1.
  • the identification code is, for example, H-RNTI, and the length of the identification code is greater than the above-mentioned length of the identification code, and is at least 48-56 bits.
  • the identification information may also be UE ID, or other terminal identification.
  • Access network device #0 may be access network device #1, or an access network device or core network device different from access network device #1.
  • the sending manner of the indication information #F is the same as that of the indication information #B, and in order to avoid redundant description, repeated description is not repeated.
  • the access network device #2 determines whether to save the configuration information #A*, obtains the configuration information #A* if there is no configuration information #A*, and determines the configuration information #B* (an example of the third context information), the configuration Information #B* is configuration information when the access network device #2 establishes an RRC connection with UE #1.
  • the access network device #2 and the access network device #1 are in the same RAN-Based Notification Area.
  • the access network device #2 receives the indication information #F sent by the UE#1, and can know that the UE#1 is the UE#1 that saves the configuration information #A*, and the access network device #2 can further determine whether to reserve the UE Configuration information #A* of #1.
  • the access network device #2 queries the saved configuration information #A* of the UE#1 according to the device identifier of the UE#1 in the access request information, and determines whether to save the configuration information #A* of the UE#1 Configuration information #A*.
  • the access network device #2 may also directly obtain the configuration information #A* of the UE #1 according to the information identifier H-RNTI of the configuration information #A*.
  • the configuration information #A* between it and the access network device #1 of the historical access cell #1 may be saved in the access network device #2, and further, If access network device #1 saves configuration information #A* for multiple UEs #1, the indication information includes an identification code, and access network device #2 can also use the identification code as an index to obtain corresponding configuration information# A*.
  • the access network device #2 confirms that the configuration information #A* of the UE#1 is not stored, and the access network device #2 can use the configuration information of the serving cell #0 included in the indication information #F.
  • the identification information identifies the access network device #0 that stores the configuration information #A*, and the access network device #2 sends request information #e to the access network device #0, where the request information #e is used to request the access network device #0
  • the configuration information #B* stored for the UE#1 is sent, and the request information includes the identity of the UE#1.
  • the access network device #0 sends the configuration information #A* stored for the UE #1 to the access network device #2, and the access network device #2 obtains the configuration information #A*, and determines the configuration information #A* as the configuration information #A* associated with the UE #1.
  • #1 Restore the initial configuration of the RRC connection.
  • Access network device #0 may be access network device #1, or an access network device or core network device different from access network device #1.
  • the method for determining the configuration information #B* is similar to the method for determining the configuration information #B, and will not be described repeatedly.
  • the access network device #2 may further perform RRC reconfiguration on the basis of the configuration information #B*. Specifically, Access network device #2 configures a new value for a parameter, and sends the value of the reconfigured parameter to UE#1, and does not send parameters that have not been reconfigured in configuration information #B*, for example, configuration information # B* includes parameter A and parameter B. The values of parameter A and parameter B are A1 and B1 respectively. Access network device #2 reconfigures parameter A as A2, and access network device #2 sends parameter A2 to UE. #1. Therefore, the configuration signaling load sent by the access network device #2 to the UE #1 can be reduced.
  • the access network device #2 sends indication information #G (an example of the second indication information) to the UE #1, where the indication information #G is used to instruct the UE #1 to communicate with the access network device according to the configuration information #B* #2 establishes a third RRC connection.
  • indication information #G an example of the second indication information
  • the indication information #G may be an RRC configuration message sent by the access network device #2, where the RRC configuration message includes at least one of an RRC connection establishment message, an RRC connection reestablishment message, and an RRC connection reconfiguration message. It should be noted that the indication information #G includes the configuration information #B* determined by the access network device #2, specifically which configuration is used as the configuration information #B*.
  • the indication information #G further includes parameter values that the access network device #2 reconfigures some parameters on the basis of the configuration information #B*, that is, the access network device In addition to sending the determined configuration information #B* to UE#1, #2 also sends the reconfigured parameter values to UE#1. It should be understood that parameters that are not reconfigured will not be sent.
  • UE#1 determines to use the configuration information #B* as the initial configuration parameter according to the configuration information #B* included in the received indication information #G.
  • the configuration information #B* may be configuration one, configuration two, or configuration three.
  • UE#1 can use configuration information #A* as the initial configuration of the configuration for parameter configuration; if it is configuration 2, UE#1 can use the configuration information before handover or before reconfiguration as the configuration information.
  • UE#1 receives indication information #G, and UE#1 establishes a third RRC connection with access network device #2 according to indication information #G.
  • the configuration information of the same access network device or different access network devices of the same RAN-Based Notification Area saved before can be reused to perform the RRC process ( Including but not limited to one or more of the RRC establishment process, the RRC reestablishment process, the RRC reconfiguration process, the RRC recovery process, the RRC redirection process, the handover process, and the RRC reset process), without the need for the network device to send for the access network device All configuration information, reducing signaling redundancy for repeatedly sending configuration information.
  • the access network device #2 and the access network device #1 belong to the same RAN Area, and the configuration information of different access networks in the same RAN Area has greater similarity.
  • the historical configuration information stored in a RAN Area can be used for UE#1 to access any access network device in the RAN Area, without the need for the network device to send all configuration information for the access network device, reducing the need to repeatedly send configuration information. make redundant.
  • the access network device #2 and the access network device #1 may also have other similar attributes, for example, the configuration information of the access network device #2 and the access network device #1 of the same operator has a larger value. Similarity, using a method similar to Embodiment 2 of this application, the historical configuration information saved by the access network device UE#1 in an operator network can be used for any access in the operator network when UE#1 accesses The network equipment does not need the network equipment to send all the configuration information for the access network equipment, reducing the signaling redundancy of repeatedly sending the configuration information. For another example, the configuration information of access network devices with similar or the same coverage is relatively similar. For example, access network device #1 and access network device #2 are both macro sites, and the second embodiment of the present application is similar.
  • the access network equipment and the historical configuration information of a macro station saved by UE#1 can be used to access other macro station equipment at UE#1 without the need for the network equipment to send all configuration information for the access network equipment, reducing the need for Signaling redundancy for repeatedly sending configuration information.
  • more than one access network device may be configured as a configuration information sharing area, using a method similar to Embodiment 2 of the present application, the configuration information of any access network device and UE#1 in the configuration information sharing area can be used. It is used when UE#1 accesses the configuration information sharing area again, without the need for the network device to send all configuration information for the access network device, thereby reducing signaling redundancy for repeatedly sending configuration information.
  • the methods and operations implemented by the terminal equipment may also be implemented by components (such as chips or circuits) that can be used in the terminal equipment, and may be implemented by network equipment (such as cell A or a cell to which cell A belongs).
  • the methods and operations implemented by network equipment can also be implemented by components (eg, chips or circuits) that can be used in network equipment.
  • each network element such as a transmitter device or a receiver device
  • each network element includes hardware structures and/or software modules corresponding to performing each function in order to implement the above functions.
  • Those skilled in the art should realize that the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • the transmitting-end device or the receiving-end device may be divided into functional modules according to the foregoing method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. middle.
  • the above-mentioned integrated modules can be implemented in the form of hardware, or can be implemented in the form of software function modules.
  • the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation. The following description will be given by using the division of each function module corresponding to each function as an example.
  • FIG. 6 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application.
  • the communication device 600 includes a transceiver unit 610 , a storage unit 620 and a processing unit 630 .
  • the transceiver unit 610 can implement corresponding communication functions, the storage unit 620 can be used to store instructions and/or data, and the processing unit 630 can read the instructions and/or data in the storage unit, so that the communication device can implement the foregoing method embodiments.
  • Transceiver unit 610 may also be referred to as a communication interface or a communication unit.
  • the communication device 600 can be used to perform the actions performed by the terminal device in the above method embodiments.
  • the communication device 600 can be a terminal device or a component that can be configured in the terminal device, and the transceiver unit 610 is used to perform the above method.
  • the storage unit 620 is configured to perform operations related to data or instruction storage on the terminal device side in the above method embodiments
  • the processing unit 630 is configured to execute the terminal device side in the above method embodiments. side processing related operations.
  • the communication device 600 may be configured to perform the actions performed by the access network device #1 (or cell #1) and the access network device #2 (or cell #2) in the above method embodiments, and the transceiver unit 610 uses In performing the operations related to sending and receiving on the side of the access network device #1 (or cell #1) and the access network device #2 (or cell #2) in the above method embodiments, the storage unit 620 is configured to perform the above method implementation In the example, the storage-related operations on the access network device #1 (or cell #1) and the access network device #2 (or cell #2) side, the processing unit 630 is configured to execute the access network device in the above method embodiment. Operations related to processing on the side of #1 (or cell #1) and the access network device #2 (or cell #2).
  • an embodiment of the present application further provides a communication device 700 .
  • the communication device 700 includes a processor 710 coupled with a memory 720, the memory 720 is used for storing computer programs or instructions and/or data, the processor 710 is used for executing the computer programs or instructions and/or data stored in the memory 720, Also included is a transceiver 730 for reception and/or transmission of signals.
  • the processor 710 is used to control the transceiver 730 to receive and/or transmit signals. The methods in the above method embodiments are caused to be executed.
  • the communication apparatus 700 includes one or more processors 710 .
  • the communication apparatus 700 may further include a memory 720 .
  • the communication device 700 may include one or more memories 720 .
  • the memory 720 may be integrated with the processor 710, or provided separately.
  • the communication apparatus 700 is configured to implement the operations performed by the terminal device in the above method embodiments.
  • the processor 710 is configured to implement the processing-related operations performed by the terminal device in the above method embodiments
  • the transceiver 730 is configured to implement the above-mentioned method embodiments performed by the terminal device.
  • the communication apparatus 700 is configured to implement the operations performed by the network device in the above method embodiments.
  • the processor 710 is configured to implement the processing-related operations performed by the network device in the above method embodiments
  • the transceiver 730 is configured to implement the above-mentioned method embodiments performed by the network device. Transceive-related operations.
  • a processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • 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 conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this 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 (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be Random Access Memory (RAM), which acts as an external cache.
  • RAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory Synchlink DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution, and 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 execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

本申请提供了一种通信方法和通信装置，该方法包括：第二设备从第一设备获取所述第二设备的第一上下文信息，所述第一上下文信息包括第一设备和所述第二设备之间的第一RRC连接的全部或部分配置信息；所述第二设备接收RRC消息并保持所述第一上下文信息；所述第二设备发送RRC连接建立请求消息，用于指示所述第二设备保持所述第一上下文信息；和/或所述第二设备接收RRC配置消息，所述RRC配置消息包括第二指示信息，所述第二指示信息用于指示所述第二设备根据所述第一上下文信息建立第二RRC连接。从而，能够使终端设备与接入网设备根据保留的配置信息进行RRC过程，无需接入网设备发送全部配置信息，节省了系统开销。

Description

一种通信方法和装置 技术领域
本申请涉及通信领域，并且更具体地，涉及一种通信方法和装置。
背景技术
在第三代合作伙伴计划(3rd generation partnership project，3GPP)中，终端设备为了进行数据传输，需要先和接入网设备建立无线资源控制(radio resource control，RRC)连接来实现数据传输，当终端设备没有数据传输时，接入网设备会暂时删除与终端数据传输相关的上下文信息，当终端设备需要传输数据包时，需要重新建立无线资源控制连接，重新建立与该终端数据传输相关的上下文信息，建立新的连接需要传输大量信令，传输效率降低。
因此，亟需一种保存上下文信息的通信机制，以减少RRC相关过程中终端设备上下文确定和或配置参数确定过程造成的信令开销，提高传输效率。
发明内容
本申请提供一种通信方法和装置，用于节省系统开销。
第一方面，提供了一种通信方法，包括：第二设备从第一设备获取该第二设备的第一上下文信息，该第一上下文信息包括第一设备和该第二设备之间的第一RRC连接的全部或部分配置信息，该第一设备是该第二设备的服务小区；该第二设备接收RRC消息；响应于该RRC消息,该第二设备保持该第一上下文信息；该第二设备发送RRC连接建立请求消息，该RRC连接建立请求消息包括第一指示信息，该第一指示信息用于指示该第二设备保持该第一上下文信息；和/或该第二设备接收RRC配置消息，该RRC配置消息包括第二指示信息，该第二指示信息用于指示该第二设备根据该第一上下文信息建立第二RRC连接，该RRC配置消息包括RRC连接建立消息、RRC连接重建立消息、RRC连接重配置消息中的至少一个。
示例地，该第二设备接收所述第一设备发送的指示信息，所述第二设备根据所述指示信息保存所述第一上下文信息，也就是说第二设备可以根据RRC消息保持所述第一上下文信息，也可以根据一个单独的指示信息来保持该第一上下文信息。
根据本申请提供的通信方法，第二设备获取第二设备与第一设备连接的第一上下文信息(即第一设备与第二设备在建立第一RRC连接时的全部或部分配置信息)，第二设备与第一设备在释放或更新连接时保持该第一上下文信息，第二设备可以与待接入设备通过该第一上下文信息进行RRC过程，这里的RRC过程包括但不限于RRC建立过程、RRC重建过程、RRC重配置过程、RRC恢复过程、RRC重定向过程、切换过程、RRC重置过程中的一个或多个)，从而能够避免重新进行RRC过程时需要传输相关上下文信息消耗大量信令，提升传输效率。
结合第一方面，在第一方面的某些实现方式中，第二设备保存第一上下文信息，该第一上下文信息包括第一设备和该第二设备之间的第一RRC连接的部分或全部配置信息；该第二设备释放或重配置所述第一RRC连接；该第二设备根据第一配置信息与所述第一设备建立第二RRC连接；和/或，该第二设备根据第一配置信息与第三设备建立第三RRC连接。
结合第一方面，在第一方面的某些实现方式中，该第二设备可以向该第一设备发送指示信息，该指示信息用于指示该第一设备保存第一上下文信息并释放或重配置RRC连接。该上下文信息可以是第二设备在历史接入该第一设备时该第一设备指示第二设备保存的部分或全部配置信息，也可以是第二设备确定保持当前上下文信息，并通知第一设备保持当前上下文信息。
基于上述方案，第二设备(即，终端设备)也可以指示第一设备保存第一上下文信息并释放或重配置RRC连接，也就是说保存第一上下文信息的动作可以由终端设备发起，也可以由接入网设备发起，从而指示第二设备与第一设备在释放或更新连接时保持该第一上下文信息，第二设备可以与待接入设备通过该第一上下文信息进行RRC过程，这里的RRC过程包括但不限于RRC建立过程、RRC重建过程、RRC重配置过程、RRC恢复过程、RRC重定向过程、切换过程、RRC重置过程中的一个或多个)，从而能够避免重新进行RRC过程时需要传输相关上下文信息消耗大量信令，提升传输效率。
结合第一方面，在第一方面的某些实现方式中，响应于该RRC消息,该第二设备保持该第一上下文信息，包括：该RRC消息为RRC连接释放消息，响应于该RRC连接释放消息，该第二设备保持该第一上下文信息且该第二设备进入空闲态；或者，该RRC消息为RRC连接重配置消息，响应于该RRC连接重配置消息，该第二设备保持该第一上下文信息且该第二设备离开该第一设备。
基于上述方案，第二设备与第一设备处于连接态时获取了第一上下文信息，第二设备会接收第一设备发送的RRC消息，接收到的RRC消息可以是RRC连接释放消息，也可以是RRC连接重配置消息，当收到RRC连接释放消息，第二设备在保持该第一上下文信息后，第二设备断开与第一设备的RRC连接，进入空闲态；当收到RRC连接重配置消息，第二设备在保持该第一上下文信息后，第二设备断开与第一设备的连接并离开当前服务小区，可能接入其他小区。
结合第一方面，在第一方面的某些实现方式中，该第一上下文信息包括该第一设备的小区标识、该第二设备的设备标识、该第一设备的无线接入网区域(RAN Area)标识、该第一上下文的信息标识中的至少一个。
结合第一方面，在第一方面的某些实现方式中，该第二设备发送RRC连接建立请求消息之前，该方法还包括：该第二设备根据第一设备的小区标识确定该第二设备是否保持有该第一设备的第一上下文信息；该第二设备向该第一设备发送RRC连接建立请求消息。
基于上述方案，第一设备和第二设备在保持第一上下文信息之后，可以根据第一上下文信息中的第一设备的小区标识确定是否保持有该第一设备的上下文信息，确保保持有该第一设备的上下文信息之后再去发送RRC连接建立请求信息，从而确保该第一设备一定保持有该上下文信息，进一步地保证在使用该上下文信息进行RRC过程时是有效的，提升RRC过程效率。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第二设备向该第一设备上报第三指示信息，该第三指示信息用于指示该第二设备具有在空闲态或离开该第一设备后保持该第一上下文信息的能力。
示例地，该第二设备在向第一设备上报第三指示信息之前，还包括：第二设备接收第一设备发送的请求信息，该请求信息用于请求第二设备上报具有在空闲态和/或离开该第一设备后保持该第一上下文信息的能力。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第二设备接收该第一设备发送的第四指示信息，该第四指示信息用于指示该第一设备是否具有该第二设备在空闲态和或该第二设备离开该第一设备后保持该第一上下文信息的能力。
基于上述方案，第一设备确认第二设备是否具有在空闲态或离开该第一设备后保持该第一上下文信息的能力，在确定第二设备具备该存储能力的情况下，进行第一上下文信息的保存以及使用该上下文信息进行RRC过程。
结合第一方面，在第一方面的某些实现方式中，在响应于RRC消息，该第二设备保持该第一上下文信息之前，该方法还包括：该第二设备确定该第二设备为该第一设备的常驻设备。
示例地，该第二设备根据第一条件确定该第二设备为该第一设备的常驻设备，该第一条件，例如，第二设备接入第一设备的驻留时间大于一定的门限。再例如，第二设备接入第一设备的次数或频率。再例如，第二设备曾经接入该第一设备。该第一条件可以由第一设备或第二设备或由预定义的规则确定。
基于上述方案，确定第二设备为第一设备的常驻终端设备，即，接入网设备和终端设备进行识别接入，接入网设备只保存常驻终端设备的上下文信息，常驻终端设备只保存常驻接入网设备的上下文信息，进一步节省网络设备和终端设备的存储开销。
结合第一方面，在第一方面的某些实现方式中，该第二设备接收RRC配置消息还包括：该第一设备根据该第一上下文信息确定第二上下文信息，该第二上下文信息与该第一上下文信息至少部分相同；该第二设备根据该第二上下文信息，确定该第二RRC连接的上下文信息。
基于上述方案，第一设备确定的第二上下文信息与第一上下文信息部分或全部相同，在第一指示信息中可以包括不同的信息的部分，第二设备不需要与第一设备进行全部上下文信息的交互，根据第一指示信息中包括的不同的部分以及自己保存的第一上下文信息来确定最终进行第二次RRC连接的上下文信息，节省了RRC过程中上下文信息交互造成的信令开销。
第二方面，提供了一种通信方法，包括：第一设备获取第一上下文信息，该第一上下文信息包括第一设备和第二设备之间的第一RRC连接的全部或部分配置信息，该第一设备是该第二设备的服务小区；该第一设备发送RRC消息且保持该第一上下文信息，该RRC消息用于指示该第二设备保持该第一上下文信息；该第一设备从该第二设备接收RRC连接建立请求消息，该RRC连接建立请求消息包括第一指示信息，该第一指示信息用于指示该第二设备保持有该第一上下文信息；和/或该第一设备发送RRC配置消息，该RRC配置消息包括第二指示信息，该第二指示信息用于指示该第二设备根据该第一上下文信息建立第二RRC连接，该RRC配置消息包括RRC连接建立消息、RRC连接重建立消息、 RRC连接重配置消息中的至少一个。
示例地，该第一设备可以向第二设备发送指示信息，该指示信息用于指示第二设备保存所述第一上下文信息，也就是说第二设备可以根据RRC消息保持所述第一上下文信息，也可以根据一个单独的指示信息来保持该第一上下文信息。
根据本申请提供的通信方法，第一设备获取第一上下文信息(即第一设备与第二设备在建立第一RRC连接时的全部或部分配置信息)，第二设备与第一设备在释放或更新连接时保持该第一上下文信息，第一设备可以与第二设备通过该第一上下文信息进行RRC过程，这里的RRC过程包括但不限于RRC建立过程、RRC重建过程、RRC重配置过程、RRC恢复过程、RRC重定向过程、切换过程中的一个或多个)，从而能够避免重新进行RRC过程时需要传输相关上下文信息消耗大量信令，提升传输效率。
结合第二方面，在第二方面的某些实现方式中，该第一设备接收该第二设备发送的指示信息，该第一设备根据该指示信息保存该第一上下文信息并释放或重配置RRC连接。该上下文信息可以是第二设备在历史接入该第一设备时该第一设备指示第二设备保存的部分或全部配置信息，也可以是第二设备确定保持当前上下文信息，并通知第一设备保持当前上下文信息。
结合第二方面，在第二方面的某些实现方式中，该RRC消息用于指示该第二设备保持该第一上下文信息，包括：该RRC消息为RRC连接释放消息，该RRC连接释放消息用于指示该第二设备保持该第一上下文信息且进入空闲态；或者，该RRC消息为RRC连接重配置消息，该RRC连接重配置消息用于指示该第二设备保持该第一上下文信息且离开该第一设备。
基于上述方案，第一设备发送的RRC消息，可以是RRC连接释放消息，也可以是RRC连接重配置消息，当收到RRC连接释放消息，第二设备在保持该第一上下文信息后，第二设备断开与第一设备的RRC连接，进入空闲态；当收到RRC连接重配置消息，第二设备在保持该第一上下文信息后，第二设备断开与第一设备的连接并离开当前服务小区，可能接入其他小区。
结合第二方面，在第二方面的某些实现方式中，该第一上下文信息包括该第一设备的小区标识、该第二设备的设备标识、该第一设备的无线接入网区域标识、该第一上下文的信息标识中的至少一个。
结合第二方面，在第二方面的某些实现方式中，该第一设备发送RRC配置消息之前，该方法还包括：该第一设备根据该第二设备的设备标识、该第一上下文的信息标识中的至少一个确定该第一设备是否保持有该第二设备的第一上下文信息。
基于上述方案，第一设备和第二设备在保持第一上下文信息之后，可以根据第二设备设备标识或该第一上下文的信息标识中的至少一个确定是否保持有该第二设备的第一上下文信息，确保保持有该第二设备的上下文信息之后再去发送RRC配置消息，从而确保该第二设备一定保持有该上下文信息，进一步地保证在使用该上下文信息进行RRC过程时是有效的，提升RRC过程效率。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该第一设备接收该第二设备上报的第三指示信息，该第三指示信息用于指示该第二设备具有在空闲态和或离开该第一设备后保持该第一上下文信息的能力。
示例地，该第一设备在接收第二设备上报的第三指示信息之前，还包括：第一设备向第二设备发送请求信息，该请求信息用于请求第二设备上报具有在空闲态和或离开该第一设备后保持该第一上下文信息的能力。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该第一设备向该第二设备发送第四指示信息，该第四指示信息用于指示该第一设备是否具有在空闲态和/或离开该第一设备后保持该第二设备的第一上下文信息的能力。
基于上述方案，第一设备确认第二设备是否具有在空闲态或离开该第一设备后保持该第一上下文信息的能力，在确定第二设备具备该存储能力的情况下，进行第一上下文信息的保存以及使用该上下文信息进行RRC过程。
结合第二方面，在第二方面的某些实现方式中，在该第一设备保持该第一上下文信息之前，包括：该第一设备根据第一条件或第一设备的存储能力确定第二设备为该第一设备的常驻设备。
基于上述方案，确定第二设备为第一设备的常驻终端设备，即，接入网设备和终端设备进行识别接入，接入网设备只保存常驻终端设备的上下文信息，常驻终端设备只保存常驻接入网设备的上下文信息，进一步节省网络设备和终端设备的存储开销。
结合第二方面，在第二方面的某些实现方式中，该第一设备发送RRC配置消息还包括：该第一设备根据该第一上下文信息确定第二上下文信息，该第二上下文信息与该第一上下文信息至少部分相同；该第一设备根据该第二上下文信息，确定该第二RRC连接的上下文信息。
基于上述方案，第一设备确定的第二上下文信息与第一上下文信息部分或全部相同，在第一指示信息中可以包括不同的信息的部分，第二设备不需要与第一设备进行全部上下文信息的交互，根据第一指示信息中包括的不同的部分以及自己保存的第一上下文信息来确定最终进行第二次RRC连接的上下文信息，节省了RRC过程中上下文信息交互造成的信令开销。
第三方面，提供了一种通信方法，包括：第三设备从该第二设备接收RRC连接建立请求消息，该RRC连接建立请求消息包括第一指示信息，该第一指示信息用于指示该第二设备保持有第一上下文信息；和/或该第三设备发送RRC配置消息，该RRC配置消息包括第二指示信息，该第二指示信息用于指示该第二设备根据第一上下文信息建立第三RRC连接，该RRC配置消息包括RRC连接建立消息、RRC连接重建立消息、RRC连接重配置消息中的至少一个；该第一上下文信息包括第一设备和该第二设备之间的第一RRC连接的全部或部分配置信息，该第一设备是该第二设备的历史服务小区。
示例地，该第三设备的第一上下文信息，可以是第三设备保存的，也可以是从第一设备获取的，也可以是存在服务器上可以获取的。
根据本申请提供的通信方法，第三设备作为待接入设备，可以与第二设备通过第一上下文信息进行RRC过程(这里的RRC过程包括但不限于RRC建立过程、RRC重建过程、RRC重配置过程、RRC恢复过程、RRC重定向过程、切换过程、RRC重置过程中的一个或多个)，从而能够避免重新进行RRC过程时需要传输相关上下文信息消耗大量信令，提升传输效率。
结合第三方面，在第三方面的某些实现方式中，该第三设备发送RRC配置消息之前， 该方法还包括：该第三设备根据该第一设备标识、该第二设备的设备标识、该第一设备的无线接入网区域标识、该第一上下文的信息标识中的至少一个确定该第二设备的第一上下文信息。
结合第三方面，在第三方面的某些实现方式中，该第三设备发送RRC配置消息，该方法还包括：该第三设备根据该第一上下文信息确定第三上下文信息，该第三上下文信息与该第一上下文信息至少部分相同；该第三设备根据该第三上下文信息，确定该第三RRC连接的上下文信息。
基于上述方案，第三设备确定的第三上下文信息与第一上下文信息部分或全部相同，在第一指示信息中可以包括不同的信息的部分，第三设备不需要与第二设备进行全部上下文信息的交互，根据第一指示信息中包括的不同的部分以及自己保存的或是获取的第一上下文信息来确定最终进行第三RRC连接的上下文信息，节省了RRC过程中上下文信息交互造成的信令开销。
第四方面，提供一种通信设备，该通信设备执行该第一方面或其各种实现方式中的方法的单元。
第五方面，提供一种通信设备，该通信设备执行该第二方面或其各种实现方式中的方法的单元。
第六方面，提供一种通信设备，该通信设备执行该第三方面或其各种实现方式中的方法的单元。
第七方面，提供一种通信设备，包括，处理器，存储器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该通信设备执行第一或第二或第三方面及其各种可能实现方式中的通信方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
第八方面，提供了一种通信系统，包括上述第一设备、第二设备和第三设备之一。
第九方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一方面、第二方面或第三方面中任一种可能实现方式中的方法。
第十方面，提供了一种计算机可读介质，所述计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面、第二方面或第三方面中任一种可能实现方式中的方法。
第十一方面，提供了一种电路系统，包括存储器和处理器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得安装有该电路系统的通信设备执行上述第一方面、第二方面或第三方面中任一种可能实现方式中的方法。
其中，该电路系统可以包括用于发送信息或数据的输入电路或者接口，以及用于接收信息或数据的输出电路或者接口。
第十二方面，提供了一种电路系统，用于执行上述第一方面、第二方面或第三方面中任一种可能实现方式中的方法。
附图说明
图1示出了一种适用于本申请实施例的无线通信系统100的示意图。
图2示出了另一种适用于本申请实施例的无线通信系统200的示意图。
图3示出了一种适用于本申请实施例提供的通信方法的示意性框图。
图4示出了一种适用于本申请实施例提供的通信的方法的示意性流程图。
图5示出了一种适用于本申请又一实施例提供的通信的方法的示意性流程图。
图6示出了一种适用于本申请实施例提供的通信设备的一种示意性框图。
图7示出了一种适用于本申请实施例提供的通信设备的一种示意性架构图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例提及的无线通信系统包括但不限于：长期演进(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)通信系统、第五代(5th Generation，5G)系统或新无线(New Radio，NR)、或未来的通信系统等。
本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、资源或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于:磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
图1示出了本申请实施例的无线通信系统100的示意图。如图1所示，该无线通信系统100可以包括至少一个配置节点，例如图1所示的网络设备111，该无线通信系统100还可以包括至少一个被配置节点，例如图1所示的终端设备121至终端设备123。网络设备和终端设备均可配置多个天线，网络设备与终端设备可使用多天线技术通信。
其中，网络设备和终端设备通信时，网络设备可以管理一个或多个小区，一个小区中可以有整数个终端设备。可选地，网络设备111和终端设备121至终端设备123组成一个单小区通信系统，不失一般性，将小区记为小区#1。网络设备111可以是小区#1中的网络设备，或者说，网络设备111可以为小区#1中的终端设备(例如终端设备121)服务。
需要说明的是，小区可以理解为网络设备的无线信号覆盖范围内的区域。
图2示出了本申请实施例的无线通信系统200的另一示意图。如图2所示，该无线通 信系统200可以包括至少一个配置节点，例如图2所示的终端设备211，该无线通信系统200还可以包括至少一个被配置节点，例如图2所示的终端设备221至终端设备223。网络设备和终端设备均可配置多个天线，网络设备与终端设备可使用多天线技术通信。
应理解，该无线通信系统中的配置节点可以是任意一种具有无线配置功能为配置节点生成无线资源配置信息的设备，该设备可以是网络设备，或者该设备还可以是具有配置功能的终端设备。该网络设备包括但不限于：下一代节点B(next generation Node B,gNB)演进型节点B(evolved Node B，eNB)、无线网络控制器(Radio Network Controller，RNC)、节点B(Node B，NB)、基站控制器(Base Station Controller，BSC)、基站收发台(Base Transceiver Station，BTS)、家庭基站(例如，Home evolved NodeB，或Home Node B，HNB)、基带单元(Base Band Unit，BBU)，无线保真(Wireless Fidelity，WIFI)系统中的接入点(Access Point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G，如，NR，系统中的gNB，或，传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)等。
该无线通信系统中的被配置节点可以是任意一种接收配置节点发送的无线资源配置信息的设备，该设备可以是终端设备，也可以是被配置的网络设备。该终端设备也可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。本申请的实施例中的终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。本申请的实施例对应用场景不做限定。
在本申请实施例，应理解，网络设备和终端设备根据配置信息恢复RRC连接，该配置信息为RRC连接态时网络设备为终端设备配置的小区#1的部分或全部配置信息，该配置信息的具体内容可以由网络设备与终端设备预先约定，该配置信息可以为该终端设备与安全有关的上下文、ROHC(Robust Header Compression)状态、用于DRB(Data Radio Bear)映射规则的QoS flow，该服务小区#1的PCell的cell Identity、该服务基站#1的物理层ID，在PSCell的公共配置Serving Cell Config Common、该服务小区#1广播消息Serving Cell Config Common SIB、该服务小区#1为该终端设备配置的专用配置Serving Cell Config等，本实施例对此不做限定。
下文实施例，为区分且不失一般性，接入网设备#1是网络设备作为配置节点的一个示例，UE#1是终端设备作为被配置节点的一个示例。应理解，每个网络设备的覆盖范围可以被划分为一个或多个小区，小区可以是网络设备的无线网络覆盖范围内的区域，在本申请中，不同的网络设备可以对应不同的小区，例如，接入网设备#1和接入网设备#2管理不同的小区#1和小区#2。需要说明的是，本实施例仅仅是示例性的不应该对本申请构成任何限定。配置节点也可以是网络设备的其他网元或是具有配置功能的终端设备，被配 置节点也可以是终端设备的其他设备或是可以被配置的网络设备。
本申请实施例可以在UE具有存储配置信息的能力基础上执行，例如，无线通信系统中可以包括具有存储配置信息能力的UE和不具有存储配置信息能力的UE，此情况下，接入网设备可以查询UE是否具有存储配置信息能力的情况。
方法一：
接入网设备#1向UE#1发送请求消息#a，该请求消息#a用于请求UE#1上报是否具备储存配置信息的能力。
或者说，接入网设备#1向UE#1发送请求消息#a，该请求信息#a用于确认UE是否具有存储配置信息的能力。可选地，接入网设备#1还可以向UE#1发送能力消息#b(第四指示信息的一例)，该能力消息#b用于向UE#1指示该接入网设备#1具有该UE#1在空闲态或该UE#1离开该接入网设备#1后存储配置信息的能力，该能力消息#b与请求消息#a可以为同一消息，也可以是不同消息。
或者，接入网设备#1可以通过广播消息或组播消息的方式通知UE#1该接入网设备#1具有存储配置信息的能力。
UE#1接收请求消息#a和/或能力消息#b，确认是否具有存储配置信息的能力并向接入网设备#1发送上报消息#c(第三指示信息的一例)，该上报消息#c用于告知接入网设备#1该UE#1在空闲态或离开接入网设备#1后是否具有存储配置信息的能力。
方法二：
UE#1可以主动向接入网设备#1发送上报消息#c(第三指示信息的一例)，用于告知接入网设备#1该UE#1在空闲态或离开接入网设备#1后是否具有存储配置信息的能力。
请求消息#a也可以称为能力查询消息。接入网设备#1发送该能力查询消息，用于请求UE#1上报全部或部分UE#1能力信息。上报消息#c也称为能力上报信息，包括全部或者部分UE#1支持的能力。特别的，对于本申请，上报消息#c可以包括UE#1在空闲态或离开接入网设备#1后具有存储配置信息的能力。如果上报消息#c没有包括UE#1在空闲态或离开接入网设备#1后具有存储配置信息的能力，则认为UE#1不支持在空闲态或离开接入网设备#1后具有存储配置信息的能力。
上报消息#c，进一步的，还可以包括UE#1具有N套配置信息的存储能力，其中，N为大于等于1的正整数，每一套配置信息对应一个接入网设备发给该UE#1的配置信息。
该UE#1是否具有存储配置信息的能力，进一步的，还可以包括，在N套配置信息的存储能力中，剩余的存储能力。例如UE#1具有存储5套配置信息的存储能力，如果UE#1已经存储了两个接入网设备的配置信息，如接入网设备#a的配置信息和接入网设备#b的配置信息，接入网设备#a和接入网设备#b是与接入网设备#1不同的接入网设备，则此时该UE#1可以上报该UE#1还具有3套配置信息存储能力。
该UE#1是否具有存储配置信息的能力，进一步的，可以指示UE#1是否具有存储配置信息的能力。例如UE#1具有存储2套配置信息的存储能力，如果UE#1已经存储了接入网设备#a的配置信息和接入网设备#b的配置信息，接入网设备#a和接入网设备#b是与接入网设备#1不同的接入网络设备，则此时该UE#1可以上报该UE#1不具有存储配置信息的能力。再例如，UE#1具有存储2套配置信息的存储能力，如果UE#1已经存储了接入网络设备#a的配置信息和接入网络设备#b的配置信息，接入网络设备#a和接入网络设 备#b是与接入网络设备#1不同的接入网络设备，但UE#1可以判定接入网络设备#1配置信息存储的优先级比接入网络设备#a或者接入网络设备#b中的任意一个的配置信息的存储优先级更高，则UE#1可以上报UE#1具有存储配置信息的能力。
当该UE#1不具有存储配置信息的能力时，RRC过程(包括但不限于RRC建立过程、RRC重建过程、RRC重配置过程、RRC恢复过程、RRC重定向过程、切换过程、RRC重置过程中的一个或多个)不再赘述。以下主要针对具有存储配置信息能力的UE进行RRC过程(包括但不限于RRC建立过程、RRC重建过程、RRC重配置过程、RRC恢复过程、RRC重定向工程、切换过程、RRC重置过程中的一个或多个)进行详细说明。
应理解，该终端设备可以是具有存储该配置信息能力的终端设备，也可以是不具有存储该配置信息能力的终端设备，在一种可能的实现方式中，该配置信息可以是具有存储配置信息能力的终端设备作为常驻终端设备在常驻服务小区的配置信息，也就是说常驻网络设备和常驻终端设备保存RRC连接时的配置信息。判断是否为常驻终端设备或常驻网络设备的方法，在本申请实施例中，作为示例可以采用如下方法：
方法三：接入网设备#1确认UE#1是否为常驻终端设备，在一种可能的实现方式中，接入网设备#1确认UE#1具备存储配置信息的能力之后，通过确认UE#1是否满足第一条件来确认UE#1是否为常驻终端设备。该第一条件为该接入网设备#1所确定的规则和参数，具体地，接入网设备#1可以采用统计UE#1在接入网设备#1驻留时间的方式来确定规则和参数，该规则具体为UE#1统计驻留在接入网设备#1的时间，该驻留时间大于一定门限，该门限值可以作为参数，也就是说，当UE#1统计驻留在某接入网设备#1的驻留时间大于一定的门限值，即接入网络设备#1确认该UE#1满足第一条件，则该UE#1和接入网设备#1互为常驻终端设备和常驻网络设备。或者，该规则也可以是UE#1驻留在接入网设备#1的接入时间或频率，也就是UE#1与接入网设备#1之间建立RRC连接的时间或频率，或者，该规则也可以是该UE#1与该接入网设备#1之间传输的数据包的数量或频率，该规则也可以是该UE#1接入到该接入网络设备#1的次数或频率该规则和参数可以是预先规定的，如协议定义的，也可以是网络设备根据历史通信情况确定的经验值。本申请对此不做限定。在此情况下，释放或更新RRC连接时，该接入网设备#1可以为该UE#1存储配置信息，以及该UE#1可以在释放或更新RRC连接时存储该接入网设备#1分配的配置信息。
方法四：接入网设备#1向UE发送消息#d，该消息#d用于UE确定是否满足第一条件，满足第一条件的UE为常驻终端设备。
消息#d还包括以下信息：第一条件的规则和参数。消息#d可以是广播消息，也可以是发给一组UE的组播消息，或者发给一个UE的该UE专用的消息，此时，消息#d还包括终端标识。接收到消息#d的UE根据消息#d所指示的第一条件的规则和参数，来确定UE是否满足第一条件。
具体的，接入网设备#1通过广播消息发送消息#d；或者，接入网设备#1确认UE#1具备存储配置信息的能力之后，发送消息#d给具有具备存储配置信息能力的UE#1，UE#1通过确认UE#1是否满足第一条件来确认UE#1是否为常驻终端设备。接入网设备#1向UE#1发送消息#d，该消息#d包括第一条件的规则和参数，UE#1确认是否满足第一条件，如果满足第一条件，从而确定该UE#1为常驻终端设备，在此情况下，释放或更新RRC连接时该接入网设备#1可以为该UE#1存储配置信息，该UE#1可以在释放或更新RRC 连接时存储该接入网设备#1分配的配置信息。该第一条件为该接入网设备#1所确定的规则和参数，该规则和参数可以由接入网设备#1确定，具体地，接入网设备#1可以采用统计UE#1在接入网设备#1驻留时间的方式来确定规则和参数，该规则具体为UE#1统计驻留在接入网设备#1的时间，该驻留时间大于一定门限，该门限值可以作为参数，也就是说，当UE#1统计驻留在某接入网设备#1的驻留时间大于一定的门限值，即该UE#1确认满足第一条件，则该UE#1和接入网设备#1互为常驻终端设备和常驻网络设备。或者，该规则也可以是UE#1驻留在接入网设备#1的接入时间，也就是UE#1与接入网设备#1之间建立RRC连接的时间，或者，该规则也可以是该UE#1与接入网设备#1之间传输的数据包的数量或频率，该规则也可以是该UE#1接入到该接入网设备#1的次数或频率，该规则和参数可以是预先规定的，如协议定义的，也可以是网络设备根据历史通信情况确定的经验值。本申请对此不做限定。当UE#1满足该第一条件，在此情况下，释放或更新RRC连接时，该接入网设备#1保存该UE#1的配置信息，该UE#1保存该接入网设备#1的配置信息，从而可以节省存储配置信息所需要的开销。进一步的，UE#1确认满足第一条件并向接入网设备#1发送上报消息#e，该上报消息#e用于向接入网设备#1上报该UE#1满足第一条件。
方法五：UE#1确认是否为常驻终端设备。在一种可能的实现方式中，UE#1确认UE#1具备存储配置信息的能力之后，UE#1通过判断UE#1是否满足第一条件来确认UE#1是否为常驻终端设备。例如第一条件为，UE#1在接入网络设备#1的驻留时间大于一等的门限。再例如，第一条件为，UE#1与接入网设备#1之间建立RRC连接的时间。再例如，UE#1接入到接入网络设备#1的次数或频率。第一条件由UE#1按照事先确定的规则来确定，或者由UE#1自主确定。本申请对此不做限定。当UE#1满足该第一条件，在此情况下，释放或更新RRC连接时，该接入网设备#1保存该UE#1的配置信息，该UE#1保存该接入网设备#1的配置信息，从而可以节省存储配置信息所需要的开销。进一步的，UE#1确认满足第一条件并向接入网设备#1发送上报消息#e，该上报消息#e用于向接入网设备#1上报该UE#1满足第一条件。
方法六：接入网设备#1确认UE#1是否为常驻终端设备，在一种可能的实现方式中，接入网设备#1根据自己的能力确认UE#1是否为常驻终端。具体的，接入网络设备#1确认UE#1具备存储配置信息的能力之后，判断自己的存储能力是否足够，如果足够，则确认该UE#1为常驻终端。如果自己的存储能力不够，则确认该UE#1不是常驻终端。再例如，接入网络设备#1确认UE#1具备存储配置信息的能力之后，判断自己的存储能力是否足够，如果足够，则确认该UE#1为常驻终端。如果自己的存储能力不够，则确认该UE#1的优先级是否比之前存储的任意一个或多个UE的优先级高，如果该UE#1的优先级比之前存储的任意一个或多个UE的优先级高，则确认该UE#1为常驻终端，否则，确认该UE#1不是常驻终端。
进一步的，接入网设备#1确认该UE#1为常驻终端并向该UE#1发送标识码，该标识码用于指示该接入网设备#1为该UE#1分配的配置信息。
具体的，在一种可能的实现方式中，接入网设备#1接收UE#1的上报消息#d之后，确认该UE#1为常驻终端设备，可以为该UE#1存储配置信息，该接入网设备#1还可以为该UE#1分配一个标识码。该标识码用于指示满足第一条件的常驻网络与常驻终端设备之 间RRC连接时的配置信息，或者该标识码为用于索引满足第一条件的常驻网络与常驻终端设备之间RRC连接时的配置信息的索引值。例如，该标识码可以是H-RNTI(History Radio Network Tempory Identity)，该标识码的码长可以根据接入网络设备#1的存储能力确定。如果该接入网络设备#1存储能力较强，该标识码的码长大于等于该接入网设备#1为UE#1分配的C-RNTI(Cell RNTI)的长度(一般为16比特)，小于等于该接入网设备#1为UE#1分配的I-RNTI(Inactive RNTI)的长度。H-RNTI大于等于C-RNTI是考虑到接入网设备#1实际存储的第一配置的数量会比接入网设备#1同时处于连接态的UE多，H-RNTI小于等于I-RNTI主要考虑在于减少H-RNTI的长度以提升传输的可靠性。优选的，H-RNTI位长在48-56比特之间，含48和56比特。如果该接入网络设备#1为了节省成本，存储能力较弱，则H-RNTI可以根据接入网络设备#1的实际存储能力来确定，如果接入网络设备#1只能存储128个配置信息，则H-RNTI可以为7比特。另外，接入网络设备#1还可以根据服务终端的数量多少来确定，例如如果接入网络设备同时能够服务200个终端，则H-RNTI的码长可以跟200接近，例如H-RNTI可以取8比特(对应256个终端)。
需要说明的是，该接入网设备#1和该UE#1不是永久的关系，当接入网设备#1确定UE#1不再满足第一条件时，或者接入网设备#1的存储能力不足时，可以解除低优先级的UE#1的常驻关系，或者，UE#1有更合适存储的接入网设备#1时，该网络设备#1不再是该终端设备的常驻网络设备，或者UE#1不再是接入网络设备#1的常驻终端，UE#1可以不保存该接入网设备分配的配置信息，接入网设备#1可以不保存该UE#1的配置信息。
因此通过本申请实施例，终端设备和接入网设备进行识别，释放或更新RRC连接时接入网设备可以为常驻终端设备存储配置信息，常驻终端设备可以在释放或更新RRC连接时存储该接入网设备分配的配置信息，从而节省接入网设备和终端设备在RRC过程中因参数确定造成的系统开销。
图3示出了本申请具体实施例提供的通信方法的一种示意性框图。方法300可以包括如下步骤。
S301，接入网设备#1确认UE#1具备在空闲态或离开接入网设备#1后储存配置信息的能力；
S302，接入网设备#1确认UE#1是否为常驻终端设备；
S303，接入网设备#1和UE#1在释放或重配置RRC连接时保持配置信息；
S304，根据配置信息UE#1和待接入网设备进行RRC过程。
需要说明的是，以上步骤S301和步骤S302为可选地步骤，执行任一步骤或不执行均不影响本申请实施例的具体实现。
在步骤S301和步骤S302之前或之后，还包括，接入网设备#1和UE#1建立第一RRC连接。
基于本申请实施例，终端设备在和接入网设备建立第一RRC连接后，在释放或更新连接时保持在接入网设备的配置信息，该终端设备无论是与该接入网设备断开进入空闲态或是断开后与其他接入网设备(接入网设备#2)进行RRC过程(这里的RRC过程包括但不限于RRC建立过程、RRC重建过程、RRC重配置过程、RRC恢复过程、RRC重定向过程、切换过程、RRC重置过程中的一个或多个)，都可以使用保持的配置信息，因此可以节省参数配置造成的系统开销。
图4示出了本申请具体实施例提供的通信方法的一种示意性流程图。该方法可以应用于图1和图2所示通信系统中。
S401，接入网设备#1确认UE#1具备储存配置信息的能力。
S402，接入网设备#1确认UE#1是否为常驻终端设备。
以上步骤具体过程与上述过程相似，在此不进行重复说明。
需要说明的是，以上步骤S401和步骤S402为可选地步骤，执行任一步骤或不执行均不影响本申请实施例的具体实现。
在步骤S401和步骤S402之前或之后，还包括，接入网设备#1和UE#1建立第一RRC连接。
接入网设备#1和UE#1在释放或重配置RRC连接时保持配置信息，配置信息的保存有两种方式，第一种方式如下步骤：
S403，UE#1从接入网设备#1获取UE#1的配置信息#A(第一上下文信息的一例)，该配置信息#A包括该接入网设备#1与UE#1之间的第一RRC连接所包括的部分或全部配置信息，包括接入网设备#1与UE#1建立第一RRC连接时为该UE#1配置的部分或全部配置信息，或接入网设备#1与UE#1重配置第一RRC连接时为该UE#1配置的部分或全部配置信息。接入网设备#1与UE#1建立第一RRC连接后可能会有一次或者多次重配置，其中一种具体实施方法中，配置信息#A指第一RRC连接的最新配置。其中另一种具体实施方法中，配置信息#A指第一RRC连接在某个时间的配置。第一种实施方法假定保留最新的配置，第二种实施方法假定保留常用的配置。
作为示例而非限定，该配置信息#A至少包括接入网设备#1的小区标识，UE#1的终端标识或配置信息#A的信息标识中的至少一个。
S404，接入网设备#1(第一设备中的一例)向UE#1(第二设备中的一例)发送指示信息#A，该指示信息#A用于指示该UE#1在与该接入网设备#1释放或重配置RRC连接时保存释放或重配置之前的配置信息#A。
作为示例而非限定，在本申请中，该指示信息#A可以用来指示UE#1保留接入网设备#1和UE#1之间的第一RRC连接的全部配置信息；或者，该指示信息#A也可以用来指示UE#1保留接入网设备#1和UE#1之间的第一RRC连接的具体哪个或者哪些或者哪类配置信息。这里的保留，指的是保存信息以便后继使用。
作为示例而非限定，在本申请中，该指示信息#A可以用来指示UE#1保留接入网设备#1和UE#1之间的第一RRC的当前全部或部分配置信息；或者，该指示信息#A也可以用来指示UE#1保留接入网设备#1和UE#1之间的第一RRC的特定时间的全部或部分配置信息。
这里的重配置RRC连接，指的是通过RRC重配置消息，指示UE#1断开或离开与该接入网设备#1的RRC连接，接入其他的接入网设备，也就是通常意义上的切换。
当接入网设备#1为多个UE保留其独立的配置信息#A时，该指示信息#A中还包括该接入网设备#1为UE分配的标识信息。具体地，该标识信息可以为标识码，用于指示保留的接入网设备#1与UE#1的第一RRC连接的配置信息#A，用于在接入网设备#1保留多个UE的配置信息#A时，同时保留标识码，接入网设备#1使用该标识码对当前接入小区#1的一个或多个UE对应的配置信息#A进行索引，也就是说，接入网设备#1使用该标识码 可以索引到相应UE#1的配置信息#A。
作为示例而非限定，例如，H-RNTI，考虑到接入网设备#1实际存储的配置信息#A的数量会比接入网设备#1同时处于连接态的UE数量多，该标识码的码长可以大于等于该接入网设备#1为UE#1分配的C-RNTI的长度，但是还要考虑到减少H-RNTI的长度可以提升传输的可靠性，因此H-RNTI的长度可以小于等于该接入网设备#1为UE#1分配的I-RNTI的长度。优选的而非限定，H-RNTI位长保守地可以在48-56比特之间，含48和56比特。如果该接入网络设备#1为了节省成本，存储能力较弱，则H-RNTI可以根据接入网络设备#1的实际存储能力来确定，如果接入网络设备#1只能存储128个配置信息，则H-RNTI可以为7比特。另外，接入网络设备#1还可以根据服务终端的数量多少来确定，例如如果接入网络设备同时能够服务200个终端，则H-RNTI的码长可以跟200接近，例如H-RNTI可以取8比特(对应256个终端)。
该标识信息也可以是UE#1的其他标识，作为示例而非限定，例如，UE#1的设备标识。
进一步地，如果一个接入网设备#1保存的多个UE的配置信息#A有重复的部分，重复的部分可以只保存一份，不同的部分根据索引标识码例如H-RNTI单独保存，从而可以节省接入网设备#1的存储空间。
作为示例而非限定，在本申请中，指示信息的发送方式可以有以下两种方式：
方式一：
接入网设备#1可以将指示信息#A承载于指示接入网设备#1的当前RRC连接释放消息或RRC连接重配置消息中，发送给UE#1。当承载于RRC连接释放消息时，UE#1响应于该RRC连接释放消息，UE#1保持该配置信息#A且该UE#1进入空闲态，当承载于RRC连接重配置消息时，响应于该RRC连接重配置消息，该UE#1保持该配置信息#A且离开所述接入网设备#1的小区#1。指示RRC连接释放或重配置的消息，作为示例而非限定，例如，RRC释放消息RRC release、RRC重配置消息RRC reconfiguration、切换信息、切换到非NR的命令消息Mobility From NRCommand、重定向信息等。此情况下，UE#1根据指示信息#A的指示保存当前接入网设备#1的配置信息#A，并释放或重配置与接入网设备#1的RRC连接，进入空闲状态或者与其他接入网设备建立RRC连接。这里的“保持”(keep)也可以表述为“保存”(save)或“保留”。这里的RRC连接重配置消息，指的是通过RRC重配置消息，指示UE#1断开或离开与该接入网设备#1的RRC连接，接入其他的接入网设备，也就是通常意义上的切换。
方式二：
接入网设备#1可以直接将指示信息#A作为一个独立的信息单独发送给UE#1。此情况下，指示信息#A指示UE#1在释放或重配置与该接入网设备#1的RRC连接时，保存该接入网设备#1为该UE#1配置的小区#1的部分或全部配置信息，也就是说，当前并不需要释放或重配置该UE#1与该接入网设备#1的RRC连接，该接入网设备#1只是通过指示信息#A通知该UE#1在释放或重配置RRC连接时要保存小区#1的配置信息#A。这里的重配置该UE#1与该接入网设备#1的RRC连接，指的是通过RRC重配置消息，指示UE#1断开或离开与该接入网设备#1的RRC连接，接入其他的接入网设备，也就是通常意义上的切换。
S405，接入网设备#1保存配置信息#A。
具体的，接入网络设备#1在释放或重配置与接入网设备#1的RRC连接时，保持配置信息#A。
这里的重配置与接入网设备#1的RRC连接，指的是通过RRC重配置消息，指示UE#1断开或离开与该接入网设备#1的RRC连接，接入其他的接入网设备，也就是通常意义上的切换。
应理解，步骤S404与步骤S405没有先后顺序，无论是先执行S404或是先执行S405，均不影响本申请实施例的具体实现。
S406，UE#1接收接入网设备#1发送的指示信息#A，根据该指示信息#A保存配置信息#A。根据该指示信息#A，UE#1可以在释放或重配置与接入网设备#1的RRC连接时，保持配置信息#A。
其中，“重配置与接入网设备#1的RRC连接”，指的是通过RRC重配置消息，指示UE#1断开或离开与该接入网设备#1的RRC连接，接入其他的接入网设备，也就是通常意义上的切换。
在一种可能的实现方式中，接入网设备#1在发送指示信息#A之前或发送指示信息#A时，还可以对该UE#1的配置信息#A的RRC参数进行更新。
作为示例而非限定，还可以在指示信息#A中指示UE#1保留本次更新后的参数并将更新后的参数信息作为该接入网设备#1的配置信息#A。也就是说，下次重复接入该接入网设备#1时，UE#1和接入网设备#1采用更新后的参数配置来恢复RRC连接。具体地，参数更新指的是RRC配置参数较多时，有可能存在部分参数发生变化，需要进行调整。
配置信息的保存方式，第二种方式如下步骤：
在一种可能的实现方式中，配置信息的保存也可以由被配置节点的终端设备发起执行。
S404，UE#1向接入网设备#1发送指示信息#B，该指示信息#B用于指示接入网设备#1在与UE#1释放或重配置RRC连接时保存配置信息#A，该配置信息#A包括该接入网设备#1为该UE#1配置的部分或全部配置信息。
其中，这里的“重配置RRC连接”，指的是通过RRC重配置消息，指示UE#1断开或离开与该接入网设备#1的RRC连接，接入其他的接入网设备，也就是通常意义上的切换。
作为示例而非限定，在本申请中，该指示信息#B可以指示接入网设备#1保留全部配置信息；或者，该指示信息#B也可以指示接入网设备#1保留具体哪个或者哪些或者哪类配置消息。
S405，UE#1保存配置信息#A。对应的UE#1在释放或重配置与接入网设备#1的RRC连接时，保持配置信息#A。
其中，“重配置与接入网设备#1的RRC连接”，指的是通过RRC重配置消息，指示UE#1断开或离开与该接入网设备#1的RRC连接，接入其他的接入网设备，也就是通常意义上的切换。
应理解，步骤S404与步骤S405没有先后顺序，无论是先执行S404或是先执行S405，均不影响本申请实施例的具体实现。
S406，接入网设备#1接收UE#1发送的指示信息#B，根据该指示信息#B保存配置信 息#A。根据该指示信息#B，接入网设备#1可以在释放或重配置与UE#1的RRC连接时，保持配置信息#A。
其中，“重配置与UE#1的RRC连接”，指的是通过RRC重配置消息，指示UE#1断开或离开与该接入网设备#1的RRC连接，接入其他的接入网设备，也就是通常意义上的切换。
在一种可能的实现方式中，当接入网设备#1为多个UE#1保留其独立的配置信息#A时，接入网设备#1接收到该指示信息#B后，还可以向UE#1发送指示信息#B，该指示信息#B包括标识信息，用于指示接入网设备#1为UE#1分配的配置信息#A。
具体地，该标识信息用于指示接入网设备#1为UE#1单独分配的配置信息，可以为标识码，在接入网设备#1保留多个UE的配置信息时，同时保留标识码，接入网设备#1使用标识码对当前连接的UE#1对应的配置信息#A的索引，也就是说，接入网设备#1使用该标识码可以索引到UE#1的配置信息#A。作为示例而非限定，例如，H-RNTI，考虑到接入网设备#1实际存储的第一配置的数量会比接入网设备#1同时处于连接态的UE数量多，该标识码的码长可以大于等于该接入网设备#1为UE#1分配的C-RNTI的长度，但是还要考虑到减少H-RNTI的长度可以提升传输的可靠性，因此H-RNTI的长度可以小于等于该接入网设备#1为UE#1分配的I-RNTI的长度。优选的而非限定，H-RNTI位长保守地可以在48-56比特之间，含48和56比特。如果该接入网络设备#1为了节省成本，存储能力较弱，则H-RNTI可以根据接入网络设备#1的实际存储能力来确定，如果接入网络设备#1只能存储128个配置信息，则H-RNTI可以为7比特。另外，接入网络设备#1还可以根据服务终端的数量多少来确定，例如如果接入网络设备同时能够服务200个终端，则H-RNTI的码长可以跟200接近，例如H-RNTI可以取8比特(对应256个终端)。该标识信息也可以是UE#1的其他标识，作为示例而非限定，例如，UE#1的设备标识。进一步地，如果一个接入网设备#1保存的多个UE的配置信息#A有重复的部分，重复的部分可以只保存一份，不同的部分根据索引标识码单独保存，从而可以节省接入网设备#1的存储空间。
作为示例而非限定，在本申请中，指示信息#B的发送方式可以有以下两种方式：
方式三：
UE#1可以将指示信息#B承载于指示RRC连接释放或RRC连接重配置请求的UE#1 assistance information用户设备辅助信息中，发给接入网设备#1。此情况下，接入网设备#1根据指示信息#B的指示保存当前配置信息，并释放或重配置与UE#1的RRC连接。RRC连接重配置请求，指UE#1请求断开或离开与该接入网设备#1的RRC连接，接入其他的接入网设备，也就是通常意义上的切换请求。
方式四：
UE#1可以直接将指示信息#B作为一个独立的信息单独发送给接入网设备#1。此情况下，指示信息#B指示接入网设备#1在释放或重配置与UE#1的RRC连接时，保存接入网设备#1为UE#1配置的部分或全部配置信息，也就是说，当前并不需要释放或重配置UE#1与接入网设备#1的RRC连接，UE#1只是通过指示信息#B通知接入网设备#1在释放或重配置RRC连接时要保存配置信息#A。
接入网设备#1接收UE#1发送的指示信息#B，根据指示信息#B,在释放或者重配置 RRC连接时，保存配置信息#A。
UE#1在释放或更新与该接入网设备#1的RRC连接前保存配置信息#A。
在一种可能的实施方式中，接入网设备#1在接收到UE#1发送的指示信息#B后，还可以对该UE#1的配置信息中的RRC参数进行更新，并且向UE#1发送指示信息#C，在指示信息#C中指示UE#1保留本次更新后的参数并将更新后的参数信息作为该接入网设备#1的配置信息#A。也就是说，下次重复接入该接入网设备#1时，UE#1和接入网设备#1采用更新后的参数配置来恢复RRC连接。具体地，参数更新指的是RRC配置参数较多时，有可能存在部分参数发生变化，需要进行调整。
在一种可能的实施方式中，UE#1的配置信息#A还可以保存在其他网络节点。例如其他接入网设备，或者核心网设备。接入网设备#1可以按照预先确定的规则，将UE#1的配置信息#A保持在接入网设备#1，或其他接入网设备，或者核心网设备。如果确定保存在接入网设备#1之外的其他设备，则进一步的，还包括接入网设备#1将UE#1的配置信息#A发送给其他设备，配置信息#A至少包括接入网设备#1的小区标识、UE#1的设备标识、接入网设备#1的无线接入网区域标识、配置信息#A的信息标识H-RNTI中的至少一个。
接入网设备#1与UE#1保存了配置信息#A并释放了接入网络设备#1和UE#1的RRC连接，UE#1进入空闲态或直接离开该接入网设备#1，在此情况下，该UE#1需要再次接入该接入网设备#1时，可以采用保存的配置信息#A进行RRC过程中参数的确定来恢复RRC连接，实现数据传输，以节省信令传输冗余。
以下对UE#1与接入网设备#1再次进行RRC连接的方式进行说明，以下实施例以RRC过程中的建立RRC连接为例进行说明。
S408，UE#1向接入网设备#1发送指示信息#D(第一指示信息中的一例)，该指示信息#D用于指示该接入网设备#1该UE#1存有配置信息#A，该配置信息#A包括该接入网设备#1为该UE#1配置的部分或全部配置信息。
指示信息#D进一步的，可以包括UE#1的设备标识、配置信息#A的信息标识H-RNTI中的至少一个。
在一种可能的实施方式中，接入网设备#1接收信息#D，根据指示信息#D确定UE#1存有配置信息#A。
S409，接入网设备#1确定是否保存配置信息#A并确定配置信息#B(第二上下文信息中的一例)，该配置信息#B为该接入网设备#1与UE#1再次建立RRC连接时的配置信息。
在一种可能的实现方式中，接入网设备#1根据接入请求信息中的UE#1的设备标识查询保存的该UE#1的配置信息#A，确定是否保存该UE#1的配置信息#A，根据配置信息#A确定配置信息#B。
在一种可能的实施方式中，接入网设备#1还可以直接根据保存的配置信息#A的信息标识匹配到该UE#1的配置信息#A，根据配置信息#A确定配置信息#B。
在一种可能的实现方式中，UE#1向接入网设备#1发送指示信息#D之前，S407，UE#1可以先确认是否存有配置信息#A，UE#1可以根据接入网设备#1的小区标识判断是否保存有该接入网设备#1的配置信息#A。其中，接入网设备#1可以通过广播或组播的方式发出小区标识信息。
应理解，该配置信息#A可以为该UE#1在历史接入该接入网设备#1时该接入网设备 #1指示该UE#1保存的部分或全部配置信息，例如接入网设备#1和UE#1在最近的RRC连接释放或重配置过程中保存的部分或全部配置信息；或者，网络设备认为当前配置信息为给UE#1的较佳配置，如比较稳定的配置，并通知UE#1保存当前RRC配置作为配置信息#A；或者，该配置信息#A为该UE#1历史接入该接入网设备#1时该UE#1自主确定的配置信息，例如UE#1主动确定当前配置为较佳配置并保存为配置信息#A，并通知接入网设备#1保留当前配置为配置信息#A。
作为示例而非限定，在本申请中，该指示信息#D可以指示该接入网设备该UE#1保留配置信息#A；或者，该指示信息#D还可以用来确认该接入网设备#1是否保留该UE#1的配置信息#A，也就是说，接入网设备#1可能在与该UE#1断开时未保存或丢失保存的配置信息#A；或者，该指示信息#D还可以包括标识信息。
上述实现方式中的标识信息可以为接入网设备#1为多个UE保留其独立的配置信息#A时，接入网设备#1为UE#1分配的用于指示接入网设备#1为UE#1单独分配的配置信息#A，也就是说，接入网设备#1使用该标识信息可以索引到已经保存的该UE#1的配置信息#A。该标识信息例如H-RNTI。也可以为UE ID，或是其他终端标识。
作为示例而非限定，在本申请中，指示信息的发送方式可以有以下两种方式：
方式五：
UE#1可以将指示信息#D承载于RRC连接建立请求或者RRC连接重建请求或RRC连接重配置请求信息中，即UE#1在向接入网设备#1发送RRC连接建立请求或者RRC连接重建请求或RRC连接重配置请求时，发送该指示信息#D。
方式六：
UE#1可以直接将指示信息#D作为一个独立的信息单独发送给接入网设备#1。此情况下，UE#1不一定发起RRC连接建立请求或者RRC连接重建请求或RRC连接重配置请求，也可能由接入网设备#1发起。
应理解，如果UE#1确认未保存或丢失配置信息#A，则UE#1可以不发送指示信息#D或在指示信息#D中指示该UE#1没有保存该接入网设备#1为该UE#1配置的配置信息#A。
接入网设备#1接收到UE#1发送的指示信息#D，可以获知该UE#1为保存配置信息#A的UE#1，接入网设备#1可以进一步判断是否保留有该UE#1的配置信息#A。进一步地，如果该接入网设备#1为多个UE#1保存了配置信息#A，该指示信息包含标识码，接入网设备#1可以使用该标识码作为索引，去匹配相应地配置信息#A。
作为示例而非限定，在本申请中，对配置信息#B的确定可以有以下几种情况：
情况一：
如果接入网设备#1确定存有该UE#1的配置信息#A(配置一)，接入网设备#1则进一步确定是否采用配置信息#A作为该次连接的初始配置。具体如下：
如果接入网设备#1在切换或者重配置时，接入网设备#1确定可以获取切换前或者重配置前的配置信息(配置二)，接入网设备#1可以进一步判断采用配置一和采用配置二哪种配置更节省信令，从而选择更加节省信令的配置作为配置信息#B；
如果接入网设备#1在恢复RRC连接时，接入网设备#1确定可以获得UE#1在RRC挂起之前存储的配置信息(配置三)，接入网设备#1可以进一步判断采用配置一和采用配置三哪种配置更节省信令，从而选择更加节省信令的配置作为配置信息#B。
情况二：
如果该接入网设备#1确定未保存该UE#1的配置信息#A或未查找到该UE#1的配置信息#A，接入网设备#1可以采用缺省配置(配置零)作为配置信息#B；
情况三：
接入网设备#1确定是否可以获得该UE#1的配置信息#A，如果可以获得该UE#1的配置信息#A，则接入网设备#1可以采用配置信息#A作为配置信息#B与UE#1建立RRC连接，作为示例而非限定，例如，接入网设备#1可以从其他网络节点获取该UE#1的配置信息#A；
或者，接入网设备#1确定可以获得该UE#1的配置信息#A，并且在切换或者重配置时，接入网设备#1确定可以获取切换前或者重配置前的配置信息(配置二)，接入网设备#1可以进一步判断采用配置一和采用配置二哪种配置更节省信令，从而选择更加节省信令的配置作为配置信息#B；
或者，接入网设备#1确定可以获得该UE#1的配置信息#A，并且在恢复RRC连接时，接入网设备#1确定可以获得UE#1在RRC挂起之前存储的配置信息(配置三)，接入网设备#1可以进一步判断采用配置一和采用配置三哪种配置更节省信令，从而选择更加节省信令的配置作为配置信息#B。
在一种可能的实施方式中，接入网设备#1确定配置信息#B之后，接入网设备#1在配置信息#A的基础上，还可以进一步进行RRC重配置，具体地，接入网设备#1为某参数配置新的取值，并将该重新配置参数的取值发送给UE#1，配置信息#A中未进行重新配置的参数不发送，例如，配置信息#A包括参数A和参数B，参数A和参数B的取值分别为A1和B1，接入网设备#1对参数A进行重新配置为A2，接入网设备#1将参数A2发送给UE#1。从而可以减少接入网设备#1给UE#1发送的配置信令负载。
在S410，接入网设备#1向UE#1发送指示信息#E(第二指示信息中的一例)，该指示信息#E用于指示UE#1根据配置信息#B与该接入网设备#1建立第二RRC连接。
具体的，该指示信息#E可以是接入网设备#1发送的RRC配置消息，该RRC配置消息包括RRC连接建立消息、RRC连接重建立消息、RRC连接重配置消息中的至少一个。
需要说明的是，该指示信息#E包括接入网设备#1确定的配置信息#B，具体为采用哪种配置作为配置信息#B。
在一种可能的实施方式中，该指示信息#E还包括接入网设备#1在配置信息#B的基础上对部分参数进行重配置的参数取值，也就是说，接入网设备#1除了将确定的配置信息#B发送给UE#1，还要将重配置的参数取值发送给UE#1，应理解，没有重新配置的参数不会发送。
具体的，UE#1根据接收到的指示信息#E中包括的配置信息#B，确定采用配置信息#B作为初始配置参数。应理解，配置信息#B可能为配置一，或配置二，或配置三，或配置零。具体来说，如果为配置一，则UE#1可以采用配置信息#A作为配置的初始配置进行参数配置；如果为配置二，则UE#1可以采用切换前或者重配置前的配置信息作为配置的初始配置进行参数配置；如果为配置三，则UE#1可以采用在RRC挂起之前存储的配置信息作为配置的初始配置进行参数配置；如果为配置零，则UE#1可以采用缺省配置作为配置的初始配置进行参数配置。
在一种可能的实施方式中，UE#1还可以收到指示信息#E中包含的重配置参数的取值，UE#1根据该参数取值确定对应参数的取值，采用重置的参数作为配置的初始配置进行参数配置。
UE#1接收指示信息#E，UE#1根据指示信息#E与接入网设备#1建立第二RRC连接。
因此通过本申请实施例，再次接入历史接入网设备时，可以根据终端设备和接入网设备保留的配置信息进行RRC过程(包括但不限于RRC建立过程、RRC重建过程、RRC重配置过程、RRC恢复过程、RRC重定向过程、切换过程、RRC重置过程中的一个或多个)，无需发送全部配置信息，节省了系统开销。
图5示出了本申请具体实施例提供的通信方法的另一例示意性流程图。该方法可以应用于图1和图2所示通信系统中。
下文实施例，为区分且不失一般性，接入网设备#1是网络设备作为其中一个配置节点的一个示例，接入网设备#2是网络设备作为其中另一个配置节点的一个示例，UE#1是终端设备作为被配置节点的一个示例。应理解，每个网络设备的覆盖范围可以被抽象为一个或多个小区，小区可以是网络设备的无线网络覆盖范围内的区域，在本申请中，不同的网络设备可以对应不同的小区，例如，接入网设备#1的网络覆盖范围区域为小区#1，接入网设备#2的网络覆盖范围区域为小区#2，应理解，在本实施例的方法中，接入网设备#1和接入网设备#2为同一个无线接入网通知区域(RAN-Based Notification Area，也简称为无线接入网区域RAN Area)中的不同的网络设备，该RAN Area是基于RAN的通知区域，可以覆盖一个小区或者多个小区，并在核心网配置的注册区范围内。需要说明的是，本实施例仅仅是示例性的不应该对本申请构成任何限定。配置节点也可以是网络设备的其他网元或是具有配置功能的终端设备，被配置节点也可以是终端设备的其他设备或是可以被配置的网络设备。
方法500可以包括如下步骤。
其中，步骤S501-步骤S506涉及一种具体的实施方法，与实施例一中S401-步骤S406相同，在此不再赘述。
其中，步骤S501-步骤S506另一种具体的实施方法，与实施例一中S401-步骤S406基本相同，不同之处在于，实施例一中是接入网设备#1与UE#1在释放或重配置接入网设备#1与UE#1的RRC连接时保存配置信息#A，实施例二的第二种实施方法中，接入网设备#1与UE#1在断开RRC连接且UE#1离开当前RAN Area，RAN Area#1时，UE#1保存接入网设备#1的配置信息#A*(可以作为第一上下文信息的一例)，该配置信息#A*为在RAN Area#1时接入网设备#1为UE#1配置的部分或全部配置信息，也就是说，接入网设备#1是UE#1离开RAN Area#1的最后一个服务小区。
UE离开当前RAN Area#1，接入网设备#1与UE#1保存了配置信息#A*并释放RRC连接，应理解，UE#1的配置信息#A*可以保存在接入网设备#1或者其他网络节点。例如其他接入网设备，或者核心网设备。接入网设备#1可以按照事先确定的规则，将UE#1的配置信息#A保持在接入网设备#1，或其他接入网设备，或者核心网设备。如果确定保存在接入网设备#1之外的其他设备，则进一步的，还包括，接入网设备#1将UE#1的配置信息#A发送给其他设备，配置信息#A至少包括接入网设备#1的小区标识、UE#1的设备标识、接入网设备#1的无线接入网区域标识、配置信息#A的信息标识H-RNTI中的至少 一个。例如，RAN Area#1中的任意接入网设备都可以保存该配置信息#A*。UE#1重新进入该RAN Area#1时，UE#1和接入的接入网设备可以采用保存的配置信息#A*恢复RRC连接，实现数据传输，以节省信令开销。
需要说明的是，再次进入历史RAN Area时，该UE#1可以接入任意该RAN Area内的一个小区的接入网设备，应理解，实施例二的有益效果在于，若对于一个UE来说，同一RAN Area内不同小区的RRC配置信息基本相同，因此，该UE#1可以接入该RAN Area内任意一个小区的接入网设备，并使用保存的历史接入网设备的配置信息恢复RRC连接。这种实施方法，接入网设备和UE在一个RAN Area中只需要保存一个RRC连接的历史配置信息，相对于在同一个RAN Area中保存多个不同接入网设备的RRC连接的配置信息的实施方法，这种一个RAN Area只需要保存一个RRC连接的配置信息的方法，降低了接入网络和UE的存储开销。
恢复RRC连接的方法如下。
S508，UE#1向接入网设备#2发送指示信息#F(第一指示信息中的一例)，该指示信息#F用于指示该UE#1存有RAN Area#1的配置信息#A*，该配置信息#A*包括RAN Area#的接入网设备#1为该UE#1配置的部分或全部配置信息。接入网络设备#2与接入网络设备#1在该UE#1的同一个RAN-Based Notification Area中。
需要说明的是，UE#1向接入网设备#2发送指示信息#F之前，S507，UE#1需要先确认是否存有配置信息#A*，UE#1可以根据接入网设备#2的RAN Area标识判断是否保存有该RAN Area#1的配置信息#A*。其中，接入网设备#2可以通过广播或组播的方式发出接入网设备#2的RAN Area标识信息。
应理解，该配置信息#A*可以为该UE#1在历史接入该RAN-Based Notification Area中的接入网络设备#1时，接入网设备#1指示该UE#1保存的部分或全部配置信息，例如接入网设备#1和UE#1在最近的RRC连接释放或更新过程中保存的部分或全部配置信息；或者，该配置信息#A*为该UE#1历史接入该RAN-Based Notification Area中的接入网络设备#1时，该UE#1自主确定的配置信息，例如UE#1主动确定当前配置为较佳配置并保存为配置信息#A*，并通知接入网设备#1保留当前配置为配置信息#A*。
作为示例而非限定，在本申请中，该指示信息#F可以指示UE#1保留有与RAN Area#1接入时的配置信息#A*。或者，该指示信息#F还可以用来确认该接入网设备#2是否保留该UE#1的配置信息#A*，应理解，接入网设备#2为历史接入RAN Area#1内的任意小区的接入网设备，UE#1可能在离开该RAN Area#1时将与历史接入小区#1的接入网设备#1与UE#1之间的配置信息#A*保存在接入网设备#2，也就是说，此情况下，该接入网设备#2存储了配置信息#A*。应理解，接入网设备#2也可能没有存储配置信息#A*，配置信息#A*存储UE#1最后一次在该RAN Area#1接入的接入网络小区，也就是接入网络设备#1，或配置信息#A*存储在除接入网设备#2和接入网设备#1外的接入网设备或者核心网设备。在此情况下，该指示信息#F还可以用来指示存储配置信息#A*的接入网设备为接入网设备#0，该指示信息包括该接入网设备#0的服务小区#0PCell的cell Identity。该指示信息#F还可以包括标识信息，例如标识码，该标识码为当前RAN Area#1中接入网设备#1为多个UE保留其独立的配置信息#A*时，接入网设备#1为UE#1分配的用于指示接入网设备#1为UE#1单独分配的配置信息#A*，也就是说，当前RAN Area#1无线网区域中的任意接 入网设备使用该标识码可以索引到已经保存的该UE#1的配置信息#A*。该标识码例如H-RNTI，该标识码的长度大于上述标识码长度，至少为48-56比特。该标识信息也可以为UE ID,或是其他终端标识。接入网设备#0可以是接入网设备#1，或者不同于接入网设备#1的接入网设备或核心网设备。
指示信息#F的发送方式与指示信息#B相同，为避免赘述，不进行重复说明。
S509，接入网设备#2确定是否保存配置信息#A*，没有配置信息#A*时获取配置信息#A*，并确定配置信息#B*(第三上下文信息中的一例)，该配置信息#B*为该接入网设备#2与UE#1建立RRC连接时的配置信息。该接入网设备#2与接入网设备#1处于同一RAN-Based Notification Area。
接入网设备#2接收到UE#1发送的指示信息#F，可以获知该UE#1为保存配置信息#A*的UE#1，该接入网设备#2可以进一步判断是否保留该UE#1的配置信息#A*。
在一种可能的实现方式中，接入网设备#2根据接入请求信息中的UE#1的设备标识查询保存的该UE#1的配置信息#A*，确定是否保存该UE#1的配置信息#A*。
在一种可能的实施方式中，接入网设备#2还可以直接根据配置信息#A*的信息标识H-RNTI获得该UE#1的配置信息#A*。
应理解，UE#1可能在离开该RAN Area#1时将与历史接入小区#1的接入网设备#1之间的配置信息#A*保存在接入网设备#2，进一步地，如果接入网设备#1为多个UE#1保存了配置信息#A*，该指示信息包含标识码，接入网设备#2也可以使用该标识码作为索引，去获得相应地配置信息#A*。
在一种可能的实施方式中，该接入网设备#2确认没有存储该UE#1的配置信息#A*，该接入网设备#2可以使用指示信息#F包括的服务小区#0的标识信息识别存储配置信息#A*的接入网设备#0，接入网设备#2向接入网设备#0发送请求信息#e，该请求信息#e用于请求接入网设备#0发送为该UE#1存储的配置信息#B*，该请求信息包括该UE#1的标识。接入网设备#0向接入网设备#2发送为UE#1存储的配置信息#A*，接入网设备#2获取该配置信息#A*，确定配置信息#A*作为与该UE#1恢复RRC连接的初始配置。接入网设备#0可以是接入网设备#1，或者不同于接入网设备#1的接入网设备或核心网设备。
在本申请实施例中，对配置信息#B*的确定与配置信息#B的确定方法相似，不进行重复说明。
在一种可能的实施方式中，接入网设备#2确定配置信息#B*之后，接入网设备#2在配置信息#B*的基础上，还可以进一步进行RRC重配置，具体地，接入网设备#2为某参数配置新的取值，并将该重新配置参数的取值发送给UE#1，配置信息#B*中未进行重新配置的参数不发送，例如，配置信息#B*包括参数A和参数B，参数A和参数B的取值分别为A1和B1，接入网设备#2对参数A进行重新配置为A2，接入网设备#2将参数A2发送给UE#1。从而可以减少接入网设备#2给UE#1发送的配置信令负载。
在S510，接入网设备#2向UE#1发送指示信息#G(第二指示信息中的一例)，该指示信息#G用于指示UE#1根据配置信息#B*与接入网设备#2建立第三RRC连接。
具体地，该指示信息#G可以是接入网设备#2发送的RRC配置消息，该RRC配置消息包括RRC连接建立消息、RRC连接重建立消息、RRC连接重配置消息中的至少一个。需要说明的是，该指示信息#G包括接入网设备#2确定的配置信息#B*，具体为采用哪种 配置作为配置信息#B*。
在一种可能的实施方式中，该指示信息#G还包括接入网设备#2在配置信息#B*的基础上对部分参数进行重配置的参数取值，也就是说，接入网设备#2除了将确定的配置信息#B*发送给UE#1，还要将重配置的参数取值发送给UE#1，应理解，没有重新配置的参数不会发送。
具体地，UE#1根据接收到的指示信息#G中包括的配置信息#B*，确定采用配置信息#B*作为初始配置参数。应理解，配置信息#B*可能为配置一，或配置二，或配置三。具体来说，如果为配置一，则UE#1可以采用配置信息#A*作为配置的初始配置进行参数配置；如果为配置二，则UE#1可以采用切换前或者重配置前的配置信息作为配置的初始配置进行参数配置；如果为配置三，则UE#1可以采用在RRC挂起之前存储的配置信息作为初始配置进行参数配置；如果为配置零，则UE#1可以采用缺省配置作为初始配置进行参数配置。
UE#1接收指示信息#G，UE#1根据指示信息#G与接入网设备#2建立第三RRC连接。
因此通过本申请实施例，再次接入同一RAN-Based Notification Area时，可以重用之前保存的同一个RAN Based Notification Area的同样的接入网设备或不同的接入网设备的配置信息进行RRC过程(包括但不限于RRC建立过程、RRC重建过程、RRC重配置过程、RRC恢复过程、RRC重定向过程、切换过程、RRC重置过程中的一个或多个)，无需网络设备为接入网设备发送全部配置信息，减少重复发送配置信息的信令冗余。
在实施例二中，接入网设备#2与接入网设备#1属于同一个RAN Area，同一个RAN Area的不同接入网的配置信息具有较大的相似性，这样，UE#1在一个RAN Area内保存的历史配置信息可以用于在UE#1接入到该RAN Area内的任意接入网设备，无需网络设备为接入网设备发送全部配置信息，减少重复发送配置信息的信令冗余。
进一步的，接入网设备#2与接入网设备#1还可以具有其他相似的属性，例如同一个运营商的接入网设备#2和接入网设备#1的配置信息具有较大的相似性，采用本申请实施例二类似的方法，接入网设备UE#1在一个运营商网络内保存的历史配置信息可以用于在UE#1接入到该运营商网络内的任意接入网设备，无需网络设备为接入网设备发送全部配置信息，减少重复发送配置信息的信令冗余。再例如，具有相近或相同覆盖范围的接入网设备的配置信息具有较大的相似性，例如接入网设备#1和接入网设备#2都是宏站，采用本申请实施例二类似的方法，接入网设备和UE#1保存的一个宏站的历史配置信息可以用于在UE#1接入到其他宏站设备，而无需网络设备为接入网设备发送全部配置信息，减少重复发送配置信息的信令冗余。进一步的，可以配置多于一个接入网设备为一个配置信息共享区域，采用本申请实施例二类似的方法，该配置信息共享区域的任意接入网设备和UE#1的配置信息，可以用于UE#1再次接入到该配置信息共享区域时使用，而无需网络设备为接入网设备发送全部配置信息，减少重复发送配置信息的信令冗余。
本文中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。
应理解，上述各个实施例中各个步骤仅是一种可能的实现方式，本申请实施例并不做限定。
可以理解的是，上述各个方法实施例中，由终端设备实现的方法和操作，也可以由可 用于终端设备的部件(例如芯片或者电路)实现，由网络设备(如小区A或者小区A所属的网络设备)实现的方法和操作，也可以由可用于网络设备的部件(例如芯片或者电路)实现。
上述主要从各个交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个网元，例如发射端设备或者接收端设备，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对发射端设备或者接收端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以使用硬件的形式实现，也可以使用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以使用对应各个功能划分各个功能模块为例进行说明。
以上，结合图3至图5详细说明了本申请实施例提供的方法。以下，结合图6至图10详细说明本申请实施例提供的装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
图6是本申请实施例提供的通信装置的示意性框图。该通信设备600包括收发单元610、存储单元620和处理单元630。收发单元610可以实现相应的通信功能，存储单元620可以用于存储指令和/或数据，处理单元630可以读取存储单元中的指令和/或数据，以使得通信设备实现前述方法实施例。收发单元610还可以称为通信接口或通信单元。
该通信设备600可以用于执行上文方法实施例中终端设备所执行的动作，这时，该通信设备600可以为终端设备或者可配置于终端设备的部件，收发单元610用于执行上文方法实施例中终端设备侧的收发相关的操作，存储单元620用于执行上文方法实施例中终端设备侧的数据或指令存储相关的操作，处理单元630用于执行上文方法实施例中终端设备侧的处理相关的操作。
或者，该通信设备600可以用于执行上文方法实施例中接入网设备#1(或者小区#1)以及接入网设备#2(或者小区#2)所执行的动作，收发单元610用于执行上文方法实施例中接入网设备#1(或者小区#1)以及接入网设备#2(或者小区#2)侧的收发相关的操作，存储单元620用于执行上文方法实施例中接入网设备#1(或者小区#1)以及接入网设备#2(或者小区#2)侧的存储相关的操作，处理单元630用于执行上文方法实施例中接入网设备#1(或者小区#1)以及接入网设备#2(或者小区#2)侧的处理相关的操作。
应理解，各单元执行相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
如图7所示，本申请实施例还提供一种通信设备700。该通信装置700包括处理器710，处理器710与存储器720耦合，存储器720用于存储计算机程序或指令和/或数据，处理器710用于执行存储器720存储的计算机程序或指令和/或数据，还包括收发器730，收发 器730用于信号的接收和/或发送。例如，处理器710用于控制收发器730进行信号的接收和/或发送。使得上文方法实施例中的方法被执行。
可选地，该通信装置700包括的处理器710为一个或多个。
可选地，如图7所示，该通信装置700还可以包括存储器720。
可选地，该通信装置700包括的存储器720可以为一个或多个。
可选地，该存储器720可以与该处理器710集成在一起，或者分离设置。
作为一种方案，该通信装置700用于实现上文方法实施例中由终端设备执行的操作。
例如，处理器710用于实现上文方法实施例中由终端设备执行的处理相关的操作，收发器730用于实现上文方法实施例中由终端设备执行的收发相关的操作。
作为另一种方案，该通信装置700用于实现上文方法实施例中由网络设备执行的操作。
例如，处理器710用于实现上文方法实施例中由网络设备执行的处理相关的操作，收发器730用于实现上文方法实施例中由网络设备执行的收发相关的操作。
应注意，本申请上述方法实施例可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(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)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三 种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (41)

  1. 一种通信方法，其特征在于，包括：
    第二设备从第一设备获取所述第二设备的第一上下文信息，所述第一上下文信息包括第一设备和所述第二设备之间的第一RRC连接的全部或部分配置信息，所述第一设备是所述第二设备的服务小区；
    所述第二设备接收RRC消息；
    响应于所述RRC消息，所述第二设备保持所述第一上下文信息；
    所述第二设备发送RRC连接建立请求消息，所述RRC连接建立请求消息包括第一指示信息，所述第一指示信息用于指示所述第二设备保持所述第一上下文信息；和/或
    所述第二设备接收RRC配置消息，所述RRC配置消息包括第二指示信息，所述第二指示信息用于指示所述第二设备根据所述第一上下文信息建立第二RRC连接，所述RRC配置消息包括RRC连接建立消息、RRC连接重建立消息、RRC连接重配置消息中的至少一个。
  2. 根据权利要求1所述的方法，其特征在于，所述响应于所述RRC消息，所述第二设备保持所述第一上下文信息，包括：
    所述RRC消息为RRC连接释放消息，响应于所述RRC连接释放消息，所述第二设备保持所述第一上下文信息且所述第二设备进入空闲态；或者，
    所述RRC消息为RRC连接重配置消息，响应于所述RRC连接重配置消息，所述第二设备保持所述第一上下文信息且所述第二设备离开所述第一设备。
  3. 根据权利要求1或2所述的方法，所述第一上下文信息包括所述第一设备的小区标识、所述第二设备的设备标识、所述第一设备的无线接入网区域标识、所述第一上下文的信息标识中的至少一个。
  4. 根据权利要求1至3项中任一项所述的方法，所述第二设备发送RRC连接建立请求消息之前，所述方法还包括：
    所述第二设备根据第一设备的小区标识确定所述第二设备是否保持有所述第一设备的第一上下文信息；
    所述第二设备向所述第一设备发送RRC连接建立请求消息。
  5. 根据权利要求1至4项中任一项所述的方法，其特征在于，所述方法还包括：
    所述第二设备向所述第一设备上报第三指示信息，所述第三指示信息用于指示所述第二设备具有在空闲态或离开所述第一设备后保持所述第一上下文信息的能力。
  6. 根据权利要求1至5项中任一项所述的方法，其特征在于，所述方法还包括：
    所述第二设备接收所述第一设备发送的第四指示信息，所述第四指示信息用于指示所述第一设备是否具有所述第二设备在空闲态或所述第二设备离开所述第一设备后保持所述第一上下文信息的能力。
  7. 根据权利要求1至6项中任一项所述的方法，在响应于RRC消息，所述第二设备保持所述第一上下文信息之前，所述方法还包括：
    所述第二设备确定所述第二设备为所述第一设备的常驻设备。
  8. 根据权利要求1至7项中任一项所述的方法，所述第二设备接收RRC配置消息还包括：
    所述第一设备根据所述第一上下文信息确定第二上下文信息，所述第二上下文信息与所述第一上下文信息至少部分相同；
    所述第二设备根据所述第二上下文信息，确定所述第二RRC连接的上下文信息。
  9. 一种通信方法，其特征在于，包括：
    第一设备获取第一上下文信息，所述第一上下文信息包括第一设备和第二设备之间的第一RRC连接的全部或部分配置信息，所述第一设备是所述第二设备的服务小区；
    所述第一设备发送RRC消息且保持所述第一上下文信息，所述RRC消息用于指示所述第二设备保持所述第一上下文信息；
    所述第一设备从所述第二设备接收RRC连接建立请求消息，所述RRC连接建立请求消息包括第一指示信息，所述第一指示信息用于指示所述第二设备保持有所述第一上下文信息；和/或
    所述第一设备发送RRC配置消息，所述RRC配置消息包括第二指示信息，所述第二指示信息用于指示所述第二设备根据所述第一上下文信息建立第二RRC连接，所述RRC配置消息包括RRC连接建立消息、RRC连接重建立消息、RRC连接重配置消息中的至少一个。
  10. 根据权利要求9所述的方法，其特征在于，所述RRC消息用于指示所述第二设备保持所述第一上下文信息，包括：
    所述RRC消息为RRC连接释放消息，所述RRC连接释放消息用于指示所述第二设备保持所述第一上下文信息且进入空闲态；或者，
    所述RRC消息为RRC连接重配置消息，所述RRC连接重配置消息用于指示所述第二设备保持所述第一上下文信息且离开所述第一设备。
  11. 根据权利要求9或10所述的方法，所述第一上下文信息包括所述第一设备的小区标识、所述第二设备的设备标识、所述第一设备的无线接入网区域标识、所述第一上下文的信息标识中的至少一个。
  12. 根据权利要求9至11项中任一项所述的方法，所述第一设备发送RRC配置消息之前，所述方法还包括：
    所述第一设备根据所述第二设备的设备标识、所述第一上下文的信息标识中的至少一个确定所述第一设备是否保持有所述第二设备的第一上下文信息。
  13. 根据权利要求9至12项中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收所述第二设备上报的第三指示信息，所述第三指示信息用于指示所述第二设备具有在空闲态或离开所述第一设备后保持所述第一上下文信息的能力。
  14. 根据权利要求9至13项中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备向所述第二设备发送第四指示信息，所述第四指示信息用于指示所述第一设备是否具有在空闲态和/或离开所述第一设备后保持所述第二设备的第一上下文信息的能力。
  15. 根据权利要求9至14项中任一项所述的方法，在所述第一设备保持所述第一上下文信息之前，包括：
    所述第一设备根据第一条件或第一设备的存储能力确定第二设备为所述第一设备的常驻设备。
  16. 根据权利要求9至15项中任一项所述的方法，所述第一设备发送RRC配置消息还包括：
    所述第一设备根据所述第一上下文信息确定第二上下文信息，所述第二上下文信息与所述第一上下文信息至少部分相同；
    所述第一设备根据所述第二上下文信息，确定所述第二RRC连接的上下文信息。
  17. 一种通信方法，其特征在于，包括：
    第三设备从所述第二设备接收RRC连接建立请求消息，所述RRC连接建立请求消息包括第一指示信息，所述第一指示信息用于指示所述第二设备保持有第一上下文信息；和/或
    所述第三设备发送RRC配置消息，所述RRC配置消息包括第二指示信息，所述第二指示信息用于指示所述第二设备根据第一上下文信息建立第三RRC连接，所述RRC配置消息包括RRC连接建立消息、RRC连接重建立消息、RRC连接重配置消息中的至少一个；
    所述第一上下文信息包括第一设备和所述第二设备之间的第一RRC连接的全部或部分配置信息，所述第一设备是所述第二设备的历史服务小区。
  18. 根据权利要求17所述的方法，所述第三设备发送RRC配置消息之前，所述方法还包括：
    所述第三设备根据所述第一设备标识、所述第二设备的设备标识、所述第一设备的无线接入网区域标识、所述第一上下文的信息标识中的至少一个确定所述第二设备的第一上下文信息。
  19. 根据权利要求17至18项中任一项所述的方法，所述第三设备发送RRC配置消息，所述方法还包括：
    所述第三设备根据所述第一上下文信息确定第三上下文信息，所述第三上下文信息与所述第一上下文信息至少部分相同；
    所述第三设备根据所述第三上下文信息，确定所述第三RRC连接的上下文信息。
  20. 一种通信设备，其特征在于，包括：
    收发单元，用于从第一设备获取第二设备的第一上下文信息，所述第一上下文信息包括第一设备和所述第二设备之间的第一RRC连接的全部或部分配置信息，所述第一设备是所述第二设备的服务小区；
    所述收发单元，还用于接收RRC消息；
    存储单元，用于响应于所述RRC消息,保持所述第一上下文信息；
    所述收发单元，还用于发送RRC连接建立请求消息，所述RRC连接建立请求消息包括第一指示信息，所述第一指示信息用于指示所述第二设备保持所述第一上下文信息；和/或
    还用于接收RRC配置消息，所述RRC配置消息包括第二指示信息，所述第二指示信息用于指示所述第二设备根据所述第一上下文信息建立第二RRC连接，所述RRC配置消息包括RRC连接建立消息、RRC连接重建立消息、RRC连接重配置消息中的至少一个。
  21. 根据权利要求20所述的通信设备，其特征在于，所述存储单元，用于响应于所 述RRC消息，保持所述第一上下文信息，包括：
    所述RRC消息为RRC连接释放消息，响应于所述RRC连接释放消息，所述第二设备保持所述第一上下文信息且所述第二设备进入空闲态；或者，
    所述RRC消息为RRC连接重配置消息，响应于所述RRC连接重配置消息，所述第二设备保持所述第一上下文信息且所述第二设备离开所述第一设备。
  22. 根据权利要求20或21所述的通信设备，所述第一上下文信息包括所述第一设备的小区标识、所述第二设备的设备标识、所述第一设备的无线接入网区域标识、所述第一上下文的信息标识中的至少一个。
  23. 根据权利要求20至22项中任一项所述的通信设备，所述通信设备还包括处理单元，所述处理单元用于根据所述第一设备的小区标识确定所述第二设备是否保持有所述第一设备的第一上下文信息。
  24. 根据权利要求20至23项中任一项所述的通信设备，其特征在于，所述收发单元还用于向所述第一设备上报的第三指示信息，所述第三指示信息用于指示所述第二设备具有在空闲态或离开所述第一设备后保持所述第一上下文信息的能力。
  25. 根据权利要求20至24项中任一项所述的通信设备，其特征在于，所述通信设备还用于接收所述第一设备发送的第四指示信息，所述第四指示信息用于指示所述第一设备是否具有所述第二设备在空闲态或所述第二设备离开所述第一设备后保持所述第一上下文信息的能力。
  26. 根据权利要求20至25项中任一项所述的通信设备，所述处理单元还用于确定所述第二设备为所述第一设备的常驻设备。
  27. 根据权利要求20至26项中任一项所述的通信设备，所述处理单元还用于根据所述第一上下文信息确定第二上下文信息，所述第二上下文信息与所述第一上下文信息至少部分相同；
    根据所述第二上下文信息，确定所述第二RRC连接的上下文信息。
  28. 一种通信设备，其特征在于，包括：
    收发单元，用于获取第一上下文信息，所述第一上下文信息包括第一设备和第二设备之间的第一RRC连接的全部或部分配置信息，所述第一设备是所述第二设备的服务小区；
    所述收发单元，还用于发送RRC消息且存储单元用于保持所述第一上下文信息，所述RRC消息用于指示所述第二设备保持所述第一上下文信息；
    所述收发单元，还用于接收RRC连接建立请求消息，所述RRC连接建立请求消息包括第一指示信息，所述第一指示信息用于指示所述第二设备保持有所述第一上下文信息；和/或
    还用于发送RRC配置消息，所述RRC配置消息包括第二指示信息，所述第二指示信息用于指示所述第二设备根据所述第一上下文信息建立第二RRC连接，所述RRC配置消息包括RRC连接建立消息、RRC连接重建立消息、RRC连接重配置消息中的至少一个。
  29. 根据权利要求28所述的通信设备，其特征在于，所述收发单元用于发送所述RRC消息，所述RRC消息用于指示所述第二设备保持所述第一上下文信息，包括：
    所述RRC消息为RRC连接释放消息，所述RRC连接释放消息用于指示所述第二设备保持所述第一上下文信息且进入空闲态；或者，
    所述RRC消息为RRC连接重配置消息，所述RRC连接重配置消息用于指示所述第二设备保持所述第一上下文信息且离开所述第一设备。
  30. 根据权利要求28或29所述的通信设备，其特征在于，所述第一上下文信息包括所述第一设备的小区标识、所述第二设备的设备标识、所述第一设备的无线接入网区域标识、所述第一上下文的信息标识中的至少一个。
  31. 根据权利要求28至30项中任一项所述的通信设备，其特征在于，所述通信设备还包括处理单元，所述处理单元用于根据所述第二设备的设备标识、所述第一上下文的信息标识中的至少一个判断所述第一设备是否保持有所述第二设备的第一上下文信息。
  32. 根据权利要求28至31项中任一项所述的通信设备，其特征在于，所述收发单元还用于接收所述第二设备上报的第三指示信息，所述第三指示信息用于指示所述第二设备具有在空闲态或离开所述第一设备后保持所述第一上下文信息的能力。
  33. 根据权利要求28至32项中任一项所述的通信设备，其特征在于，所述收发单元还用于向所述第二设备发送第四指示信息，所述第四指示信息用于指示所述第一设备是否具有在空闲态和/或离开所述第一设备后保持所述第二设备的第一上下文信息的能力。
  34. 根据权利要求28至33项中任一项所述的通信设备，其特征在于，所述处理单元还用于根据第一条件或第一设备的存储能力确定第二设备为所述第一设备的常驻设备。
  35. 根据权利要求28至34项中任一项所述的通信设备，所述处理单元还用于根据所述第一上下文信息确定第二上下文信息，所述第二上下文信息与所述第一上下文信息至少部分相同；
    根据所述第二上下文信息，确定所述第二RRC连接的上下文信息。
  36. 一种通信设备，其特征在于，包括：
    收发单元，用于从所述第二设备接收RRC连接建立请求消息，所述RRC连接建立请求消息包括第一指示信息，所述第一指示信息用于指示所述第二设备保持有第一上下文信息；和/或
    用于发送RRC配置消息，所述RRC配置消息包括第二指示信息，所述第二指示信息用于指示所述第二设备根据第一上下文信息建立第三RRC连接，所述RRC配置消息包括RRC连接建立消息、RRC连接重建立消息、RRC连接重配置消息中的至少一个；
    所述第一上下文信息包括第一设备和所述第二设备之间的第一RRC连接的全部或部分配置信息，所述第一设备是所述第二设备的历史服务小区。
  37. 根据权利要求36所述的通信设备，其特征在于，所述通信设备包括处理单元，所述处理单元用于根据所述第一设备标识、所述第二设备的设备标识、所述第一设备的无线接入网区域标识、所述第一上下文的信息标识中的至少一个确定所述第二设备的第一上下文信息。
  38. 根据权利要求36至37项中任一项所述的通信设备，其特征在于，所述处理单元还用于根据所述第一上下文信息确定第三上下文信息，所述第三上下文信息与所述第一上下文信息至少部分相同；
    根据所述第三上下文信息，确定所述第三RRC连接的上下文信息。
  39. 一种通信设备，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机程序，以使得所述通信装置执行权利要求1 至38中任一项所述的通信方法。
  40. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至38中任意一项所述的通信方法。
  41. 一种电路系统，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述电路系统的通信设备执行如权利要求1至38中任意一项所述的通信方法。
PCT/CN2021/070385 2021-01-06 2021-01-06 一种通信方法和装置 WO2022147671A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2021/070385 WO2022147671A1 (zh) 2021-01-06 2021-01-06 一种通信方法和装置
CN202180086394.5A CN116648992A (zh) 2021-01-06 2021-01-06 一种通信方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/070385 WO2022147671A1 (zh) 2021-01-06 2021-01-06 一种通信方法和装置

Publications (1)

Publication Number Publication Date
WO2022147671A1 true WO2022147671A1 (zh) 2022-07-14

Family

ID=82357091

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/070385 WO2022147671A1 (zh) 2021-01-06 2021-01-06 一种通信方法和装置

Country Status (2)

Country Link
CN (1) CN116648992A (zh)
WO (1) WO2022147671A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105265009A (zh) * 2013-05-15 2016-01-20 阿尔卡特朗讯公司 网络节点和方法
WO2017107073A1 (zh) * 2015-12-22 2017-06-29 华为技术有限公司 数据传输处理方法、用户设备和基站
CN107251642A (zh) * 2015-11-05 2017-10-13 株式会社Ntt都科摩 用户装置、基站以及连接建立方法
CN108353444A (zh) * 2015-11-05 2018-07-31 株式会社Ntt都科摩 用户装置、基站、连接建立方法、以及上下文信息获取方法
CN108353452A (zh) * 2015-11-05 2018-07-31 株式会社Ntt都科摩 用户装置、基站、和连接建立方法
US20180359669A1 (en) * 2016-01-25 2018-12-13 Kyocera Corporation Communication method, radio terminal, and base station

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105265009A (zh) * 2013-05-15 2016-01-20 阿尔卡特朗讯公司 网络节点和方法
CN107251642A (zh) * 2015-11-05 2017-10-13 株式会社Ntt都科摩 用户装置、基站以及连接建立方法
CN108353444A (zh) * 2015-11-05 2018-07-31 株式会社Ntt都科摩 用户装置、基站、连接建立方法、以及上下文信息获取方法
CN108353452A (zh) * 2015-11-05 2018-07-31 株式会社Ntt都科摩 用户装置、基站、和连接建立方法
WO2017107073A1 (zh) * 2015-12-22 2017-06-29 华为技术有限公司 数据传输处理方法、用户设备和基站
US20180359669A1 (en) * 2016-01-25 2018-12-13 Kyocera Corporation Communication method, radio terminal, and base station

Also Published As

Publication number Publication date
CN116648992A (zh) 2023-08-25

Similar Documents

Publication Publication Date Title
US20220248254A1 (en) Method of processing network slice based congestion, device and system thereof
CN108024221B (zh) 一种寻呼方法、基站及终端
US20210144606A1 (en) Path switching method, apparatus and system
US20200396652A1 (en) Method, apparatus, computer program product and computer program for conditional handover
WO2018019001A1 (zh) 一种终端状态转换方法及装置
US10057937B2 (en) Communications via multiple access points
CN110383939B (zh) 无线终端、基站及其方法和非暂时性计算机可读介质
WO2021238774A1 (zh) 通信方法及装置
EP3565350B1 (en) Method and device for establishing wireless connection
JP7262383B2 (ja) 共通処理実施方法、装置、及びシステム
US20230209450A1 (en) Mobility management method and apparatus
EP3532969A1 (en) Access category handling for wireless communication systems
EP4007346A1 (en) Master node, secondary node, and method thereof
KR20220044341A (ko) 보안 보호 모드 결정 방법 및 장치
US20230171823A1 (en) Information transmission method, network device and terminal
WO2021026706A1 (zh) 一种f1接口管理方法及装置
US20240098830A1 (en) Communication method and apparatus
US20230099930A1 (en) Communications method and communications apparatus
WO2023213140A1 (zh) 通信方法、资源配置方法、设备、网络节点、系统及介质
WO2021103026A1 (zh) 在带宽部分上进行通信的方法
WO2022147671A1 (zh) 一种通信方法和装置
WO2022022394A1 (zh) 一种终端设备的状态指示方法及通信装置
WO2021197029A1 (zh) 一种先听后说lbt失败指示方法及装置
WO2022141301A1 (zh) 通信方法、装置和系统
WO2019228459A1 (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: 21916729

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180086394.5

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21916729

Country of ref document: EP

Kind code of ref document: A1