WO2022082688A1 - 一种通信方法、装置及系统 - Google Patents

一种通信方法、装置及系统 Download PDF

Info

Publication number
WO2022082688A1
WO2022082688A1 PCT/CN2020/123022 CN2020123022W WO2022082688A1 WO 2022082688 A1 WO2022082688 A1 WO 2022082688A1 CN 2020123022 W CN2020123022 W CN 2020123022W WO 2022082688 A1 WO2022082688 A1 WO 2022082688A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
network node
segment
configuration
multicast
Prior art date
Application number
PCT/CN2020/123022
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/CN2020/123022 priority Critical patent/WO2022082688A1/zh
Publication of WO2022082688A1 publication Critical patent/WO2022082688A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements

Definitions

  • the present application relates to the field of communication, and in particular, to a communication method, device and system.
  • DTLS Datagram transport layer security
  • SCTP stream control transmission protocol
  • IETF Internet Engineering Task Force
  • SCAS security assurance specification
  • DTLS has limitations.
  • LTE long term evolution
  • the interface between base stations, the interface between the base station and the core network, and the interface between the centralized unit (CU) and the distributed unit (DU) in the base station all use the SCTP protocol , that is to say, the DTLS protocol may exist on the above interfaces.
  • the information transmitted by the above-mentioned interface may not be completely transmitted.
  • Embodiments of the present application provide a communication method, apparatus, and system. By instructing the first network node to perform full configuration by the first information, the drawback caused by incomplete information transmission can be solved.
  • a first aspect of the embodiments of the present application provides a communication method, and the method may be executed by a communication apparatus, or may be executed by a component of the communication apparatus (for example, a processor, a chip, or a chip system, etc.).
  • the communication device may be an access network device or a core network device.
  • the method includes: sending first information to a first network node, where the first information is used to instruct the first network node to perform a full configuration; receiving first configuration information, where the first configuration information is a configuration generated by the first network node in the full configuration information, the first configuration information is used for the terminal device to communicate with the first network node.
  • the first information is sent to the first network node, where the first information is used to instruct the first network node to perform full configuration, and the first configuration information is received, where the first configuration information is that the first network node is in full configuration
  • the generated configuration information, and the first configuration information is used for the terminal device to communicate with the first network node.
  • the first information in the above steps includes a first field, and the first field is used to instruct the first network node to perform full configuration.
  • that the first information includes the first field may be understood that the first information is the first field, or the first information includes the first field.
  • the first field is a 1-bit field, that is, a 1-bit "1" or "0" can be used to indicate whether the first network node performs full configuration.
  • the first field is used to instruct the first network node to perform full configuration, so as to reduce the number of bits of the exchanged first information, thereby reducing the transmission delay.
  • the first network node is instructed to perform the full configuration in an explicit manner, so as to reduce the delay in the judgment of the first network node.
  • the first information in the above steps includes RRC reconfiguration information, and the RRC reconfiguration information at least does not include cell group configuration information, radio bearer configuration information, and measurement configuration information. one or more of.
  • the first network node may also perform full configuration according to the first information to avoid The RRC reconfiguration information is incomplete, resulting in the failure of the first network node to perform subsequent actions.
  • the first network node is implicitly instructed to perform full configuration, and after receiving the first information, the first network node may determine that the number of bits of the second information is greater than or equal to the first threshold, that is, the first information If the incomplete second information is included, the first network node performs the full configuration, so as to avoid the failure of the first network node to perform subsequent actions due to the first information including the incomplete second information.
  • the first information and the second information in the above steps are handover request information.
  • the first network node may perform full configuration according to the first information, thereby ensuring that the handover is successful.
  • the execution body is a third network node, and in the above steps: sending the first information to the first network node includes: the third network node sending the first network node Sending the first information; the above steps further include: the third network node receives third information, where the third information is used to instruct the first network node to perform full configuration.
  • the execution subject is the third network node. If the third network node is a core network device, before sending the first information, it may also receive the third information, and generate the first information according to the third information. Therefore, the communication method can be applied not only between access network devices, but also between core network devices and access network devices.
  • a second aspect of the embodiments of the present application provides a communication method, and the method may be executed by a communication apparatus, or may be executed by a component of the communication apparatus (for example, a processor, a chip, or a chip system, etc.).
  • the communication apparatus may be an access network device.
  • the method includes: receiving first information, where the first information is used to instruct the first network node to perform full configuration; performing full configuration, and generating first configuration information in the full configuration, where the first configuration information is used to communicate with the terminal device;
  • the second network node sends the first configuration information.
  • the receiving of the first information may be received from the second network node, or may be received from the third network node.
  • first information is received, where the first information is used to instruct the first network node to perform full configuration, perform full configuration, and generate first configuration information in the full configuration, where the first configuration information is that the first network node is in The configuration information generated in the full configuration, and the first configuration information is used for the terminal device to communicate with the first network node, and the communication with the terminal device can be realized by sending the first configuration information to the second network node.
  • the first information in the above steps includes a first field, and the first field is used to indicate that full configuration is performed.
  • the first field is used to instruct the first network node to perform full configuration, so as to reduce the number of bits of the exchanged first information, thereby reducing the transmission delay.
  • the first network node is instructed to perform the full configuration in an explicit manner.
  • the first information in the above steps includes RRC reconfiguration information, and the RRC reconfiguration information does not include at least cell group configuration information, radio bearer configuration information, and measurement configuration information. one or more of.
  • the first network node may also perform full configuration according to the first information to avoid The RRC reconfiguration information is incomplete, resulting in the failure of the first network node to perform subsequent actions.
  • the first network node is implicitly instructed to perform full configuration, and after receiving the first information, the first network node may determine that the number of bits of the second information is greater than or equal to the first threshold, that is, the first information If the incomplete second information is included, the first network node performs the full configuration, so as to avoid the failure of the first network node to perform subsequent actions due to the first information including the incomplete second information.
  • the first information and the second information in the above steps are handover request information.
  • the first network node may perform full configuration according to the first information, thereby ensuring that the handover is successful.
  • a third aspect of the embodiments of the present application provides a communication method, and the method may be executed by a communication apparatus, or may be executed by a component of the communication apparatus (for example, a processor, a chip, or a chip system, etc.).
  • the communication device may be an access network device or a core network device.
  • the method includes: if a preset condition is met, sending multiple segments of first information to a first network node, the first information includes an RRC container, and the information carried in the RRC container includes RRC reconfiguration information and/or capabilities of the terminal device
  • the preset condition is at least one of the following: the number of bits of the capability information is greater than or equal to the first threshold, and the capability information comes from the terminal device; the total number of bits of the RRC container is greater than or equal to the first threshold; the total number of bits of the first information is greater than or equal to the first threshold equal to the first threshold.
  • the second network node if the preset conditions are met, the second network node sends the first information in a segmented manner, so as to avoid being unable to transmit the complete first information with the first network node when the first information exceeds the limit.
  • sending multiple segments of the first information to the first network node in the above steps includes: sending multiple pieces of fourth information, one segment of the first information It is carried by a fourth message.
  • the multiple segments in the above steps include: at least one first segment, where the first segment is information in the RRC container.
  • the second network node sends the information in the RRC container in a segmented manner, so as to avoid being unable to transmit with the first network node when the information in the RRC container exceeds the limit The complete information in the RRC container.
  • the multiple segments in the above steps further include: a second segment, where the second segment is the first segment of the first information.
  • the first segment means that the number of the second segment is 1, that is, the second segment may be a segment first sent by the second network node to the first network node (that is, the second segment may be The first segment in time), or it may not be the first segment sent (that is, the second segment may not be the first segment in time).
  • the first network node can receive the second segment before receiving the last segment, that is, after receiving the second segment, the first network node can perform subsequent operations in advance, compared with receiving all segments. After the segment, the subsequent actions are processed to reduce the processing delay of the network.
  • the RRC container such as cells, IEs, etc.
  • the segments of the first information in the above steps include one or more of the following information: a first numerical value, used to indicate the number of segments; second field, the second field is used to indicate that the first information is segmented information; the third field is used to indicate that the segment is a segment of the first information; the fourth field is used to indicate the number of the segment; capability information ; information in the RRC container.
  • the first network node may determine an attribute of the first information (for example, the the number of segments of a message, etc.).
  • a fourth aspect of the embodiments of the present application provides a communication method, and the method may be executed by a communication apparatus, or may be executed by a component of the communication apparatus (for example, a processor, a chip, or a chip system, etc.).
  • the communication apparatus may be core network equipment or access network equipment.
  • the method includes: receiving multiple segments of first information, where the first information includes an RRC container, the information carried in the RRC container includes RRC reconfiguration information and/or capability information of a terminal device, and the multiple segments are from the second network Node; assembles multiple segments.
  • the first network node receives and assembles multiple segments of the first information in a segmented manner, so as to avoid being unable to transmit the complete first information with the second network node when the first information exceeds the limit .
  • receiving multiple segments of the first information in the above steps includes: receiving multiple fourth information, and one segment of the first information is composed of one fourth information. information is carried.
  • the multiple segments in the above steps include: at least one first segment, where the first segment is information in the RRC container.
  • the first network node sends the information in the RRC container in a segmented manner, so as to avoid being unable to transmit the complete information in the RRC container with the second network node when the information in the RRC container exceeds the limit. information.
  • the multiple segments in the above steps further include: a second segment, where the second segment is the first segment of the first information.
  • the first segment means that the number of the second segment is 1, that is, the second segment may be a segment first sent by the second network node to the first network node (that is, the second segment may be The first segment in time), or it may not be the first segment sent (that is, the second segment may not be the first segment in time).
  • the first network node can receive the second segment before receiving the last segment, that is, after receiving the second segment, the first network node can perform subsequent operations in advance, compared with receiving all segments. After the segment, the subsequent actions are processed to reduce the processing delay of the network.
  • the RRC container such as cells, IEs, etc.
  • the segments of the first information in the above steps include one or more of the following information: a first numerical value, used to indicate the number of segments; a second field, the second field is used to indicate that the first information is segmented information; the third field is used to indicate that the segment is a segment of the first information; the fourth field is used to indicate the number of the segment; capability information ; information in the RRC container.
  • a fifth aspect of the embodiments of the present application provides a communication apparatus, where the communication apparatus may be core network equipment or access network equipment, or may be a component of core network equipment or access network equipment (for example, a processor, a chip, or a chip system) , the communication device includes:
  • a transceiver unit configured to send first information to the first network node, where the first information is used to instruct the first network node to perform full configuration
  • the transceiver unit is further configured to receive first configuration information, where the first configuration information is configuration information generated by the first network node in the full configuration, and the first configuration information is used for the terminal device to communicate with the first network node.
  • the above-mentioned first information includes a first field, and the first field is used to instruct the first network node to perform full configuration.
  • the above-mentioned first information includes RRC reconfiguration information
  • the RRC reconfiguration information does not include at least cell group configuration information, radio bearer configuration information, and measurement configuration information. one or more.
  • the above-mentioned first information used to instruct the first network node to perform full configuration includes: the first information is used to indicate that the number of bits of the second information is greater than or equal to the first threshold, the second information is used by the first network node to generate second configuration information, and the second configuration information is used by the terminal device to communicate with the first network node.
  • the above-mentioned first information and second information are handover request information.
  • the above-mentioned transceiver unit is a transceiver unit of a third network node, and the transceiver unit of the third network node is configured to send the first information to the first network node;
  • the transceiver unit of the third network node is further configured to receive third information, where the third information is used to instruct the first network node to perform full configuration.
  • a sixth aspect of an embodiment of the present application provides a communication device, where the communication device may be an access network device or a component of the access network device (for example, a processor, a chip, or a chip system), and the communication device includes:
  • a transceiver unit configured to receive first information, where the first information is used to instruct the first network node to perform full configuration
  • a processing unit configured to perform a full configuration, and generate first configuration information in the full configuration, and the first configuration information is used to communicate with the terminal device;
  • the transceiver unit is further configured to send the first configuration information to the second network node.
  • the above-mentioned first information includes a first field, and the first field is used to indicate that full configuration is performed.
  • the above-mentioned first information includes RRC reconfiguration information
  • the RRC reconfiguration information does not include at least cell group configuration information, radio bearer configuration information, and measurement configuration information. one or more.
  • the above-mentioned first information used to instruct the first network node to perform full configuration includes: the first information is used to indicate that the number of bits of the second information is greater than or equal to the first threshold, the second information is used by the first network node to generate second configuration information, and the second configuration information is used by the terminal device to communicate with the first network node.
  • the above-mentioned first information and second information are handover request information.
  • a seventh aspect of an embodiment of the present application provides a communication apparatus, where the communication apparatus may be core network equipment or access network equipment, or may be a component of core network equipment or access network equipment (for example, a processor, a chip, or a chip system) , the communication device includes:
  • a transceiver unit configured to send multiple segments of the first information to the first network node if a preset condition is met, the first information includes the RRC container, and the information carried in the RRC container includes the RRC reconfiguration information and/or the information of the terminal device.
  • capability information is at least one of the following: the number of bits of the capability information is greater than or equal to the first threshold, and the capability information comes from the terminal device; the total number of bits of the RRC container is greater than or equal to the first threshold; the total number of bits of the first information is greater than or equal to the first threshold or equal to the first threshold.
  • the transceiver unit in the above communication device is specifically configured to send multiple pieces of fourth information, and one segment of the first information is carried by one piece of fourth information.
  • the above-mentioned multiple segments include: at least one first segment, where the first segment is information in the RRC container.
  • the above-mentioned multiple segments further include: a second segment, where the second segment is the first segment of the first information.
  • the segment of the above-mentioned first information includes one or more of the following information: a first numerical value, used to indicate the number of segments; a second field , the second field is used to indicate that the first information is segmented information; the third field is used to indicate that the segment is a segment of the first information; the fourth field is used to indicate the number of the segment; capability information; Information in the RRC container.
  • An eighth aspect of an embodiment of the present application provides a communication device, where the communication device may be core network equipment or access network equipment, or may be a component of core network equipment or access network equipment (for example, a processor, a chip, or a chip system) , the communication device includes:
  • a transceiver unit configured to receive multiple segments of the first information, the first information includes an RRC container, the information carried in the RRC container includes RRC reconfiguration information and/or capability information of the terminal device, and the multiple segments come from the second network node;
  • Processing unit for assembling multiple segments.
  • the transceiver unit in the above communication device is specifically configured to receive multiple pieces of fourth information, and a segment of one piece of the first information is carried by one piece of fourth information.
  • the above-mentioned multiple segments include: at least one first segment, where the first segment is information in the RRC container.
  • the above-mentioned multiple segments further include: a second segment, where the second segment is the first segment of the first information.
  • the segment of the above-mentioned first information includes one or more of the following information: a first numerical value, used to indicate the number of segments; a second field , the second field is used to indicate that the first information is segmented information; the third field is used to indicate that the segment is a segment of the first information; the fourth field is used to indicate the number of the segment; capability information; Information in the RRC container.
  • a ninth aspect of an embodiment of the present application provides a communication device, where the communication device may be a core network device or an access network device, or a component (for example, a processor, a chip, or a chip system) of the core network device or the access network device. ), the communication apparatus performs the method in the foregoing first aspect or any possible implementation manner of the first aspect, or the communication apparatus performs the foregoing third aspect or the method in any possible implementation manner of the third aspect.
  • a tenth aspect of an embodiment of the present application provides a communication device, where the communication device may be an access network device or a component of the access network device (for example, a processor, a chip, or a chip system), and the communication device executes the foregoing first step.
  • the method in the second aspect or any possible implementation manner of the second aspect, or the communication device performs the method in the foregoing fourth aspect or any possible implementation manner of the fourth aspect.
  • An eleventh aspect of an embodiment of the present application provides a communication device, including: a processor, where the processor is coupled to a memory, and the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the communication device can implement the above-mentioned The method in the first aspect or any possible implementation manner of the first aspect, or the communication apparatus performs the method in the aforementioned third aspect or any possible implementation manner of the third aspect.
  • a twelfth aspect of an embodiment of the present application provides a communication device, including: a processor, where the processor is coupled to a memory, and the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the communication device can implement the above-mentioned
  • the method in the second aspect or any possible implementation manner of the second aspect, or the communication apparatus performs the method in the foregoing fourth aspect or any possible implementation manner of the fourth aspect.
  • a thirteenth aspect of an embodiment of the present application provides a communication system, including the communication device provided in the ninth aspect, and/or the communication device in the tenth aspect.
  • a fourteenth aspect of an embodiment of the present application provides a communication system, including the communication device provided in the eleventh aspect, and/or the communication device in the twelfth aspect.
  • a fifteenth aspect of the embodiments of the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed on a computer, cause the computer to execute the foregoing first aspect or any of the first aspects.
  • a sixteenth aspect of the embodiments of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the foregoing first aspect or any possible implementation manner of the first aspect, the second aspect or the second aspect A method in any possible implementation of the aspect, the third aspect or any possible implementation of the third aspect, the fourth aspect or any possible implementation of the fourth aspect.
  • the embodiments of the present application at least include the following advantages: sending first information to the first network node, where the first information is used to instruct the first network node to perform full configuration, receiving the first configuration information, first The configuration information is the configuration information generated by the first network node in the full configuration, and the first configuration information is used for the terminal device to communicate with the first network node.
  • FIG. 1 is a schematic diagram of a communication system in an embodiment of the application.
  • FIG. 2 is a network frame diagram of handover between base stations in an embodiment of the present application
  • FIG. 3 is a network frame diagram of cross-core network handover in an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a communication method in an embodiment of the present application.
  • FIG. 5 is another schematic flowchart of the communication method in the embodiment of the present application.
  • FIG. 6 is another schematic flowchart of the communication method in the embodiment of the present application.
  • FIG. 7 is another schematic flowchart of the communication method in the embodiment of the application.
  • FIG. 8 is a schematic diagram of a tracking area list in an embodiment of the present application.
  • FIG. 9 is another schematic flowchart of the communication method in the embodiment of the application.
  • FIG. 10-FIG. 15 are schematic diagrams of several structures of a communication device in an embodiment of the present application.
  • the terminal device in this embodiment of the present application may be a user equipment (user equipment, UE), an access terminal, a UE unit, a UE station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a UE terminal, a terminal, a wireless Communication equipment, multimedia equipment, streaming media equipment, UE proxy or UE device, etc.
  • UE user equipment
  • the access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (SIP) telephone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in future 5G networks or terminals in future evolved public land mobile network (PLMN) networks Wait.
  • the terminal device 101 may also be stationary or mobile.
  • the access network device in this embodiment of the present application is a device that communicates with a terminal device, and may be a base station, a relay station, or an access point.
  • a base station can be a base transceiver station (BTS) in a global system for mobile communication (GSM) or a code division multiple access (CDMA) network, or a broadband code division A node base station (NB) in wideband code division multiple access (WCDMA), an evolutional NB (eNB or eNodeB) in LTE, or a cloud radio access network (cloud radio access network)
  • the wireless controller in the radio access network, CRAN) scenario can also be the base station equipment in the 5G network, such as: next generation node B (gNB), and the access network equipment can also be the future evolved PLMN network
  • the access network device in the device can also be a wearable device or a vehicle-mounted device.
  • the core network devices in the embodiments of the present application correspond to different devices in different systems.
  • a GPRS service support node serving GPRS support node, SGSN
  • a GPRS gateway support node gatewayway GPRS support Node, GGSN
  • MME mobility management entity
  • S-GW serving gateway
  • 5G it can correspond to access and mobility management function (AMF), session management function (SMF) or user plane management Function (user plane function, UPF).
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane management Function
  • the terminal device sends a measurement report (measurement report) to the source base station according to the measurement configuration (measurement configuration).
  • the source base station sends handover request information (handover request) to the target base station, and the handover request information includes: target cell identity document (ID), terminal equipment ID, handover reason, context information of the terminal equipment, and capability information of the terminal equipment , parameters such as radio resource control (RRC) reconfiguration information (RRC reconfiguration) and/or RRC resume information (RRC resume) that the terminal device communicates with the source base station.
  • RRC radio resource control
  • RRC reconfiguration RRC reconfiguration
  • RRC resume RRC resume
  • the target base station After the target base station receives the handover request information, the target base station prepares the target cell resources required by the terminal device (for example, adding, deleting and/or modifying the RRC reconfiguration information for the communication between the terminal device and the source base station), after the preparation is successful, Send handover request acknowledgement to the source base station.
  • the handover request confirmation information includes: a cell-radio network temporary identifier (cell-radio network temporary identifier, C-RNTI) of the terminal device in the target cell, an RRC container (RRC container), and the like.
  • the RRC container may include RRC reconfiguration information and/or RRC recovery information for the terminal device to communicate with the target base station.
  • the source base station After the source base station receives the handover request confirmation information, the source base station sends a handover command (handover command) to the terminal device, the handover command is used to instruct the terminal device to perform handover, and the handover command includes:
  • the terminal device communicates with the RRC reconfiguration of the target base station information, target cell ID, C-RNTI of the terminal device in the target cell, etc. And transfer the data of the user panel to the target base station.
  • the terminal device After the terminal device receives the handover command, the terminal device connects to the target base station through the RRC reconfiguration information, and sends the RRC reconfiguration information completion information to the target base station, where the RRC reconfiguration information completion information is used to indicate that the handover has succeeded.
  • the full configuration is used to generate RRC configuration information, and it can also be understood that the base station can reconfigure the RRC resources used for communicating with the UE through the full configuration.
  • the RRC reconfiguration information generated during the full configuration process is different from the RRC reconfiguration information in other scenarios.
  • the RRC reconfiguration information of the target base station is obtained by adding, deleting, and/or modifying the RRC reconfiguration information of the source base station.
  • the RRC configuration information generated in the full configuration process is not information obtained by further processing on the basis of the RRC configuration information generated by the source base station, but is completely new configuration information.
  • the target base station instructs the terminal device to release/clear the current dedicated radio configurations through the source base station, and then the terminal device can communicate with the target base station according to the new configuration information.
  • Embodiments of the present application provide a communication method, apparatus, and system. By instructing the first network node to perform full configuration by the first information, the drawback caused by incomplete information transmission can be solved.
  • the present application can be applied to the protocol frameworks of various wireless communication systems.
  • the wireless communication systems may include, but are not limited to, general packet radio service (GPRS), LTE system, New Radio (NR) system, Future evolved communication systems, etc., future evolved communication systems such as future networks or sixth-generation communication systems.
  • GPRS general packet radio service
  • LTE Long Term Evolution
  • NR New Radio
  • Future evolved communication systems etc.
  • future evolved communication systems such as future networks or sixth-generation communication systems.
  • FIG. 1 is a schematic diagram of a communication system to which the embodiments of the present application are applied.
  • the communication system may include terminal equipment 101 , access network equipment 102 and core network equipment 103 .
  • terminal device 101 only one terminal device 101, one access network device 102, and one core network device 103 are used as examples for description. In practical applications, there may be more terminal devices, access network devices, and core network devices. equipment, which is not limited here.
  • Communication between the terminal device 101 and the access network device 102 is generally performed through the Uu air interface.
  • the access network device 102 and the core network device 103 generally communicate through the NG, N2 or S1 interface. If the communication system includes more access network devices, the access network devices generally communicate through Xn or X2 interfaces.
  • the access network device 102 in this embodiment of the present application may include CUs and DUs in some scenarios (eg, NR scenarios).
  • the CU and DU generally communicate through the F1 interface
  • the control plane (CP) and the user plane (UP) in the CU communicate through the E1 interface, that is, gNB-CU-CP and gNB -Communication between CU-UP through E1 interface.
  • the interaction information between the above interfaces includes but is not limited to the following signaling or messages:
  • the signaling exchanged between the access network device 102 and the core network device 103 may include: handover request information, UE context establishment, modification and other information related to UE context management, and the like.
  • the signaling exchanged between access network devices may include: handover request information, some signaling in dual-connection scenarios (such as secondary base station addition, reconfiguration, etc.), initial uplink (UL)/downlink (down link, DL) RRC message transmission, UE context management related information (eg, UE context retrieval process), etc.
  • the signaling exchanged between the CU and the DU may include: UE context establishment, modification and other related information related to UE context management, initial uplink RRC message transmission (INITIAL UL RRC MESSAGE TRANSFER), downlink/ Uplink RRC message transmission (DL/UL RRC MESSAGE TRANSFER), etc.
  • the interface between base stations (such as Xn interface), the interface between the base station and the core network (such as N2, NG) and the interface between CU-DU in the base station (such as F1) may exist Protocols that limit the size of transmission packets (for example: DTLS protocol, where the maximum transmission packet allowed by DTLS protocol is 16K), that is to say, there may be restrictions on the size of transmission packets of Xn interface, N2 interface, F1 interface, and E1 interface.
  • Protocols that limit the size of transmission packets (for example: DTLS protocol, where the maximum transmission packet allowed by DTLS protocol is 16K), that is to say, there may be restrictions on the size of transmission packets of Xn interface, N2 interface, F1 interface, and E1 interface.
  • the size of some information is allowed to be larger than the size of the protocol data unit (PDU) in the packet data convergence protocol (PDCP).
  • PDU protocol data unit
  • PDCP packet data convergence protocol
  • the uplink information that allows segmentation may include UE capability messages, and the downlink messages may include RRC reconfiguration and RRC resume.
  • RRC radio access capability segmentation
  • the UE can implement segmented transmission of the UE capability information through the RACS function.
  • the uplink information supports UE capability information in up to 16 segments
  • downlink information supports RRC reconfiguration information (RRC reconfiguration) and RRC resume information (RRC resume) in up to 5 segments.
  • RRC reconfiguration RRC reconfiguration
  • RRC resume RRC resume information
  • the maximum number of bits per segment is 9K. That is, if the air interface has the RACS function, the maximum capability information reported by the UE to the base station may be 9K ⁇ 16.
  • the information transmitted by the above interfaces includes UE capability information and/or RRC reconfiguration/RRC resume reported by the air interface, the information may not be transmitted or the transmission may be incomplete, which may result in receiving The subsequent actions on the side cannot be performed normally (for example, in the switching scenario, the switching fails).
  • the communication methods provided by the embodiments of the present application are briefly described below.
  • the communication methods provided by the embodiments of the present application can be summarized as the first solution and the second solution.
  • Solution 1 can be applied to the communication between the second network node and the first network node, and can also be applied to the communication between the third network node and the first network node.
  • the first information instructs the first network node to perform full configuration, so as to solve the communication failure caused by incomplete information transmission between the network nodes.
  • the second network node sends the first information to the first network node, and the second network node and the first network node may be access network devices.
  • the first information is used to instruct the first network node to perform the full configuration;
  • the second network node receives the first configuration information, the first configuration information is the configuration information generated by the first network node in the full configuration, and the first configuration information is used for the terminal
  • the device communicates with the first network node.
  • the third network node sends the first information to the first network node
  • the third network node may be a core network device
  • the first network node is an access network device.
  • the first information is used to instruct the first network node to perform full configuration
  • the third network node receives the first configuration information
  • the first configuration information is the configuration information generated by the first network node in the full configuration
  • the first configuration information is used for the terminal
  • the device communicates with the first network node.
  • the second network node can segment the above interfaces (NG, Xn or F1) information is transmitted to the receiving side, and the first network node assembles the information to realize complete information transmission between the second network node and the first network node.
  • the communication method provided in the embodiments of the present application can be applied between base stations and base stations, and can also be applied between base stations and core networks. In practical applications, the communication method can also be applied between other devices. For example, in CU/ Between the CU and the DU in the DU separation architecture, between the CP and the UP in the CU, etc., there is no specific limitation here.
  • the communication method provided in this embodiment of the present application is applied between base stations (for example, signaling of Xn and X2 interfaces), it can be applied to handover scenarios (for example, handover request information), and some signaling in dual-connection scenarios (for example, handover request information). For example, secondary base station addition, reconfiguration, etc.), initial UL/DLRRC message transmission, UE context management related information (eg, UE context retrieval process), etc.
  • the communication method provided by the embodiments of this application is applied between the base station and the core network (for example, signaling of NG and S1 interfaces), it can be applied to information related to UE context management, such as handover request information, UE context establishment and modification, etc. Wait.
  • the communication method provided by the embodiment of the present application is applied between the CU and the DU (for example, signaling of the F1 interface), it can be applied to the UE context establishment, modification and other related information and the UE context management.
  • the communication method provided by the embodiments of this application is applied between the CP and the UP in the CU (for example, gNB-CU-CP and gNB-CU-UP), it can be applied to UE context establishment, modification, etc. and related information of UE context management , initial uplink RRC message transmission, downlink/uplink RRC message transmission, etc.
  • the terminal device is a UE and the access network device is a base station as an example for illustrative description.
  • it can be applied to handover between base stations through the core network (as shown in Figure 2, that is, source base station-core network equipment-target base station), and can also be applied to cross-core network handover (as shown in Figure 2). 3, that is, source base station-source core network device-target core network device-target base station), which is not specifically limited here.
  • the first embodiment is a possible implementation of the above solution 1, and the first embodiment is applied to the second network node sending the first information to the first network node.
  • the first embodiment may be applied between base stations (eg, signaling of Xn and X2 interfaces).
  • FIG. 4 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • Step 401 The second network node sends first information to the first network node.
  • Step 402 the first network node performs full configuration.
  • Step 403 The first network node sends the first configuration information to the second network node.
  • the first information in the embodiment shown in FIG. 4 may be handover request information
  • the second network node may be a source base station
  • the first network node may be a target base station
  • the terminal device may be a UE
  • the first configuration information may be It is understood as RRC reconfiguration information.
  • the source base station and/or the target base station have enabled the DTLS protocol, and the DTLS protocol stipulates that the maximum number of bits of transmission information is 16K. If the number of bits of the handover request information to be sent by the source base station to the The base station cannot send complete handover request information to the target base station. If the measurement configuration information is missing, the UE cannot determine the measurement object, or the measurement event, etc., thus causing the handover failure.
  • the source base station sends the first information to the target to instruct the target to perform full configuration.
  • the first information may instruct the target base station to perform full configuration by indicating that the number of bits of the second information is greater than or equal to the first threshold, that is, the handover request information sent by the source base station to the target base station indicates to the target base station.
  • the number of bits of the second information is greater than or equal to the first threshold, and the target base station can learn it according to the handover request information. In this case, full configuration needs to be performed.
  • the second information may also be handover request information. Different from the first information, the second information is the complete handover request information that the source base station originally intended to send to the target base station.
  • the first information may be handover request information with incomplete content.
  • the second information is used by the first network node to generate second configuration information, and the second configuration information is used by the terminal device to communicate with the first network node.
  • the first information may instruct the target base station to perform full configuration by indicating that the RRC reconfiguration information in the first information is incomplete. That is to say, the handover request information sent by the source base station to the target base station indicates to the target base station that the RRC reconfiguration information in the handover request information is incomplete, and the target base station can know it according to the handover request information, and full configuration is required at this time.
  • the first information may instruct the target base station to perform full configuration by indicating that the UE capability information in the first information is incomplete. That is to say, the handover request information sent by the source base station to the target base station indicates to the target base station that the UE capability information in the handover request information is incomplete, and the target base station can know it according to the handover request information, and full configuration is required at this time.
  • the first information may instruct the target base station to perform full configuration by indicating that the transmission of the UE information in the first information is incomplete. That is to say, the handover request information sent by the source base station to the target base station indicates to the target base station that the UE information in the handover request information is not completely transmitted, and the target base station can know it according to the handover request information, and full configuration is required at this time.
  • the first information may instruct the target base station to perform full configuration by indicating that the first information is incomplete second information. That is to say, the handover request information sent by the source base station to the target base station indicates to the target base station that the handover request information is incomplete handover request information, and the target base station can know it according to the handover request information, which requires full configuration.
  • the second information may be the complete handover request information originally intended to be sent by the source base station to the target base station.
  • the first information in this embodiment of the present application may instruct the first network node to perform full configuration by way of display or indication.
  • Manner 1 Instruct the target base station to perform full configuration in an explicit manner.
  • the first information includes first indication information, where the first indication information is used to instruct the target base station to perform full configuration.
  • the first indication information may instruct the target base station to perform full configuration in the form of a first field.
  • the first field is a 1-bit field.
  • a 1-bit "1" or “0” can be used to indicate whether the target base station performs the full configuration, for example: 1 means to perform the full configuration, 0 means that the full configuration does not need to be performed. It is also possible to indicate whether the target base station performs full configuration in the manner of "true (true)” or “false (false)", for example: true means to perform full configuration, false means that full configuration is not required.
  • the first indication information is a field or information instructing the target base station to perform full configuration. When the first indication information appears, it is used to instruct the target base station to perform full configuration.
  • the above-mentioned handover request information as the first information may further include: target cell ID, terminal equipment ID, handover reason and/or UE context, and the like.
  • Mode 2 Instruct the target base station to perform full configuration in an implicit manner, that is, the first information is handover request information with incomplete content.
  • the incomplete content of the handover request information may be at least one of the following situations:
  • the handover request information may include incomplete RRC reconfiguration information, and the RRC reconfiguration information may at least not include cell group configuration information (cell group config), radio bearer configuration information (radio bearer config), One or more of the measurement configuration information (meas config).
  • the cell group configuration information in the above can be used to configure a master cell group (master cell group, MCG) or a secondary cell group (secondary cell group, SCG), and the cell group includes a MAC entity, a group of logical channels with associated RLC entities , a primary cell (spcell) and one or more secondary cells (scell).
  • Radio bearer configuration information may be used to add, modify and release signaling and/or data radio bearers.
  • the measurement configuration information is used to specify the measurements to be performed by the UE, and covers intra-frequency, inter-frequency, inter-radio access technology (RAT) mobility, and configuration of measurement gaps.
  • RAT inter-frequency access technology
  • the RRC reconfiguration information when the RRC reconfiguration information lacks the cell group configuration information, it may be that part of the information in the cell group configuration information is lacking.
  • the RRC reconfiguration information includes the cell group config, but does not include the master cell group configuration and/or the secondary cell group configuration in the cell group config.
  • Radio bearer configuration information (radio bearer config) related signaling radio bearers (signalling radio bearers, SRB) add modification list (srb-to add modification list), SRB1, data resource bearer (data radio bearer, DRB) and other related configurations Information, etc., are not limited here.
  • the handover may fail, the handover behavior cannot be realized, the service of the terminal equipment is interrupted, or the source base station will select another target base station for handover, or the RRC connection may fail, resulting in service transmission. Delay or business failure.
  • the handover request information includes incomplete UE capability information.
  • the handover request information may include UE capability information supported by the source base station (for example, one or more of a band list, a band combination list or carrier aggregation), and the rest of the UE capability information may be obtained from the UE or the core network.
  • UE capability information supported by the source base station for example, one or more of a band list, a band combination list or carrier aggregation
  • the rest of the UE capability information may be obtained from the UE or the core network.
  • the capability information included in the handover request information is a reduction of the complete UE capability information.
  • the handover request information includes a part of the carrier aggregation capability. Bandwidth combinations, etc., are not limited here.
  • the handover request information includes incomplete UE context information.
  • the UE context information may include UE capability information or RRC reconfiguration information.
  • the UE context information may be incomplete due to incomplete UE capability information, RRC reconfiguration information or other information in the UE context information.
  • reference may be made to the first situation and the second situation in the second manner.
  • the first information is handover request information with incomplete content, that is, the handover request information may include incomplete UE capabilities, incomplete RRC reconfiguration information or One or more pieces of incomplete UE context information, or one or more pieces of the above information are missing, or other information in the handover request information is incomplete, resulting in incomplete handover request information.
  • the incomplete handover request information is missing some content compared to the handover request information that the source base station originally needs to send to the target base station.
  • the incomplete handover request information can be understood as: the handover request information is obtained by subtracting the complete handover request information.
  • the complete handover request information includes RRC reconfiguration information, and the handover request information does not include RRC reconfiguration information.
  • the complete handover request information includes UE capability information, and the handover request information does not include UE capability information.
  • the complete handover request information includes UE information transmission, and the handover request information does not include UE information transmission.
  • the complete handover request information includes RRC recovery information, and the handover request information does not include RRC recovery information, etc., which is not specifically limited here.
  • the handover request information uses an implicit way to instruct the target base station to perform full configuration.
  • the above four ways are just examples, and there are other implicit ways in practical applications, which are not specifically limited here. .
  • the handover request information instructs the target base station to perform full configuration by at least one combination of the above-mentioned explicit and implicit modes, or indicates that the number of bits of the complete handover request information is greater than or equal to the first threshold.
  • the handover request information includes the first indication information and the RRC reconfiguration information, but the RRC reconfiguration information does not include the cell group configuration information.
  • the target base station can determine according to the first indication information. When performing full configuration, it can also be determined through protocol provisions that the RRC reconfiguration information in the handover request information lacks cell group configuration information, and then the target base station performs full configuration.
  • the handover request information includes the first indication information and incomplete UE capability information.
  • the target base station may determine that the UE capability information in the handover request information is incomplete, and then the target base station performs Fully configured.
  • the handover request information includes first indication information, incomplete UE capability information, and complete RRC reconfiguration information.
  • the target base station can determine the UE capability information in the handover request information. Incomplete, and then the target base station is fully configured.
  • the manner in which the handover request information is used to instruct the target base station to perform full configuration in the embodiment of the present application may be the above-mentioned explicit manner, at least one of the implicit manners, or at least one of an explicit and implicit combination.
  • a combination manner is not specifically limited here.
  • Step 402 may be specifically as follows: the target base station performs full configuration.
  • the target base station performs full configuration, and generates first configuration information in the full configuration.
  • Step 403 is specifically as follows: the target base station sends first configuration information to the source base station, where the first configuration information may be carried in the handover request confirmation information.
  • the target base station After the target base station reconfigures the RRC resources for communicating with the UE (ie, performs full configuration), the target base station sends handover request confirmation information to the source base station, where the handover request confirmation information includes the first configuration information.
  • the first configuration information is used for communication between the target base station and the terminal device.
  • the handover request confirmation information also includes the C-RNTI of the UE in the target cell (that is, the cell served by the target base station), and/or the DRB resources, target cell ID, etc. allocated by the target base station for the UE, and the user panel The data is transferred to the target base station, etc.
  • the source base station after the source base station receives the handover request confirmation information, the source base station sends the first configuration information to the terminal device.
  • the terminal device after the terminal device receives the first configuration information, the terminal device communicates with the target base station through the first configuration information, and sends RRC reconfiguration information completion information to the target base station.
  • the condition under which the second network node sends the first information to the first network node can be judged according to the first condition or the second condition. If the first and/or conditions are satisfied, the second network node sends the first information to the first network node.
  • the source base station and/or the target base station have enabled or have a protocol that limits the size of the transmitted data packets (hereinafter referred to as a limitation protocol), such as DTLS.
  • a limitation protocol such as DTLS.
  • the limit may be the first threshold.
  • condition one may include one or more of the following:
  • the source base station determines that the number of bits of the complete handover request information to be sent to the target base station is greater than or equal to the first threshold.
  • the number of bits of information received from the air interface segment is greater than or equal to the first threshold.
  • the source base station determines that the number of bits of the UE capability information is greater than or equal to the first threshold.
  • the source base station determines that the number of bits of the RRC reconfiguration information is greater than or equal to the first threshold.
  • the source base station determines that the total number of bits of the RRC reconfiguration information and the UE capability information is greater than or equal to the first threshold.
  • the source base station determines that the total number of bits of the RRC container in the complete handover request information is greater than or equal to the first threshold.
  • the RRC container may include RRC reconfiguration information, RRC recovery information and/or UE capability information.
  • the total number of bits of UE context information is greater than or equal to the first threshold.
  • the first threshold in the above can be the maximum threshold allowed by the restriction (for example, the threshold specified by the restriction protocol), or the threshold set according to actual needs (for example, a little smaller than the maximum threshold), or it can be determined according to the network processing capability.
  • the threshold for example, the maximum processing capability of the source base station, etc., is not specifically limited here.
  • the UE capability information is received from the air interface in a segmented manner.
  • the size of the information is described by the number of bits as an example for schematic illustration, and the size of the information may also be described by the number of bytes, which is not limited here.
  • the communication method shown in FIG. 4 can be applied not only in the handover scenario, but also in scenarios such as dual connection, which is not specifically limited here.
  • the first information may be some signaling in a dual-connection scenario (for example, secondary base station addition, reconfiguration, etc.), and the first information may also be related information of UE context management (for example, the process of retrieving UE context).
  • the first information may be incomplete UE context management information
  • the second information may be complete UE context management information
  • the first configuration information may be RRC reconfiguration information
  • the target base station is instructed to perform full configuration through the handover request information, and further, the source base station may instruct the target base station to perform full configuration in an implicit and/or explicit manner.
  • the handover failure caused by incomplete transmission of the complete handover request information can be avoided.
  • the difference between the second embodiment and the first embodiment is that the first embodiment is interaction between two base stations, and in the second embodiment, the base stations communicate with each other through core network equipment.
  • the second embodiment applies to the third network node sending the first information to the first network node.
  • the second embodiment may be applied between the core network device and the base station (for example: signaling of NG, S1 interface).
  • FIG. 5 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • the second network node sends third information to the third network node.
  • Step 502 The third network node sends the first information to the first network node.
  • Step 503 The first network node performs full configuration.
  • the first network node sends the first configuration information to the third network node.
  • step 505 the third network node sends the second configuration information to the second network node.
  • the first network node may be the target base station shown in FIG. 2
  • the second network node may be the source base station shown in FIG. 2
  • the third network node may be the core shown in FIG. 2. network equipment.
  • the number of the third network nodes may be two, for example, the third network nodes may include the source core network device and the target core network device shown in FIG. 3 .
  • the second network node sends third information to the third network node.
  • the second network device node sends third information to the third network node, where the third information includes information used to instruct the first network node to perform full configuration, and the third network node generates the first information according to the third information.
  • the third information may include second indication information, where the second indication information is used to instruct the first network node to perform full configuration.
  • the second indication information is sent by the source base station to the core network equipment, and the core network equipment sends the first indication information to the target base station.
  • the functions of the first indication information and the second indication information are the same.
  • the functions of the second indication information please refer to The first indication information in the first embodiment. It can be understood that since the second indication information and the first indication information are sent between different network devices, the second indication information and the first indication information may be different fields.
  • the third information is handover required information (handover required), that is, the third information is used by the first network node to prepare resources related to handover.
  • step 502 the third network node sends the first information to the first network node.
  • the third network node After the third network node receives the third information, the third network node generates the first information according to the third information.
  • the first information is handover request information (handover request).
  • handover request information handover request
  • the first embodiment reference may be made to the first embodiment.
  • Step 502 in this embodiment is similar to step 401 in the aforementioned embodiment shown in FIG. 4 , and details are not described herein again.
  • step 503 the first network node performs a full configuration.
  • Step 503 in this embodiment is similar to step 402 in the aforementioned embodiment shown in FIG. 4 , and details are not repeated here.
  • the first network node generates first configuration information during the full configuration process, where the first configuration information is used for the terminal device to communicate with the first network node.
  • step 504 the first network node sends the first configuration information to the third network node. This step is optional.
  • the first network node After the first network node generates the first configuration information in the full configuration, the first network node sends the first configuration information to the third network node.
  • the first network node sends handover request acknowledgement information (handover request acknowledgement) to the third network node, where the handover request acknowledgement information includes the first configuration information.
  • handover request acknowledgement includes the first configuration information.
  • the fourth information further includes third indication information, where the third indication information is used to indicate that the first network node has performed full configuration.
  • the fourth information is handover request acknowledgement information (handover request acknowledgement), that is, the fourth information is used to indicate that the first network node has reserved resources, and the resources are used for the terminal device and the first network node. to communicate.
  • handover request acknowledgement handover request acknowledgement information
  • step 505 the third network node sends the second configuration information to the second network node. This step is optional.
  • the above-mentioned first configuration information and second configuration information include the same RRC reconfiguration information.
  • this embodiment may include step 502 and step 503 (for example: core network-target base station).
  • this embodiment may include step 501, step 502, step 503, step 504, and step 505 (for example: source base station-core network-target base station).
  • the target base station is instructed to perform full configuration through the handover request information, and further, the target base station may be instructed to perform full configuration in an implicit and/or explicit manner.
  • the handover failure caused by incomplete transmission of the complete handover request information can be avoided.
  • the third embodiment is an optional implementation manner of the second solution of the embodiment of the present application.
  • the difference from the first two examples is:
  • the first embodiment and the second embodiment use the first information to instruct the first network node to perform full configuration, which can solve the drawback caused by incomplete information transmission.
  • the second network node when a preset condition is met, sends the first information to the first network node by means of segments, and the first network node assembles multiple segments to realize the connection between the second network node and the first network node.
  • the transmission of complete information between nodes in a network when a preset condition is met, the second network node sends the first information to the first network node by means of segments, and the first network node assembles multiple segments to realize the connection between the second network node and the first network node.
  • the second network node may send multiple segments of the first information to the first network node, and the first network node receives and assembles the multiple segments to obtain the complete first information, thereby realizing the second network node Complete data is transmitted with the first network node, so that subsequent actions can be carried out smoothly.
  • FIG. 6 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • Step 601 If a preset condition is met, the second network node sends a plurality of segments of the first information to the first network node.
  • Step 602 the first network node assembles multiple segments.
  • the second network node may be the aforementioned second access network device shown in FIG. 2
  • the first network node may be the aforementioned first access network device shown in FIG. 2
  • the second network node may be the aforementioned second access network device shown in FIG. 3
  • the first network node may be the aforementioned second core network device shown in FIG. 3
  • the second network node may be the aforementioned second core network device shown in FIG. 3
  • the first network node may be the aforementioned first core network device shown in FIG. 3
  • the second network node may be the first core network device shown in FIG.
  • the first network node may be the first access network device shown in FIG. 3 .
  • the second network node may be a CU in the access network device, and the first network node may be a DU in the access network device.
  • the second network node may be the CP in the CU (gNB-CU-CP), and the first network node may be the UP (gNB-CU-UP) in the CU.
  • gNB-CU-CP CP in the CU
  • UP gNB-CU-UP
  • the first information may be in the handover scenario (for example, handover request information).
  • the handover scenario for example, handover request information.
  • Some signaling in dual connectivity scenarios such as secondary base station addition, reconfiguration, etc.
  • initial UL/DLRRC message transmission such as initial UL/DLRRC message transmission
  • UE context management related information such as UE context retrieval process
  • the first information may be handover request information, UE context establishment , modification and other information related to UE context management.
  • the first information may be UE context establishment, modification, etc. and UE context management related information, etc.
  • the first information may be UE context establishment , modification, etc. related information related to UE context management, initial uplink RRC message transmission, downlink/uplink RRC message transmission, etc.
  • a handover scenario is used as an example for description.
  • the first network node may be the target base station
  • the second network node may be the source base station
  • the first network node may be a core network device
  • the second network node may be a core network device.
  • the network node is the source base station.
  • step 601 if a preset condition is satisfied, the second network node sends a plurality of segments of the first information to the first network node.
  • the preset conditions include condition one and/or condition two.
  • the source base station and/or the target base station have enabled or have a protocol that limits the size of the transmitted data packets (hereinafter referred to as a limitation protocol), such as DTLS.
  • a limitation protocol such as DTLS.
  • the limit may be the first threshold.
  • condition one may include one or more of the following:
  • the source base station determines that the number of bits of the complete handover request information to be sent to the target base station is greater than or equal to the first threshold.
  • the number of bits of information received from the air interface segment is greater than or equal to the first threshold.
  • the source base station determines that the number of bits of the UE capability information is greater than or equal to the first threshold.
  • the source base station determines that the number of bits of the RRC reconfiguration information is greater than or equal to the first threshold.
  • the source base station determines that the total number of bits of the RRC reconfiguration information and the UE capability information is greater than or equal to the first threshold.
  • the source base station determines that the total number of bits of the RRC container in the complete handover request information is greater than or equal to the first threshold.
  • the RRC container may include RRC reconfiguration information, RRC recovery information and/or UE capability information.
  • the total number of bits of UE context information is greater than or equal to the first threshold.
  • the first threshold in the above can be the maximum threshold allowed by the restriction (for example, the threshold specified by the restriction protocol), or the threshold set according to actual needs (for example, a little smaller than the maximum threshold), or it can be determined according to the network processing capability.
  • the threshold for example, the maximum processing capability of the source base station, etc., is not specifically limited here.
  • the UE capability information is received from the air interface in a segmented manner.
  • the size of the information is described by the number of bits as an example for schematic illustration, and the size of the information may also be described by the number of bytes, which is not limited here.
  • the first information includes an RRC container
  • the information carried in the RRC container includes RRC reconfiguration information and/or capability information of the terminal device.
  • the number of the multiple segments of the first information may be two or more, which is not specifically limited here.
  • the second network node encodes multiple segments of the first information, where the encoding rule may be an abstract syntax notation (ASN.1), etc., which is not specifically limited here.
  • ASN.1 abstract syntax notation
  • the plurality of segments includes a second segment, and the second segment is the first segment of the first information.
  • the first segment means that the number of the second segment is the first (for example: if the segment is numbered from 0, the number of the first segment is 0; if the segment starts from 1 number, the number of the first segment is 1), that is, the second segment may be a segment first sent by the second network node to the first network node (that is, the second segment may be the first segment in time) segment), or it may not be the first segment sent (that is, the second segment may not be the first segment in time).
  • the first segment of the plurality of segments may include at least one of the following:
  • a first value where the first value is used to indicate how many segments the first information is divided into (for example, it can be used to indicate the number of segments that the first network node needs to receive the first information).
  • the first value is calculated by the following method:
  • the first value is not an integer, it may be rounded up.
  • the first threshold is 16K
  • the maximum threshold specified by the DTLS protocol and the total number of bits of the first information is 50K, that is, the first value is 3.15, which is not an integer. It can be rounded up, that is, the first value is 4, that is, the second network node sends 4 segments to the first network node.
  • a second field is used to indicate that the first information is segmented information.
  • the third field is used to indicate that the segment is a segment of the first information.
  • the third field may be specifically used to indicate that the segment is a segment of the handover request information.
  • the fourth field is used to indicate that the segment is the first segment of the first information.
  • UE capability information is used to indicate that the segment is the first segment of the first information.
  • the capability information included in the first information is a reduction of the complete UE capability information, for example: the first information includes a part of the carrier aggregation capability, and the part of the carrier aggregation capability can support the UE capability with fewer carriers or support the capability of the UE with a smaller bandwidth. Bandwidth combinations, etc., are not limited here.
  • the second network node may group multiple bandwidth combinations in the UE capability information into the same segment.
  • the UE capability information may include a subset of the feature set, and the feature set includes specific capability information of a bandwidth (band) combination (for example, the band combination needs to refer to the specific capability information in the feature set).
  • bandwidth bandwidth
  • the second network node receives multiple segments of the UE capability information sent by the terminal device from the air interface, and the multiple segments of the UE capability information may include a second numerical value, and the second numerical value is used to indicate the second network node.
  • the number of segments that need to be received or an indication of the number of segments that the second network node also needs to receive.
  • the second network node transmits the UE capability information with the first network node, and the second network node receives the second value. That is, it can be known how many pieces of first information the second network node needs to send to the first network node to complete the transmission of the entire information.
  • the second numerical value is the same in number as the first numerical value.
  • the primary cell in the RRC reconfiguration information may be in the same segment, the secondary cell may be in the same segment, and the serving cell may be in the same segment.
  • RRC reconfiguration information RRC recovery information and/or capability information of the terminal device, etc.
  • the first segment of the plurality of segments may include other information in addition to at least one of the above.
  • the first segment may further include target cell ID, UE context information, etc., which is not specifically limited here.
  • the last segment of the plurality of segments may include at least one of the following:
  • the second field is used to indicate that the first information is segmented information
  • a third field used to indicate that the segment is a segment of the first information
  • the fourth field is used to indicate that the segment is the last segment
  • the segments are numbered from 0, the number of the first segment is 0, the number of the second segment is 1, and so on. If the segments are numbered from 1, the first segment is numbered 1, the second segment is numbered 2, and so on.
  • the ninth indication information may implicitly indicate that the segment is segment information, or implicitly indicate that the segment is a segment of the first information.
  • the last segment includes UE capability information
  • the primary cell, secondary cell and serving cell in the RRC reconfiguration information may be in the same segment.
  • RRC reconfiguration information RRC recovery information and/or capability information of the terminal device, etc.
  • the last segment of the plurality of segments may also include other information (eg, the first value).
  • the last segment may further include target cell ID, UE context information, etc., which is not specifically limited here.
  • other segments may use at least one of the foregoing information.
  • one segment of the first information is carried by one fourth information, that is, step 601 can be understood as: if the preset condition is satisfied, the second network node sends a plurality of fourth information to the first network node, one fourth information The information is used to carry one segment of the first information.
  • the related UE capability information may be divided into the same segment.
  • multiple bandwidth combinations in the UE capability information are grouped into the same segment.
  • the related RRC reconfiguration information may be segmented into the same segment.
  • the primary cell, the secondary cell, and the serving cell may be equally divided into the same segment.
  • step 602 the first network node assembles the plurality of segments.
  • the first network node may assemble the multiple segments to obtain the first information.
  • the first network node may receive and assemble simultaneously.
  • the first network node may partially assemble the received continuous segments according to the ninth indication information.
  • the first network node receives segments numbered 1, 2, 3, and 7, and the first network node may assemble segments 1, 2, and 3 first. While being assembled, the remaining segments are received. The efficiency of assembling the plurality of segments by the first network node can be improved.
  • the first network node assembles all segments after receiving them.
  • the first network node determines whether the received multiple segments are complete according to the first value and/or the third indication information. Exemplarily, if the first value is 6, the first network node may determine that the first information includes 6 segments, and determine, according to the third indication information, the number of segments that have received 6 pieces of the first information, then the first network node The node may determine that the 6 segments of the first information have been completely received, and assemble the 6 segments to obtain the first information.
  • the capability information included in the first information is a reduction of the complete UE capability information, for example: the first information includes a part of the carrier aggregation capability, and the part of the carrier aggregation capability can support the UE capability with fewer carriers or support a smaller bandwidth. or multiple bandwidth combinations in the UE capability information are divided into the same segment, etc., which are not limited here.
  • the first network node first obtains a part of the UE capability information, and then reconfigures the user terminal according to the obtained part of the UE capability (for example, modifying the transmission link parameters between the terminal device and the source base station to parameters of the transmission link between the terminal equipment and the target base station so that the user terminal can perform data transmission). Further, in the process of reconfiguring the user terminal by the first network node, the remaining UE capability information may be continuously received, thereby reducing the processing delay of the second network node.
  • the related RRC reconfiguration information is divided into the same segment.
  • the primary cell, the secondary cell and the serving cell are equally divided into the same segment.
  • the SRB addition modification list, SRB1 and DRB are divided into the same segment. Then, before the first network node receives all the segments, the configuration information of the cell group can be prepared first, so as to improve the processing efficiency of the first network node.
  • the first network node is a core network device.
  • the plurality of segments include at least one first segment, where the first segment is information in the RRC container. Since the core network device does not need to parse the RRC container, the processing delay caused by parsing the first segment is reduced.
  • the second network node may send multiple segments of the first information to the first network node, and the first network node receives and assembles the multiple segments to obtain the complete first information, The transmission of complete data between the second network node and the first network node is realized, and subsequent actions are carried out smoothly.
  • the fourth embodiment is an optional implementation of the second embodiment of the present application, and the fourth embodiment is a modification of the third embodiment. Sections are further limited. That is, the first segment includes the information in the RRC container, the second segment includes all information (such as cell, IE, etc.) except the Uu interface information, and the second segment is the segment numbered the first, and then After receiving the second segment, the first network node can configure related resources (for example, handover preparation in a handover scenario, reserved resources, etc.), thereby reducing network delay and improving processing efficiency.
  • related resources for example, handover preparation in a handover scenario, reserved resources, etc.
  • FIG. 7 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • a handover scenario is used as an example for description.
  • the first network node may be the target base station
  • the second network node may be the source base station
  • the first network node may be a core network device
  • the second network node may be a core network device.
  • the network node is the source base station.
  • Step 701 If a preset condition is satisfied, the second network node sends multiple segments of the first information to the first network node.
  • Step 702 The first network node assembles multiple segments.
  • Steps 701 and 702 in this embodiment are similar to steps 601 and 602 in the aforementioned embodiment shown in FIG. 6 .
  • the embodiment shown in FIG. 7 is a further description of the embodiment shown in FIG. 6 shows the embodiment.
  • step 701 if a preset condition is satisfied, the second network node sends a plurality of segments of the first information to the first network node.
  • the second network node sends a plurality of segments of the first information to the first network node.
  • the preset conditions are similar to those in the embodiment shown in FIG. 6 , and details are not described herein again.
  • the plurality of segments of the first information include at least one first segment and one second segment.
  • the first segment includes information in the RRC container (RRC reconfiguration information, RRC recovery information, and/or capability information of the terminal device, etc.). Further, the first segment only includes the information in the RRC container, that is, the second segment includes all the information (eg, cell, IE, etc.) in the first information except the Uu interface information.
  • the RRC container information may be understood as Uu port information, and the Uu port is an air interface for communication between the terminal device and the access network device.
  • the second segment may also include the information in the RRC container and all the information in the first information except the Uu interface information.
  • the second segment includes a fourth field, and the fourth field is used to indicate that the second segment is the first segment of the first information.
  • the first network node may determine that the received information is the first segment of the first information. The first network node may first configure the resources required by the terminal device according to the information in the first segment. The first network node may continue to receive other segments of the first information while configuring resources.
  • the first network node may prepare resources for handover. That is, preparations for handover can be made before all segments are received. Thereby, network delay is reduced, processing time is reduced, processing efficiency is improved, and/or service quality is improved.
  • the first network node may add preparation resources for the secondary base station. It is not necessary to receive all the segments, and the secondary base station is added after assembly/analysis, thereby reducing network delay, reducing processing time, improving processing efficiency, and/or improving service quality.
  • the first network node may first use the part of the RRC reconfiguration information to perform RRC for the user terminal.
  • the delta configuration of the reconfiguration information that is, operations such as addition, deletion or modification based on the RRC reconfiguration information.
  • the remaining RRC reconfiguration information may be continuously received, thereby reducing the processing delay of the first network node.
  • the second network node when the second network node splits the RRC container in the first information, exemplarily, the second network node may divide multiple bandwidth combinations in the UE capability information into the same segment, or divide the RRC container into the same segment.
  • the primary cell, secondary cell and serving cell in the reconfiguration information are in the same segment. Further, the integrity of the information contained in each segment of the first information is guaranteed.
  • step 702 the first network node assembles the plurality of segments.
  • Step 702 in this embodiment is similar to step 602 in the aforementioned embodiment shown in FIG. 6 , and further features are described below.
  • the first network node is a core network device.
  • the core network device After receiving the multiple segments of the first information, the core network device assembles and processes the multiple segments of the first information and generates the second information. It can be understood that the second information The function is the same as that of the first information, except that the second information is the information after being assembled and processed by the core network.
  • the core network device receives multiple segments of the first information sent by the source base station, and the number of segments of the first information is the first value, then the core network device can send the multiple segments of the second information to the target base station, The number of segments of the second information is the same as the number of segments of the first information. That is, the core network device sends the number of segments of the second information to the target base station as many segments of the first information are received.
  • the second segment is not necessarily the first segment received by the first network node, but the second segment is not the last segment received by the first network node. That is, when the first network node receives the second segment, it has not received all the first segments.
  • the second segment includes all information (such as cell, IE, etc.) except the Uu interface information, and the second segment is the segment numbered the first, and the first network node receives the second segment.
  • related resources can be configured (for example, handover preparations in handover scenarios, reserved resources, etc.), thereby reducing network delay, reducing processing time, improving processing efficiency, and improving service quality.
  • a fifth embodiment of the present application provides a communication method for providing access network equipment with area information for performing multicast/multicast services, so as to realize effective delivery of multicast/multicast services to terminal equipment that needs to receive the service transmission.
  • a multicast/multicast service is a service sent to terminal devices interested in the service.
  • a terminal device interested in a multicast/multicast service needs to be registered with a multicast/multicast server, and the registration content may include the multicast/multicast service that the terminal device is interested in, and the The cell identification information for device access/residence.
  • the multicast/multicast server may determine the transmission area of the multicast/multicast service according to the cell identification information of the terminal device, and deliver the cell list to the core network.
  • the core network establishes a multicast/multicast session with the corresponding multicast control entity and base station according to the cell list, and transmits multicast/multicast service data through the multicast/multicast session.
  • the terminal equipment When the terminal equipment changes cells, it needs to report its new cell identification information to the multicast/multicast server, so that the multicast/multicast server updates the cell list, and the updated cell list will be delivered to the core network, multicast control entity, and network equipment will establish/release multicast/multicast sessions according to the updated cell list.
  • the current technology cannot solve the transmission problem of some multicast/multicast services that do not need to be registered with the multicast/multicast server.
  • the multicast/multicast service that does not need to be registered with the multicast/multicast server (hereinafter referred to as the first multicast/multicast service).
  • the server registration does not grasp the location information of the terminal equipment interested in the first multicast/multicast service.
  • a terminal device (hereinafter referred to as a first terminal device) that is interested in the first multicast/multicast service and/or is receiving the first multicast/multicast service.
  • the first terminal device needs to register relevant information with the core network, such as the identification information of the terminal device (such as UE ID), the multicast/multicast service that the terminal device is interested in, and the like.
  • the core network When the first terminal device is in the RRC idle state/inactive state, the core network only grasps the tracking area list (TA lists) of the first terminal device.
  • the tracking area list generally includes multiple cells, and may also be multiple cells belonging to multiple base stations, as shown in FIG. 8 , which is a schematic diagram of the tracking area list.
  • the first terminal device is located in a certain cell in the tracking area list. Only when the first terminal device moves out of a cell described in a certain tracking area list, will it report its new tracking area list to the core network. That is to say, the core network does not grasp the specific location information of the first terminal equipment that needs to receive the first multicast/multicast (such as the cell to which the first terminal equipment accesses/resides), but only grasps the information of the first terminal equipment.
  • a list of tracking areas ie the set of cells where the first terminal device may exist. Therefore, at this time, the core network cannot determine which cell the first terminal device is located in. If the core network and the access network to which each cell in the tracking area list belongs to establish a multicast/multicast session resource serving the cell, it will cause a lot of waste of resources and invalid transmission. Therefore, in this case, the core network cannot effectively establish session resources for transmitting the first multicast/multicast service with the access network device to which the cell where the first terminal device resides belongs. At this time, effective/efficient transmission of the first multicast/multicast service cannot be performed.
  • the access network device can receive the area information of the first multicast/multicast service from the core network, and the access network device can send the multicast data in the area corresponding to the area information.
  • broadcast/multicast service notification After receiving the multicast/multicast service notification, the first terminal device interested in the first multicast/multicast service may enter the RRC connected state. Then, the access network device can determine the location information of the first terminal device and report it to the core network.
  • the core network may establish a session resource for transmitting the first multicast/multicast service with the serving cell/base station of the first terminal device according to the location information of the first terminal device, and perform data transmission of the first multicast/multicast service .
  • This solution can ensure the effective transmission of multicast/multicast service data to all terminal devices interested in multicast/multicast services, while avoiding invalid transmission of network devices to areas where there are no terminal devices interested in the service.
  • This solution can improve the reliability and accuracy of multicast/multicast service notification, improve service quality, improve multicast/multicast service transmission efficiency, and save communication resources.
  • FIG. 9 shows a schematic diagram of the transmission of multicast/multicast industry area information and the notification process of the multicast/multicast industry.
  • the access network device receives the first area information of the first multicast/multicast service from the core network.
  • the first area information of the multicast/multicast service is used to indicate the area that needs to be notified of the multicast/multicast service, or it is possible that the first multicast/multicast service is being received, and/or the multicast/group service may be received.
  • the first area information may include any one or more of the following: cell list (cell list), tracking area list (TA list), base station list, multicast/multicast (transmission) area information/list, etc., here No restrictions.
  • the access network device receives the multicast before the first multicast/multicast service starts to transmit, or before the first multicast/multicast session for data transmission of the first multicast/multicast service is established. /First area information of multicast service.
  • the access network device receives the area information of the multicast/multicast service from the core network device.
  • the terminal equipment of the multicast/multicast service is registered in the core network or joins the multicast/multicast service group (hereinafter, registration is used instead of registration or joins the multicast/multicast service group)
  • the terminal The registration content of the device may include any of the following: the identification information of the terminal device (such as UE ID, etc.), the tracking area list (TA list) of the terminal device, the access/resident information of the terminal device.
  • Cell identification information (such as cell list, PID), the cell list information that meets the camping conditions obtained by the terminal device through measurement, and the identification information of the multicast/multicast service that the terminal device is interested in (for example, the multi- The mobile user identification group radio network temporary identifier corresponding to the broadcast/multicast service, G-RNTI; the temporary mobile group identification temporary mobile group identity, TMGI, etc.).
  • the core network device receives the above information from a multicast/multicast service server or other network elements.
  • the core network device determines, according to the content registered/reported by the terminal device, the multicast/multicast service that the terminal device is interested in, and the location information of the terminal device, thereby: Determine the area information that requires multicast/multicast service transmission.
  • the core network device determines, according to the content registered/reported by the terminal device, the terminal device information that is interested in a certain (some) multicast/multicast service and/or is receiving the service, including all The location information of the terminal equipment is used to determine the area information that needs to perform multicast/multicast service transmission.
  • the access network device sends multicast/multicast service notification information in the area indicated by the first area information.
  • the multicast/multicast service notification information is used to notify the terminal equipment that the multicast/multicast service is about to start, or to notify the terminal equipment to prepare for receiving the multicast/multicast service, or to notify the terminal equipment to establish an RRC connection/ Enter the RRC connected state to receive the multicast/multicast service, or inform the terminal device whether it needs to establish an RRC connection/enter the RRC connected state to receive the multicast/multicast service, or notify the terminal device to request the multicast/multicast service.
  • Configuration/control information or in other words, notify the terminal device to request control/configuration information of the multicast/multicast service through broadcast information (such as system broadcast system information, information sent by the multicast control channel MCCH).
  • the multicast/multicast service is the multicast/multicast service corresponding to the multicast/multicast service notification information, and the multicast/multicast service may be one or more multicast/multicast services.
  • the access network device sends the multicast/multicast service notification information area information in the area indicated by the first area information according to the first area information. For example, the access network device determines that the multicast needs to be sent according to the cell list (cell list), tracking area list (TA list), base station list, and multicast/multicast (transmission) area information/list included in the first area information.
  • the area for multicast service notification information can be a cell/base station that sends multicast/multicast service notification information.
  • the broadcast/multicast service notification information may be scrambled by using the multicast/multicast service identification information indicated by the broadcast/multicast service notification information, such as using the mobile user identification (group identity) corresponding to the multicast/multicast service.
  • radio network temporary identifier, G-RNTI for scrambling, or scrambling with identification information used to notify the multicast/multicast service changes (that is, different multicast/multicast services may have different changes identification information), or use pre-defined identification information for notifying multicast/multicast for scrambling, etc., which are not limited here.
  • the terminal device receives the multicast/multicast service notification information, and makes corresponding preparations for receiving the multicast/multicast service.
  • the terminal device receives the multicast/multicast service notification information from the access network device.
  • the terminal device is one or more terminal devices that are interested in the multicast/multicast service corresponding to the multicast/multicast service notification information and or are receiving the service.
  • the terminal device can establish an RRC connection/enter the RRC connection state to receive the multicast/multicast service according to the indication of the multicast/multicast service notification information, or can broadcast information (such as system broadcast system information, The information sent by the multicast control channel MCCH) requests the control/configuration information of the multicast/multicast service, etc., which is not limited here.
  • the terminal device may request control/configuration information of the multicast/multicast service through broadcast information (such as system broadcast system information, information sent by a multicast control channel MCCH).
  • broadcast information such as system broadcast system information, information sent by a multicast control channel MCCH.
  • the terminal device receives the multicast/multicast service data by using the control/configuration information of the multicast/multicast service.
  • the terminal equipment entering the RRC connection state may report the RRC connection to the access network equipment because of receiving the multicast/multicast service, and the terminal equipment may also report the multicast/group of interest to it.
  • broadcast service identification information In this case, the identification information of the multicast/multicast service that it is interested in is reported to indicate that the terminal device establishes the RRC connection because it wants to receive the multicast/multicast service.
  • the access network device sends the relevant information of the terminal device to the core network device, and the relevant information may include the RRC state of the terminal device, the identification information of the terminal device (such as UE ID), the The multicast/multicast services that the terminal device is interested in, the identification information of the cell to which the terminal device accesses, the information about the multicast/multicast area to which the terminal device belongs, the number of the terminal devices, etc., are not included here. make restrictions.
  • the access network device receives the multicast/multicast session start notification information from the core network.
  • the access network device receives multicast/multicast session start notification information from the core network.
  • the core network device determines the location information of the terminal device according to the relevant information of the terminal device reported by the access network device, and the location information may be the cell, base station/access network device described by the terminal device , multicast/multicast service area, etc.
  • the core network device sends multicast/multicast session start notification information to the access network device related to the location information.
  • the multicast/multicast session start notification information is used to indicate that the multicast/multicast session is about to start, or to instruct the access network device to establish a session for the multicast/multicast, or to instruct the access network device to establish a session for the multicast/multicast.
  • the network access device prepares session resources for the multicast/multicast, or is used to establish a connection between the core network and the access network for the multicast/multicast.
  • the access network device after receiving the multicast/multicast session start notification information, performs the actions required by the multicast/multicast session start notification letter. And after the behavior is successfully performed, the corresponding information of multicast/multicast session start is sent to the core network device.
  • the core network device After the multicast/multicast session is started/established, the core network device sends the data of the multicast/multicast service to the access network device through the multicast/multicast session. Since the start/establishment of the multicast/multicast session is only for the cell/base station where there are terminal devices interested in the multicast/multicast session, the realization of the multicast/multicast service data is only directed to the presence of the multi-cast/multicast service data.
  • the cell/base station of the terminal equipment interested in the multicast/multicast service does not need to transmit to the cell/base station where the terminal equipment interested in the multicast/multicast service does not exist. Thereby improving transmission efficiency, saving transmission resources and energy, and ensuring service quality.
  • the above scheme provides the access network equipment with the area information of the multicast/multicast service through the core network equipment, so that the access network equipment can send the multicast/group to the area where the terminal equipment interested in the multicast/multicast service may exist.
  • broadcast service notification information The terminal device prepares to receive the multicast/multicast service by receiving the multicast/multicast service notification information, such as establishing an RRC connection and requesting the configuration of the multicast/multicast service through a broadcast control channel /Control information, etc.
  • the access network equipment may report the location information of the terminal equipment (such as information about the cell where it is located) to the core network equipment, and the core network equipment determines the terminal equipment to which the terminal equipment belongs according to the location information.
  • the core network device sends the data of the multicast/multicast service to the access network device through the multicast/multicast session.
  • the access network device sends the data to terminal devices interested in the multicast/multicast service.
  • the above solution can realize effective/efficient transmission of multicast/multicast services, avoid invalid transmission of multicast/multicast services, and thus avoid waste of communication resources and energy.
  • terminal devices interested in multicast/multicast services can receive multicast/multicast services, thereby ensuring service quality.
  • the embodiments of the present application further provide corresponding apparatuses, including corresponding modules for executing the foregoing embodiments.
  • Modules can be software, hardware, or a combination of software and hardware.
  • the communication apparatus may be core network equipment or access network equipment, or may be a component of core network equipment or access network equipment (for example, a processor, a chip or system-on-a-chip), the communication device includes:
  • a transceiver unit 1001 configured to send first information to a first network node, where the first information is used to instruct the first network node to perform full configuration
  • the transceiver unit 1001 is further configured to receive first configuration information, where the first configuration information is the configuration information generated by the first network node in the full configuration, and the first configuration information is used for the terminal device to communicate with the first network node.
  • each unit in the communication device is similar to the operations performed by the second network node or the third network node in the foregoing embodiments shown in FIG. 4 to FIG. 9 , and details are not described herein again.
  • the transceiver unit 1001 sends first information to the first network node, where the first information is used to instruct the first network node to perform full configuration, and the transceiver unit 1001 receives the first configuration information, where the first configuration information is the first network node
  • the configuration information generated by the node in the full configuration, and the first configuration information is used for the terminal device to communicate with the first network node.
  • the network node can successfully perform subsequent actions.
  • the communication apparatus may be an access network device, or may be a component of the access network device (for example, a processor, a chip, or a chip system), the communication device include:
  • a transceiver unit 1101 configured to receive first information, where the first information is used to instruct the first network node to perform full configuration
  • a processing unit 1102 configured to perform a full configuration, and generate first configuration information in the full configuration, and the first configuration information is used to communicate with the terminal device;
  • the transceiver unit 1101 is further configured to send the first configuration information to the second network node.
  • each unit in the communication device is similar to the operations performed by the first network node in the foregoing embodiments shown in FIG. 4 to FIG. 9 , and details are not described herein again.
  • the transceiver unit 1101 receives the first information, where the first information is used to instruct the first network node to perform the full configuration, the processing unit 1102 performs the full configuration, and generates the first configuration information in the full configuration, and the first configuration information is The configuration information generated by the first network node in the full configuration, and the first configuration information is used for the terminal device to communicate with the first network node.
  • the transceiver unit 1101 can communicate with the terminal by sending the first configuration information to the second network node. device communication.
  • the communication apparatus may be core network equipment or access network equipment, or may be a component of core network equipment or access network equipment (for example, a processor, a chip or system-on-a-chip), the communication device includes:
  • Transceiver unit 1201 configured to send multiple segments of first information to a first network node if a preset condition is met, where the first information includes an RRC container, and the information carried in the RRC container includes RRC reconfiguration information and/or terminal equipment capacity information;
  • the preset condition is at least one of the following:
  • the number of bits of the capability information is greater than or equal to the first threshold, and the capability information comes from the terminal device;
  • the total number of bits of the RRC container is greater than or equal to the first threshold
  • the total number of bits of the first information is greater than or equal to the first threshold.
  • each unit in the communication device is similar to the operations performed by the second network node or the third network node in the foregoing embodiments shown in FIG. 4 to FIG. 9 , and details are not described herein again.
  • the transceiver unit 1201 sends the first information in segments, so as to avoid being unable to transmit the complete first information with the first network node when the first information exceeds the limit.
  • the communication apparatus may be core network equipment or access network equipment, or may be a component of core network equipment or access network equipment (for example, a processor, a chip or system-on-a-chip), the communication device includes:
  • the transceiver unit 1301 is configured to receive multiple segments of the first information, the first information includes an RRC container, the information carried in the RRC container includes RRC reconfiguration information and/or capability information of the terminal device, and the multiple segments come from the first information.
  • the first information includes an RRC container
  • the information carried in the RRC container includes RRC reconfiguration information and/or capability information of the terminal device, and the multiple segments come from the first information.
  • two network nodes are configured to receive multiple segments of the first information, the first information includes an RRC container, the information carried in the RRC container includes RRC reconfiguration information and/or capability information of the terminal device, and the multiple segments come from the first information.
  • each unit in the communication device is similar to the operations performed by the first network node in the foregoing embodiments shown in FIG. 4 to FIG. 9 , and details are not described herein again.
  • the transceiver unit 1301 receives multiple segments of the first information in a segmented manner, and the processing unit 1302 assembles the multiple segments to obtain the first information, so as to avoid failure to communicate with the first information when the first information exceeds the limit.
  • the second network node transmits the complete first information.
  • FIG. 14 is a schematic structural diagram of the communication device involved in the above-mentioned embodiment provided for the embodiment of the present application, wherein the communication device may specifically be the first network node in the foregoing embodiment, and the structure of the communication device may be Refer to the structure shown in FIG. 14 .
  • the communication device includes at least one processor 1411 , at least one memory 1412 , at least one transceiver 1413 , at least one network interface 1414 and one or more antennas 1415 .
  • the processor 1411, the memory 1412, the transceiver 1413 and the network interface 1414 are connected, for example, through a bus. In this embodiment of the present application, the connection may include various interfaces, transmission lines, or buses, which are not limited in this embodiment. .
  • the antenna 1415 is connected to the transceiver 1413 .
  • the network interface 1414 is used to connect the communication device with other communication devices through a communication link.
  • the network interface 1414 may include a network interface between the communication device and the core network device, such as the S1 interface, and the network interface may include the communication device and other networks.
  • a network interface between devices such as other access network devices or core network devices, such as an X2 or Xn interface.
  • the processor 1411 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process data of the software programs, for example, to support the communication device to perform the actions described in the embodiments.
  • the communication device may include a baseband processor and a central processing unit.
  • the baseband processor is mainly used to process communication protocols and communication data.
  • the central processing unit is mainly used to control the entire terminal equipment, execute software programs, and process data of software programs. .
  • the processor 1411 in FIG. 14 may integrate the functions of a baseband processor and a central processing unit. Those skilled in the art can understand that the baseband processor and the central processing unit may also be independent processors, interconnected by technologies such as a bus.
  • a terminal device may include multiple baseband processors to adapt to different network standards, a terminal device may include multiple central processors to enhance its processing capability, and various components of the terminal device may be connected through various buses.
  • the baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip.
  • the central processing unit can also be expressed as a central processing circuit or a central processing chip.
  • the function of processing the communication protocol and communication data may be built in the processor, or may be stored in the memory in the form of a software program, and the processor executes the software program to realize the baseband processing function.
  • the memory is mainly used to store software programs and data.
  • the memory 1412 may exist independently and be connected to the processor 1411 .
  • the memory 1412 can be integrated with the processor 1411, for example, in one chip.
  • the memory 1412 can store program codes for implementing the technical solutions of the embodiments of the present application, and is controlled and executed by the processor 1411 .
  • Figure 14 shows only one memory and one processor. In an actual terminal device, there may be multiple processors and multiple memories.
  • the memory may also be referred to as a storage medium or a storage device or the like.
  • the memory may be a storage element on the same chip as the processor, that is, an on-chip storage element, or an independent storage element, which is not limited in this embodiment of the present application.
  • the transceiver 1413 can be used to support the reception or transmission of radio frequency signals between the communication device and the terminal, and the transceiver 1413 can be connected to the antenna 1415 .
  • the transceiver 1413 includes a transmitter Tx and a receiver Rx.
  • one or more antennas 1415 can receive radio frequency signals
  • the receiver Rx of the transceiver 1413 is configured to receive the radio frequency signals from the antennas, convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and convert the digital
  • the baseband signal or digital intermediate frequency signal is provided to the processor 1411, so that the processor 1411 performs further processing on the digital baseband signal or digital intermediate frequency signal, such as demodulation processing and decoding processing.
  • the transmitter Tx in the transceiver 1413 is also used to receive the modulated digital baseband signal or digital intermediate frequency signal from the processor 1411, and convert the modulated digital baseband signal or digital intermediate frequency signal into a radio frequency signal, and pass a
  • the radio frequency signals are transmitted by the antenna or antennas 1415.
  • the receiver Rx can selectively perform one or more stages of down-mixing processing and analog-to-digital conversion processing on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency signal.
  • the order of precedence is adjustable.
  • the transmitter Tx can selectively perform one or more stages of up-mixing processing and digital-to-analog conversion processing on the modulated digital baseband signal or digital intermediate frequency signal to obtain a radio frequency signal, and the up-mixing processing and digital-to-analog conversion processing
  • the sequence of s is adjustable.
  • Digital baseband signals and digital intermediate frequency signals can be collectively referred to as digital signals.
  • a transceiver may also be referred to as a transceiver unit, a transceiver, a transceiver, or the like.
  • the device used to implement the receiving function in the transceiver unit may be regarded as a receiving unit
  • the device used to implement the transmitting function in the transceiver unit may be regarded as a transmitting unit, that is, the transceiver unit includes a receiving unit and a transmitting unit, and the receiving unit also It can be called a receiver, an input port, a receiving circuit, etc.
  • the sending unit can be called a transmitter, a transmitter, or a transmitting circuit, etc.
  • the communication apparatus shown in FIG. 14 can be specifically used to implement the steps implemented by the first network node in the first to fourth embodiments of the methods corresponding to FIG. 4 to FIG. 9 , and realize the technical effect corresponding to the first network node, or FIG.
  • the communication apparatus shown in 14 may also be specifically used in the steps implemented by the core network device or the access network in the fifth embodiment.
  • FIG. 15 is a possible schematic diagram of the communication apparatus 1500 involved in the above-mentioned embodiments provided by the embodiments of the present application.
  • the communication apparatus 1500 may specifically be the communication apparatus in the foregoing embodiments, and the communication apparatus 1500 may Including but not limited to the processor 1501 , the communication port 1502 , the memory 1503 , and the bus 1504 .
  • the processor 1501 is used to control and process the actions of the communication device 1500 .
  • the processor 1501 may be a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It may implement or execute the various exemplary logical blocks, modules and circuits described in connection with this disclosure.
  • the processor may also be a combination that implements computing functions, such as a combination comprising one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like.
  • the communication device shown in FIG. 15 can be specifically used to implement the functions of the steps performed by the second network node or the third network node in the first to fourth embodiments, and realize the second network node or the third network node. The technical effects corresponding to the three network nodes.
  • the communication apparatus shown in FIG. 15 may also be specifically used for the steps implemented by the core network device or the access network in the fifth embodiment.
  • Embodiments of the present application further provide a computer-readable storage medium that stores one or more computer-executable instructions.
  • the processor executes the possible implementations of the communication device in the foregoing embodiments. method, wherein the communication device may specifically be the first network node, the second network node or the third network node in the foregoing method embodiments corresponding to FIG. 4 to FIG. 9 , and FIG. 9 corresponding to the access network equipment in the method embodiments , core network equipment or terminal equipment.
  • Embodiments of the present application further provide a computer program product that stores one or more computers.
  • the processor executes the method for possible implementations of the above communication device, wherein the communication device may specifically be FIG. 4 to FIG. 9 correspond to the first network node, the second network node or the third network node in the method embodiment, and FIG. 9 corresponds to the access network device, core network device or terminal device in the method embodiment.
  • An embodiment of the present application further provides a chip system, where the chip system includes a processor, which is configured to support the communication apparatus to implement the functions involved in the possible implementation manners of the foregoing communication apparatus.
  • the chip system may further include a memory for storing necessary program instructions and data of the communication device.
  • the chip system may be composed of chips, or may include chips and other discrete devices, wherein the communication device may specifically be the first network node, the second network node, or the third network node in the method embodiments corresponding to FIG. 4 to FIG. 9 .
  • a network node, FIG. 9 corresponds to an access network device, a core network device, or a terminal device in the method embodiment.
  • the systems, devices and methods described in this application can also be implemented in other ways.
  • the apparatus embodiments described above are only illustrative.
  • the division of units is only a logical function division.
  • there may be other division methods for example, multiple units or components may be combined or integrated. to 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.
  • Units described as separate components may or may not be physically separated, and components shown 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 stand-alone 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.
  • 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 (read-only memory, ROM), random access memory (random access memory, RAM), 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

本申请实施例公开了一种通信方法,可以应用于无线通信系统,例如长期演进LTE、新无线NR系统等。本申请实施例方法可以由通信装置执行,也可以由通信装置的部件(例如处理器、芯片、或芯片系统等)执行。该方法包括:向第一网络节点发送第一信息,该第一信息用于指示第一网络节点执行全配置,接收第一配置信息,第一配置信息为第一网络节点在全配置中生成的配置信息,且该第一配置信息用于终端设备与第一网络节点通信。通过第一信息指示第一网络节点执行全配置,可以解决信息发送不完整的带来的弊端。

Description

一种通信方法、装置及系统 技术领域
本申请涉及通信领域,尤其涉及一种通信方法、装置及系统。
背景技术
数据报传输层安全(datagram transport layer security,DTLS)是流控制传输协议(stream control transmission protocol,SCTP)的安全相关的协议,由国际互联网工程任务组(internet engineering task force,IETF)定义。安全保证规范(security assurance specification,SCAS)认证要求必须支持DTLS,而DTLS有限制。目前中国信通院和三大运营商均需符合SCAS要求,其他国家运营商陆续进行认证。目前DTLS已经在长期演进(long term evolution,LTE)线网中开始应用,由运营商决定是否开启此功能。
目前,对于通信网络而言,基站之间的接口、基站与核心网之间的接口以及基站中集中单元(centralized unit,CU)和分布单元(distributed unit,DU)之间的接口均使用SCTP协议,也就是说上述接口均可能存在DTLS协议。
但是,若上述接口存在DTLS协议,则上述接口传输的信息就可能无法完整传输。
发明内容
本申请实施例提供了一种通信方法、装置及系统。通过第一信息指示第一网络节点执行全配置,可以解决信息发送不完整的带来的弊端。
本申请实施例第一方面提供了一种通信方法,该方法可以由通信装置执行,也可以由通信装置的部件(例如处理器、芯片、或芯片系统等)执行。该通信装置可以是接入网设备,也可以是核心网设备。该方法包括:向第一网络节点发送第一信息,第一信息用于指示第一网络节点执行全配置;接收第一配置信息,第一配置信息为第一网络节点在全配置中生成的配置信息,第一配置信息用于终端设备与第一网络节点通信。
本申请实施例中,向第一网络节点发送第一信息,该第一信息用于指示第一网络节点执行全配置,接收第一配置信息,第一配置信息为第一网络节点在全配置中生成的配置信息,且该第一配置信息用于终端设备与第一网络节点通信。通过第一信息指示第一网络节点执行全配置,可以解决信息发送不完整的带来的弊端。
可选地,在第一方面的一种可能的实现方式中,上述步骤中的第一信息包括第一字段,第一字段用于指示第一网络节点执行全配置。其中,第一信息包括第一字段可以理解为第一信息为第一字段,或第一信息包括第一字段。例如:第一字段为1个比特的字段,即可以用1比特的“1”或“0”指示第一网络节点是否执行全配置,例如:1为执行全配置,0为无需执行全配置。
该种可能的实现方式中,一方面,通过第一字段指示第一网络节点执行全配置,减少交互第一信息的比特数大小,从而减少传输时延。另一方面,通过显式的方式指示第一网络节点执行全配置,减少第一网络节点判断的时延。
可选地,在第一方面的一种可能的实现方式中,上述步骤中的第一信息包括RRC重配信息,RRC重配信息至少不包括小区组配置信息、无线承载配置信息、测量配置信息中的一个或多个。
该种可能的实现方式中,若第一信息不包括小区组配置信息、无线承载配置信息、测量配置信息中的一个或多个,第一网络节点也可以根据第一信息执行全配置,避免由于RRC重配信息不完整,导致的第一网络节点后续动作执行失败。
可选地,在第一方面的一种可能的实现方式中,上述步骤中的第一信息用于指示第一网络节点执行全配置包括:第一信息用于指示第二信息比特数大于或等于第一阈值,第二信息用于第一网络节点生成第二配置信息,第二配置信息用于终端设备与第一网络节点通信。
该种可能的实现方式中,通过隐式的方式指示第一网络节点执行全配置,第一网络节点接收第一信息后,可以确定第二信息比特数大于或等于第一阈值,即第一信息包括不完整的第二信息,则第一网络节点执行全配置,避免由于第一信息包括不完整的第二信息,导致的第一网络节点后续动作执行失败。
可选地,在第一方面的一种可能的实现方式中,上述步骤中的第一信息和第二信息为切换请求信息。
该种可能的实现方式中,在切换场景下,第一网络节点可以根据第一信息执行全配置,从而保证切换成功。
可选地,在第一方面的一种可能的实现方式中,执行主体是第三网络节点,上述步骤中的:向第一网络节点发送第一信息包括:第三网络节点向第一网络节点发送第一信息;上述步骤还包括:第三网络节点接收第三信息,第三信息用于指示第一网络节点执行全配置。
该种可能的实现方式中,执行主体是第三网络节点。若第三网络节点为核心网设备,在发送第一信息之前,还可以接收第三信息,并根据第三信息生成第一信息。使得该通信方法不仅可以应用于接入网设备之间,还可以应用于核心网设备与接入网设备之间。
本申请实施例第二方面提供了一种通信方法,该方法可以由通信装置执行,也可以由通信装置的部件(例如处理器、芯片、或芯片系统等)执行。该通信装置可以是接入网设备。该方法包括:接收第一信息,第一信息用于指示第一网络节点执行全配置;执行全配置,在全配置中生成第一配置信息,第一配置信息在用于与终端设备通信;向第二网络节点发送第一配置信息。其中,接收第一信息可以从第二网络节点接收,也可以是从第三网络节点接收。
本申请实施例中,接收第一信息,该第一信息用于指示第一网络节点执行全配置,执行全配置,在全配置中生成第一配置信息,第一配置信息为第一网络节点在全配置中生成的配置信息,且该第一配置信息用于终端设备与第一网络节点通信,通过向第二网络节点发送第一配置信息的方式可以实现与终端设备通信。
可选地,在第二方面的一种可能的实现方式中,上述步骤中的第一信息包括第一字段,第一字段用于指示执行全配置。
该种可能的实现方式中,一方面,通过第一字段指示第一网络节点执行全配置,减少交互第一信息的比特数大小,从而减少传输时延。另一方面,通过显式的方式指示第一网络节点执行全配置。
可选地,在第二方面的一种可能的实现方式中,上述步骤中第一信息包括RRC重配信息,RRC重配信息至少不包括小区组配置信息、无线承载配置信息、测量配置信息中的一个或多个。
该种可能的实现方式中,若第一信息不包括小区组配置信息、无线承载配置信息、测量配置信息中的一个或多个,第一网络节点也可以根据第一信息执行全配置,避免由于RRC重配信息不完整,导致的第一网络节点后续动作执行失败。
可选地,在第二方面的一种可能的实现方式中,上述步骤中的第一信息用于指示第一网络节点执行全配置包括:第一信息用于指示第二信息比特数大于或等于第一阈值,第二信息用于第一网络节点生成第二配置信息,第二配置信息用于终端设备与第一网络节点通信。
该种可能的实现方式中,通过隐式的方式指示第一网络节点执行全配置,第一网络节点接收第一信息后,可以确定第二信息比特数大于或等于第一阈值,即第一信息包括不完整的第二信息,则第一网络节点执行全配置,避免由于第一信息包括不完整的第二信息,导致的第一网络节点后续动作执行失败。
可选地,在第二方面的一种可能的实现方式中,上述步骤中的第一信息和第二信息为切换请求信息。
该种可能的实现方式中,在切换场景下,第一网络节点可以根据第一信息执行全配置,从而保证切换成功。
本申请实施例第三方面提供了一种通信方法,该方法可以由通信装置执行,也可以由通信装置的部件(例如处理器、芯片、或芯片系统等)执行。该通信装置可以是接入网设备,也可以是核心网设备。该方法包括:若满足预设条件,向第一网络节点发送第一信息的多个分段,第一信息包括RRC容器,RRC容器中承载的信息包括RRC重配信息和/或终端设备的能力信息;预设条件为以下至少一项:能力信息的比特数大于或等于第一阈值,能力信息来自于终端设备;RRC容器的比特总数大于或等于第一阈值;第一信息的比特总数大于或等于第一阈值。
本申请实施例中,若满足预设条件,第二网络节点通过分段的方式发送第一信息,避免在第一信息超过限制的情况下,无法与第一网络节点传输完整的第一信息。
可选地,在第三方面的一种可能的实现方式中,上述步骤中的向第一网络节点发送第一信息的多个分段包括:发送多个第四信息,第一信息一个分段由一个第四信息进行承载。
可选地,在第三方面的一种可能的实现方式中,上述步骤中的多个分段包括:至少一个第一分段,第一分段为RRC容器中的信息。
该种可能的实现方式中,若满足预设条件,第二网络节点通过分段的方式发送RRC容器中的信息,避免在RRC容器中的信息超过限制的情况下,无法与第一网络节点传输完整的RRC容器中的信息。
可选地,在第三方面的一种可能的实现方式中,上述步骤中的多个分段还包括:一个第二分段,第二分段是第一信息的第一条分段。其中,该第一条分段是指第二分段的编号为1,即第二分段可以是第二网络节点向第一网络节点最开始发送的一个分段(即第二分段可以是时间上的第一条分段),也可以不是最开始发送的一个分段(即第二分段可以不是时间上的第一条分段)。
该种可能的实现方式中,如果第二分段包括第一信息中除了RRC容器外的全部信息(例如信元、IE等),由于第二分段是第一信息中多个分段的第一个分段,第一网络节点在接收最后一个分段之前可以收到第二分段,即第一网络节点在接收第二分段之后,就可以提前进行后续操作,相较于接收所有分段之后在处理后续动作,降低网络的处理时延。
可选地,在第三方面的一种可能的实现方式中,上述步骤中第一信息的分段包括以下信息中的一个或多个:第一数值,用于指示分段的数量;第二字段,第二字段用于指示第一信息是被分段的信息;第三字段,用于指示分段为第一信息的一个分段;第四字段,用于指示分段的编号;能力信息;RRC容器中的信息。
该种可能的实现方式中,第一网络节点可以根据上述中的第一数值或字段(第一字段、第二字段、第三字段和/或第四字段)确定第一信息的属性(例如第一信息的分段数量等)。
本申请实施例第四方面提供了一种通信方法,该方法可以由通信装置执行,也可以由通信装置的部件(例如处理器、芯片、或芯片系统等)执行。该通信装置可以是核心网设备,也可以是接入网设备。该方法包括:接收第一信息的多个分段,第一信息包括RRC容器,RRC容器中承载的信息包括RRC重配信息和/或终端设备的能力信息,多个分段来自于第二网络节点;组装多个分段。
本申请实施例中,第一网络节点通过分段的方式接收并组装第一信息的多个分段,避免在第一信息超过限制的情况下,无法与第二网络节点传输完整的第一信息。
可选地,在第四方面的一种可能的实现方式中,上述步骤中的接收第一信息的多个分段包括:接收多个第四信息,第一信息一个的分段由一个第四信息进行承载。
可选地,在第四方面的一种可能的实现方式中,上述步骤中的多个分段包括:至少一个第一分段,第一分段为RRC容器中的信息。
该种可能的实现方式中,第一网络节点通过分段的方式发送RRC容器中的信息,避免在RRC容器中的信息超过限制的情况下,无法与第二网络节点传输完整的RRC容器中的信息。
可选地,在第四方面的一种可能的实现方式中,上述步骤中的多个分段还包括:一个第二分段,第二分段是第一信息的第一条分段。其中,该第一条分段是指第二分段的编号为1,即第二分段可以是第二网络节点向第一网络节点最开始发送的一个分段(即第二分段可以是时间上的第一条分段),也可以不是最开始发送的一个分段(即第二分段可以不是时间上的第一条分段)。
该种可能的实现方式中,如果第二分段包括第一信息中除了RRC容器外的全部信息(例如信元、IE等),由于第二分段是第一信息中多个分段的第一个分段,第一网络节点在接收最后一个分段之前可以收到第二分段,即第一网络节点在接收第二分段之后,就可以提前进行后续操作,相较于接收所有分段之后在处理后续动作,降低网络的处理时延。
可选地,在第四方面的一种可能的实现方式中,上述步骤中第一信息的分段包括以下信息中的一个或多个:第一数值,用于指示分段的数量;第二字段,第二字段用于指示第一信息是被分段的信息;第三字段,用于指示分段为第一信息的一个分段;第四字段,用于指示分段的编号;能力信息;RRC容器中的信息。本申请实施例第五方面提供一种通信装置,该通信装置可以是核心网设备或接入网设备,也可以是核心网设备或接入网设备的部件(例如处理器、芯片或芯片系统),该通信装置包括:
收发单元,用于向第一网络节点发送第一信息,第一信息用于指示第一网络节点执行全配置;
收发单元,还用于接收第一配置信息,第一配置信息为第一网络节点在全配置中生成的配置信息,第一配置信息用于终端设备与第一网络节点通信。
可选地,在第五方面的一种可能的实现方式中,上述的第一信息包括第一字段,第一字段用于指示第一网络节点执行全配置。
可选地,在第五方面的一种可能的实现方式中,上述的第一信息包括RRC重配信息,RRC重配信息至少不包括小区组配置信息、无线承载配置信息、测量配置信息中的一个或多个。
可选地,在第五方面的一种可能的实现方式中,上述的第一信息用于指示第一网络节点执行全配置包括:第一信息用于指示第二信息比特数大于或等于第一阈值,第二信息用于第一网络节点生成第二配置信息,第二配置信息用于终端设备与第一网络节点通信。
可选地,在第五方面的一种可能的实现方式中,上述的第一信息和第二信息为切换请求信息。
可选地,在第五方面的一种可能的实现方式中,上述收发单元是第三网络节点的收发单元,第三网络节点的收发单元,用于向第一网络节点发送第一信息;
第三网络节点的收发单元,还用于接收第三信息,第三信息用于指示第一网络节点执行全配置。
本申请实施例第六方面提供一种通信装置,该通信装置可以是接入网设备,也可以是接入网设备的部件(例如处理器、芯片或芯片系统),该通信装置包括:
收发单元,用于接收第一信息,第一信息用于指示第一网络节点执行全配置;
处理单元,用于执行全配置,在全配置中生成第一配置信息,第一配置信息在用于与终端设备通信;
收发单元,还用于向第二网络节点发送第一配置信息。
可选地,在第六方面的一种可能的实现方式中,上述的第一信息包括第一字段,第一字段用于指示执行全配置。
可选地,在第六方面的一种可能的实现方式中,上述的第一信息包括RRC重配信息,RRC重配信息至少不包括小区组配置信息、无线承载配置信息、测量配置信息中的一个或多个。
可选地,在第六方面的一种可能的实现方式中,上述的第一信息用于指示第一网络节点执行全配置包括:第一信息用于指示第二信息比特数大于或等于第一阈值,第二信息用于第一网络节点生成第二配置信息,第二配置信息用于终端设备与第一网络节点通信。
可选地,在第六方面的一种可能的实现方式中,上述的第一信息和第二信息为切换请求信息。
本申请实施例第七方面提供一种通信装置,该通信装置可以是核心网设备或接入网设备,也可以是核心网设备或接入网设备的部件(例如处理器、芯片或芯片系统),该通信装置包括:
收发单元,用于若满足预设条件,向第一网络节点发送第一信息的多个分段,第一信息包括RRC容器,RRC容器中承载的信息包括RRC重配信息和/或终端设备的能力信息;预设条件为以下至少一项:能力信息的比特数大于或等于第一阈值,能力信息来自于终端设备;RRC容器的比特总数大于或等于第一阈值;第一信息的比特总数大于或等于第一阈值。
可选地,在第七方面的一种可能的实现方式中,上述通信装置中的收发单元,具体用于发送多个第四信息,第一信息一个分段由一个第四信息进行承载。
可选地,在第七方面的一种可能的实现方式中,上述的多个分段包括:至少一个第一分段,第一分段为RRC容器中的信息。
可选地,在第七方面的一种可能的实现方式中,上述的多个分段还包括:一个第二分段,第二分段是第一信息的第一条分段。
可选地,在第七方面的一种可能的实现方式中,上述的第一信息的分段包括以下信息中的一个或多个:第一数值,用于指示分段的数量;第二字段,第二字段用于指示第一信息是被分段的信息;第三字段,用于指示分段为第一信息的一个分段;第四字段,用于指示分段的编号;能力信息;RRC容器中的信息。
本申请实施例第八方面提供一种通信装置,该通信装置可以是核心网设备或接入网设备,也可以是核心网设备或接入网设备的部件(例如处理器、芯片或芯片系统),该通信装置包括:
收发单元,用于接收第一信息的多个分段,第一信息包括RRC容器,RRC容器中承载的信息包括RRC重配信息和/或终端设备的能力信息,多个分段来自于第二网络节点;
处理单元,用于组装多个分段。
可选地,在第八方面的一种可能的实现方式中,上述通信装置中的收发单元,具体用于接收多个第四信息,第一信息一个的分段由一个第四信息进行承载。
可选地,在第八方面的一种可能的实现方式中,上述的多个分段包括:至少一个第一分段,第一分段为RRC容器中的信息。
可选地,在第八方面的一种可能的实现方式中,上述的多个分段还包括:一个第二分段,第二分段是第一信息的第一条分段。
可选地,在第八方面的一种可能的实现方式中,上述的第一信息的分段包括以下信息中的一个或多个:第一数值,用于指示分段的数量;第二字段,第二字段用于指示第一信息是被分段的信息;第三字段,用于指示分段为第一信息的一个分段;第四字段,用于指示分段的编号;能力信息;RRC容器中的信息。本申请实施例第九方面提供了一种通信装置,该通信装置可以是核心网设备或接入网设备,也可以是核心网设备或接入网设备的部件(例如处理器、芯片或芯片系统),该通信装置执行前述第一方面或第一方面的任意可能的实现方式中的方法,或者该通信装置执行前述第三方面或第三方面的任意可能的实现方式中的方法。
本申请实施例第十方面提供了一种通信装置,该通信装置可以是接入网设备,也可以是接入网设备的部件(例如处理器、芯片或芯片系统),该通信装置执行前述第二方面或第二方面的任意可能的实现方式中的方法,或者该通信装置执行前述第四方面或第四方面的任意可能的实现方式中的方法。
本申请实施例第十一方面提供了一种通信装置,包括:处理器,处理器与存储器耦合,存储器用于存储程序或指令,当程序或指令被处理器执行时,使得该通信装置实现上述第一方面或第一方面的任意可能的实现方式中的方法,或者该通信装置执行前述第三方面或第三方面的任意可能的实现方式中的方法。
本申请实施例第十二方面提供了一种通信装置,包括:处理器,处理器与存储器耦合,存储器用于存储程序或指令,当程序或指令被处理器执行时,使得该通信装置实现上述第二方面或第二方面的任意可能的实现方式中的方法,或者该通信装置执行前述第四方面或第四方面的任意可能的实现方式中的方法。
本申请实施例第十三方面提供了一种通信系统,包括第九方面提供的通信装置,和/或第十方面的通信装置。
本申请实施例第十四方面提供了一种通信系统,包括第十一方面提供的通信装置,和/或第十二方面的通信装置。
本申请实施例第十五方面提供了一种计算机可读存储介质,该计算机可读存储介质中存储有指令,该指令在计算机上执行时,使得计算机执行前述第一方面或第一方面的任意可能的实现方式、第二方面或第二方面的任意可能的实现方式、第三方面或第三方面的任意可能的实现方式、第四方面或第四方面的任意可能的实现方式中的方法。
本申请实施例第十六方面提供了一种计算机程序产品,该计算机程序产品在计算机上执行时,使得计算机执行前述第一方面或第一方面的任意可能的实现方式、第二方面或第二方面的任意可能的实现方式、第三方面或第三方面的任意可能的实现方式、第四方面或第四方面的任意可能的实现方式中的方法。
其中,第五、第九、第十一、第十三、第十五、第十六方面或者其中任一种可能实现方式所带来的技术效果可参见第一方面或第一方面不同可能实现方式所带来的技术效果,此处不再赘述。
其中,第六、第十、第十二、第十三、第十五、第十六方面或者其中任一种可能实现方式所带来的技术效果可参见第二方面或第二方面不同可能实现方式所带来的技术效果,此处不再赘述。
其中,第七、第九、第十一、第十四、第十五、第十六方面或者其中任一种可能实现方式所带来的技术效果可参见第三方面或第三方面不同可能实现方式所带来的技术效果,此处不再赘述。
其中,第八、第十、第十二、第十四、第十五、第十六方面或者其中任一种可能实现方式所带来的技术效果可参见第四方面或第四方面不同可能实现方式所带来的技术效果,此处不再赘述。
从以上技术方案可以看出,本申请实施例至少包括以下优点:向第一网络节点发送第一信息,该第一信息用于指示第一网络节点执行全配置,接收第一配置信息,第一配置信息为第一网络节点在全配置中生成的配置信息,且该第一配置信息用于终端设备与第一网络节点通信。通过第一信息指示第一网络节点执行全配置,可以解决信息发送不完整的带来的弊端。
附图说明
图1为本申请实施例中通信系统的示意图;
图2为本申请实施例中基站间切换的网络框架图;
图3为本申请实施例中跨核心网切换的网络框架图;
图4为本申请实施例中通信方法的一个流程示意图;
图5为本申请实施例中通信方法的另一个流程示意图;
图6为本申请实施例中通信方法的另一个流程示意图;
图7为本申请实施例中通信方法的另一个流程示意图;
图8为本申请实施例中跟踪区列表的一种示意图;
图9为本申请实施例中通信方法的另一个流程示意图;
图10-图15为本申请实施例中通信装置的几种结构示意图。
具体实施方式
为了便于理解,下面先对本申请实施例主要涉及的相关术语和概念进行介绍。
本申请实施例中的终端设备可以是用户设备(user equipment,UE)、接入终端、UE单元、UE站、移动站、移动台、远方站、远程终端、移动设备、UE终端、终端、无线通信设备、多媒体设备、流媒体设备、UE代理或UE装置等。接入终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol,SIP)电话、无线本地环路(wireless local loop,WLL)站、个人数字处理(personal digital assistant,PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、未来5G网络中的终端或者未来演进的公共陆地移动网络(public land mobile network,PLMN)网络中的终端等。终端设备101也可以是固定的或者移动的。
本申请实施例中的接入网设备是与终端设备进行通信的设备,可以是基站、中继站或接入点。基站可以是全球移动通信系统(global aystem for mobile communication,GSM)或码分多址(code division multiple access,CDMA)网络中的基站收发信台(base transceiver station,BTS),也可以是宽带码分多址(wideband code division multiple access,WCDMA)中的节点基站(nodebase station,NB),还可以是LTE中的演进型(evolutional)NB(eNB或eNodeB),还可以是云无线接入网络(cloud radio access network,CRAN)场景下的无线控制器,还可以是5G网络中的基站设备,例如:下一代节点基站(next generation node B,gNB),接入网设备还可以是未来演进的PLMN网络中的接入网设备,还可以是可穿戴设备或车载设备。
本申请实施例中的核心网设备在不同的系统对应不同的设备。比如在3G中可以对应GPRS的服务支持节点(serving GPRS support node,SGSN)和/或GPRS的网关支持节点(gateway GPRS support Node,GGSN);在4G中可以对应移动管理实体(mobility management entity,MME)和/或服务网关(serving gateway,S-GW);在5G中可以对应接入和移动管理功能(access and mobility management function,AMF)、会话管理功能(session management function,SMF)或者用户面管理功能(user plane function,UPF)。
下面以基站间切换为例对本申请所涉及的切换场景进行示意性说明,其中,切换流程包括:
终端设备按照测量配置(measurement configuration)向源基站发送测量报告(measurement report),该测量报告包括:邻小区的测量结果以及服务小区的测量结果等。
源基站向目标基站发送切换请求信息(handover request),该切换请求信息包括:目标小区身份标识号(identity document,ID)、终端设备ID、切换原因、终端设备的上下文信息、终端设备的能力信息、终端设备与源基站进行通信的无线资源控制(radio resource control,RRC)重配信息(RRC reconfiguration)和/或RRC恢复信息(RRC resume)等参数。
目标基站接收到切换请求信息之后,目标基站准备终端设备所需的目标小区资源(例如在终端设备与源基站进行通信的RRC重配信息上进行增删和/或修改等操作),准备成功后,向源基站发送切换请求确认信息(handover request acknowledge)。切换请求确认信息中包括:终端设备在目标小区中的小区无线网络临时标识(cell-radio network temporary identifier, C-RNTI)、RRC容器(RRC container)等。其中,RRC容器中可以包括终端设备与目标基站进行通信的RRC重配信息,和/或RRC恢复信息。
源基站接收到切换请求确认信息之后,源基站向终端设备发送切换命令(handover command),该切换命令用于指示终端设备执行切换,该切换命令包括:终端设备与目标基站进行通信的RRC重配信息、目标小区ID、终端设备在目标小区中的C-RNTI等。并将用户面板的数据转移到目标基站。
终端设备接收到切换命令之后,终端设备通过RRC重配信息与目标基站连接,向目标基站发送RRC重配信息完成信息,该RRC重配信息完成信息用于指示切换已经成功。
全配置(full configuration):
全配置用于生成RRC配置信息,也可以理解为基站可以通过全配置重新配置用于与UE通信的RRC资源。全配置过程中生成的RRC重配信息与其他场景中的RRC重配信息生成的方式不同。以切换场景为例,上述正常切换中,目标基站的RRC重配信息是在源基站的RRC重配信息基础上进行增删和/或修改等操作得到。而全配置过程中生成的RRC配置信息不是在源基站生成的RRC配置信息基础上进一步处理得到的信息,而是全新的配置信息。目标基站通过源基站指示终端设备释放/清空当前的专用无线电配置(dedicated radio configurations)等,然后终端设备根据全新的配置信息就可以实现与目标基站进行通信。
本申请实施例提供了一种通信方法、装置及系统。通过第一信息指示第一网络节点执行全配置,可以解决信息发送不完整的带来的弊端。
下面将结合各个附图对本申请技术方案的实现原理、具体实施方式及其对应能够达到的有益效果进行详细的阐述。
本申请可以应用于多种无线通信系统的协议框架中,无线通信系统可以包括但不限于通用分组无线服务技术(general packet radio service,GPRS)、LTE系统、新无线(New Radio,NR)系统、未来演进的通信系统等,未来演进的通信系统例如未来网络或第六代通信系统等。
图1给出了本申请实施例适用的一种通信系统示意图。该通信系统可以包括终端设备101、接入网设备102以及核心网设备103。
本申请实施例中,仅以一个终端设备101、一个接入网设备102以及一个核心网设备103为例进行说明,在实际应用中,可以有更多的终端设备、接入网设备以及核心网设备,此处不做限定。
终端设备101与接入网设备102之间一般通过Uu空中接口进行通信。接入网设备102与核心网设备103之间一般通过NG、N2或S1接口进行通信。如果通信系统包括更多的接入网设备,接入网设备之间一般通过Xn或X2接口进行通信。
本申请实施例中的接入网设备102在某些场景下(例如NR场景)可以包括CU和DU。其中,CU与DU之间一般通过F1接口进行通信,CU中的控制面板(control plane,CP)与用户面板(user plane,UP)之间通过E1接口进行通信,即gNB-CU-CP与gNB-CU-UP之间通过E1接口进行通信。
上述各个接口之间的交互信息包括但不限于以下信令或消息:
接入网设备102与核心网设备103之间交互的信令可以包括:切换请求信息、UE上下文建立、修改等与UE上下文管理相关的信息等。
接入网设备之间交互的信令可以包括:切换请求信息、双联接场景下的一些信令(例如辅基站添加、重配置等)、初始上行链路(up link,UL)/下行链路(down link,DL)RRC消息传输、UE上下文管理的相关信息(例如,检索UE上下文过程)等。
本申请实施例中CU与DU之间交互的信令可以包括:UE上下文建立、修改等与UE上下文管理的相关信息、初始上行链路RRC消息传输(INITIAL UL RRC MESSAGE TRANSFER),下行链路/上行链路RRC消息传输(DL/UL RRC MESSAGE TRANSFER)等。
对于上述的通信系统而言,基站之间的接口(如Xn接口)、基站与核心网之间的接口(如N2、NG)以及基站中CU-DU之间的接口(如F1)均可能存在限制传输数据包大小的协议(例如:DTLS协议,其中,DTLS协议允许的最大传输数据包为16K),也就是说Xn接口、N2接口以及F1接口、E1接口传输数据包的大小可能存在限制。
然而,目前冻结的R16协议中,允许一些信息的尺寸(例如比特总数或字节总数等)大于分组数据汇聚协议(packet data convergence protocol,PDCP)中协议数据单元(protocol data unit,PDU)的尺寸,并通过分段的方式在空口进行传输。目前允许分段的上行信息可以包括UE能力消息,下行消息可以包括RRC重配置和RRC resume。比如,对于UE能力信息的上报,无线能力分段(radio access capability segmentation,RACS)实现了空口的上行信息分段。在一些场景下,例如:当UE需要向基站发送UE能力(UE capability information)的场景。若UE能力信息大于PDCP所允许的最大阈值,则UE可以通过RACS功能实现UE能力信息的分段发送。R16协议中,上行信息支持UE能力信息最多分16段,下行信息支持RRC重配信息(RRC reconfiguration)和RRC恢复信息(RRC resume)最多分5段。每段最大比特数为9K。也即是,若空口存在RACS功能,则UE向基站上报的最大能力信息可以为9K×16。若上述接口(NG、Xn、F1或E1)传输的某些信息中包括空口上报的UE能力信息和/或RRC重配置/RRC resume,则可能导致信息无法传输或传输不完整,可能会导致接收侧后续的动作无法正常进行(例如切换场景下,导致切换失败)。
下面对本申请实施例提供的通信方法进行概括性的说明,本申请实施例所提供的通信方法可以概括为方案一和方案二。
对于方案一,可以应用于第二网络节点与第一网络节点之间的通信,也可以应用于第三网络节点与第一网络节点之间的通信。通过向第一网络节点发送第一信息,第一信息指示第一网络节点执行全配置,解决由于网络节点之间信息发送不完整导致的通信失败。
一种可能实现的方式中:第二网络节点向第一网络节点发送第一信息,第二网络节点和第一网络节点可以为接入网设备。该第一信息用于指示第一网络节点执行全配置;第二网络节点接收第一配置信息,第一配置信息为第一网络节点在全配置中生成的配置信息,第一配置信息用于终端设备与第一网络节点通信。通过第一信息指示第一网络节点执行全配置,可以解决第二网络节点与第一网络节点之间传输信息不完整带来的弊端。
另一种可能实现的方式中:第三网络节点向第一网络节点发送第一信息,第三网络节点可以为核心网设备,第一网络节点为接入网设备。该第一信息用于指示第一网络节点执行全配置;第三网络节点接收第一配置信息,第一配置信息为第一网络节点在全配置中生成的配置信息,第一配置信息用于终端设备与第一网络节点通信。通过第一信息指示第一网络节点执行全配置,可以解决第三网络节点与第一网络节点之间传输信息不完整带来的弊端。
对于方案二,可以应用于第二网络节点与第一网络节点之间的通信,若第二网络节点将要发送的信息超过限制,第二网络节点可以通过分段的方式将上述接口(NG、Xn或F1)的信息传输至接收侧,第一网络节点组装得到信息,实现第二网络节点与第一网络节点之间完整信息的传输。
下面对本申请提供的技术方案进行具体的介绍。
本申请实施例提供的通信方法可以应用于基站与基站之间,也可以应用于基站与核心网之间,在实际应用中,该通信方法还可以应用于其他设备之间,例如,在CU/DU分离架构中的CU与DU之间,CU中CP与UP之间等,具体此处不做限定。
本申请实施例提供的通信方法,如果应用于基站与基站之间(例如:Xn、X2接口的信令),可以应用于切换场景(例如切换请求信息),双联接场景下的一些信令(例如辅基站添加、重配置等)、初始UL/DLRRC消息传输、UE上下文管理的相关信息(例如取回UE上下文过程)等。
本申请实施例提供的通信方法,如果应用于基站与核心网之间(例如:NG、S1接口的信令),可以应用于切换请求信息、UE上下文建立、修改等与UE上下文管理相关的信息等。
本申请实施例提供的通信方法,如果应用于CU与DU之间(例如:F1接口的信令),可以应用于UE上下文建立、修改等与UE上下文管理的相关信息等。
本申请实施例提供的通信方法,如果应用于CU中CP与UP之间(例如gNB-CU-CP与gNB-CU-UP),可以应用于UE上下文建立、修改等与UE上下文管理的相关信息、初始上行链路RRC消息传输、下行链路/上行链路RRC消息传输等。
本申请实施例中,仅以终端设备是UE,接入网设备是基站为例进行示意性说明。
可选地,如果应用于切换场景,可以应用于通过核心网的基站间切换(如图2所示,即源基站-核心网设备-目标基站),还可以应用于跨核心网切换(如图3所示,即源基站-源核心网设备-目标核心网设备-目标基站),具体此处不做限定。
第一实施例:
第一实施例是上述方案一的一种可能的实现方式,第一实施例应用于第二网络节点向第一网络节点发送第一信息。可选地,第一实施例可以应用于基站与基站之间(例如:Xn、X2接口的信令)。
请参阅图4,图4为本申请实施例提供的一种通信方法的流程示意图。
步骤401、第二网络节点向第一网络节点发送第一信息。
步骤402、第一网络节点执行全配置。
步骤403、第一网络节点向第二网络节点发送第一配置信息。
下面以切换场景为例,对图4所示通信方法进行描述:
图4所示实施例中的第一信息可以为切换请求信息(handover request),第二网络节点可以为源基站,第一网络节点可以为目标基站,终端设备可以为UE,第一配置信息可以理解为RRC重配信息。
在切换场景下,源基站和/或目标基站已开启DTLS协议,而DTLS协议规定传输信息的比特数最大为16K,若源基站将要向目标基站发送的切换请求信息的比特数大于16K,则源基站无法向目标基站发送完整的切换请求信息,如果缺少了测量配置信息,UE无法确定测量对象、 或测量事件等,进而导致切换失败。
因此,在本申请第一实施例中,源基站向目标发送第一信息,以指示目标执行全配置。
可选地,第一信息可以通过指示第二信息的比特数大于或等于第一阈值的方式指示目标基站执行全配置,也就是说,源基站向目标基站发送的切换请求信息向目标基站指示了第二信息比特数大于或等于第一阈值,目标基站根据该切换请求信息就能够获知,此时需要执行全配置。在切换的场景下,第二信息也可以为切换请求信息,不同于第一信息,第二信息是源基站本来要向目标基站发送的内容完整的切换请求信息。而第一信息可以是内容不完整的切换请求信息。第二信息用于第一网络节点生成第二配置信息,第二配置信息用于终端设备与第一网络节点通信。
可选地,第一信息可以通过指示第一信息中的RRC重配信息不完整的方式指示目标基站执行全配置。也就是说,源基站向目标基站发送的切换请求信息向目标基站指示该切换请求信息中的RRC重配信息不完整,目标基站根据切换请求信息就能获知,此时需要全配置。
可选地,第一信息可以通过指示第一信息中的UE能力信息不完整的方式指示目标基站执行全配置。也就是说,源基站向目标基站发送的切换请求信息向目标基站指示该切换请求信息中的UE能力信息不完整,目标基站根据切换请求信息就能获知,此时需要全配置。
可选地,第一信息可以通过指示第一信息中的UE信息传输不完整的方式指示目标基站执行全配置。也就是说,源基站向目标基站发送的切换请求信息向目标基站指示该切换请求信息中的UE信息传输不完整,目标基站根据切换请求信息就能获知,此时需要全配置。
可选地,第一信息可以通过指示第一信息是不完整的第二信息的方式指示目标基站执行全配置。也就是说,源基站向目标基站发送的切换请求信息向目标基站指示该切换请求信息是不完整的切换请求信息,目标基站根据切换请求信息就能获知,此时需要全配置。其中,第二信息可以为源基站本来要向目标基站发送的内容完整的切换请求信息。
本申请实施例中的第一信息可以通过显示或指示的方式指示第一网络节点执行全配置。
还可以是显式方式与隐式方式中至少一种组合的方式,下面分别描述。
方式一、采用显式的方式指示目标基站执行全配置。
第一信息包括第一指示信息,该第一指示信息用于指示目标基站执行全配置。
可选地,第一指示信息可以用一个第一字段的方式指示目标基站执行全配置。
示例性的,第一字段为1比特的字段。可以用1比特的“1”或“0”指示目标基站是否执行全配置,例如:1为执行全配置,0为无需执行全配置。也可以用“真(true)”或“假(false)”的方式指示目标基站是否执行全配置,例如:true为执行全配置,false为无需执行全配置。
可选地,第一指示信息为指示目标基站执行全配置的字段或信息。当第一指示信息出现时,用于指示目标基站执行全配置。
可选地,上述作为第一信息的切换请求信息还可以包括:目标小区ID、终端设备ID、切换原因和/或UE上下文等。
方式二、采用隐式的方式指示目标基站执行全配置,也就是第一信息是内容不完整的切换请求信息。
方式二中,切换请求信息的内容不完整可以是以下多种情况中的至少一种:
方式二的第一种情况下:切换请求信息可以包括不完整的RRC重配信息,RRC重配信息可 以至少不包括小区组配置信息(cell group config)、无线承载配置信息(radio bearer config)、测量配置信息(meas config)中的一个或多个。
上述中的小区组配置信息可以用于配置主小区组(master cell group,MCG)或辅小区组(secondary cell group,SCG),小区组包括一个MAC实体、一组具有关联的RLC实体的逻辑信道、一个主小区(spcell)以及一个或多个辅助小区(scell)。无线承载配置信息可以用于添加、修改和释放信令和/或数据无线承载。测量配置信息用于指定要由UE执行的测量,并涵盖频率内、频率间、无线接入技术(radio access technology,RAT)间移动性以及测量间隙的配置。
可选的,当RRC重配信息缺少小区组配置信息时,可以是缺少小区组配置信息中的部分信息。示例性的,RRC重配信息包括cell group config,但不包括cell group config中的mastercellgroup configuration和/或secondary cell group configuration。
缺少无线承载配置信息(radio bearer config)相关的信令无线承载(signalling radio bearers,SRB)添加修改列表(srb-to add modification list),SRB1、数据资源承载(data radio bearer,DRB)等相关配置信息等,此处不做限定。
若目标基站接收的切换请求信息内容不完整,则可能导致切换失败,无法实现切换行为,终端设备的业务中断,或者源基站会选择其他目标基站进行切换,或者可能导致RRC连接失败,造成业务传输时延或业务失败。
方式二的第二种情况下:切换请求信息包括不完整的UE能力信息。
可选地,切换请求信息可以包括源基站支持的UE能力信息(例如:波段列表、波段组合列表或载波聚合中的一个或多个),其余的UE能力信息可以从UE或核心网获取。
可选地,切换请求信息包括的能力信息是完整UE能力信息的精简,例如,切换请求信息包括一部分载波聚合的能力,该部分载波聚合能力可以支持载波较少的UE能力或者支持带宽较小的带宽组合等,此处不做限定。
方式二的第三种情况下:切换请求信息包括不完整的UE上下文信息。
UE上下文信息可以包括UE能力信息或RRC重配信息,可选的,可以是由于UE能力信息、RRC重配信息或UE上下文信息中的其他信息的不完整导致UE上下文信息不完整。UE能力信息或RRC重配信息的情况可以参考方式二的第一种情况和第二种情况。
方式二的第四种情况下:作为第一信息的信息第一信息是内容不完整的切换请求信息,也就是说,切换请求信息可以包括不完整的UE能力、不完整的RRC重配信息或不完整的UE上下文信息的一个或多个,或者缺少上述信息中的一个或多个,或者是切换请求信息中的其他信息不完整,导致切换请求信息不完整。这里切换请求信息不完整是相比于源基站原本需要向目标基站发送的切换请求信息缺少了部分内容。
一种可能实现的方式中,切换请求信息不完整可以理解为:切换请求信息由完整的切换请求信息删减得到。例如:完整的切换请求信息包括RRC重配信息,切换请求信息不包括RRC重配信息。或者完整的切换请求信息包括UE能力信息,切换请求信息不包括UE能力信息。或者完整的切换请求信息包括UE信息传输,切换请求信息不包括UE信息传输。或者完整的切换请求信息包括RRC恢复信息,切换请求信息不包括RRC恢复信息等,具体此处不做限定。
本申请实施例中,切换请求信息采用隐式的方式指示目标基站执行全配置的方式有多种, 上面4种只是示例,在实际应用中还有其他的隐式方式,具体此处不做限定。
方式三、切换请求信息采用上述显式方式与隐式方式中的至少一种组合的方式指示目标基站执行全配置,或指示完整切换请求信息的比特数大于或等于第一阈值。
下面简单举例说明一下显式与隐式组合中的至少一种组合的方式:
示例性的,切换请求信息包括第一指示信息以及RRC重配信息,但是RRC重配信息不包括小区组配置信息,源基站向目标基站发送切换请求信息之后,目标基站可以根据第一指示信息确定执行全配置,也可以通过协议规定确定切换请求信息中的RRC重配信息缺少小区组配置信息,进而目标基站进行全配置。
示例性的,切换请求信息包括第一指示信息以及不完整的UE能力信息,源基站向目标基站发送切换请求信息之后,目标基站可以确定切换请求信息中的UE能力信息不完整,进而目标基站进行全配置。
示例性的,切换请求信息包括第一指示信息、不完整的UE能力信息以及完整的RRC重配信息,源基站向目标基站发送切换请求信息之后,目标基站可以确定切换请求信息中的UE能力信息不完整,进而目标基站进行全配置。
本申请实施例中切换请求信息用于指示目标基站执行全配置的方式可以是上述显式方式,也可以是隐式方式中的至少一种,还可以是显式与隐式组合中的至少一种组合的方式,具体此处不做限定。
步骤402可以具体为:目标基站执行全配置。
目标基站执行全配置,在全配置中生成第一配置信息。
步骤403具体为:目标基站向源基站发送第一配置信息,第一配置信息可以承载于切换请求确认信息。
目标基站重新配置与UE通信的RRC资源(即执行全配置)之后,目标基站向源基站发送切换请求确认信息,该切换请求确认信息中包括第一配置信息。第一配置信息用于目标基站和终端设备通信。
可选地,切换请求确认信息中还包括UE在目标小区(即目标基站服务的小区)中的C-RNTI,和/或目标基站为UE分配的DRB资源、目标小区ID等,并将用户面板的数据转移到目标基站等。
可选地,源基站接收到切换请求确认信息之后,源基站向终端设备发送第一配置信息。
可选地,终端设备接收到第一配置信息之后,终端设备通过第一配置信息与目标基站进行通信,并向目标基站发送RRC重配信息完成信息。
对于第二网络节点在什么情况下向第一网络节点发送第一信息,可以通过条件一或条件二进行判断。满足条件一和/或条件,第二网络节点向第一网络节点发送第一信息。
条件一:
在一种情况下,源基站和/或目标基站已开启或存在限制传输数据包大小的协议(以下简称限制协议),例如:DTLS。在另一种情况下,网络的处理能力存在限制。对于上述两种情况下,第二网络节点和第一网络节点之间对于传输数据包的大小存在限制,该限制可以为第一阈值。
在此情况下,条件一可以包括以下一个或多个:
源基站确定原本要向目标基站发送的完整的切换请求信息的比特数大于或等于第一阈值。
从空口分段接收的信息的比特数大于或等于第一阈值。
源基站确定UE能力信息的比特数大于或等于第一阈值。
源基站确定RRC重配信息的比特数大于或等于第一阈值。
源基站确定RRC重配信息与UE能力信息的总比特数大于或等于第一阈值。
源基站确定完整的切换请求信息中RRC容器的比特总数大于或等于第一阈值。其中,RRC容器可以包括RRC重配信息、RRC恢复信息和/或UE能力信息。
UE上下文信息的比特总数大于或等于第一阈值。
上述中的第一阈值可以是限制所允许的最大阈值(例如限制协议规定的阈值),也可以是根据实际需要设置的阈值(例如比最大阈值小一点),还可以是根据网络处理能力确定的阈值(例如:源基站的最大处理能力)等,具体此处不做限定。
条件二:
从空口通过分段的方式接收UE能力信息。
本申请实施例中,仅以信息的尺寸大小用比特数描述为例进行示意性说明,信息的尺寸大小也可以用字节数等描述,此处不做限定。
上述的几种条件只是举例,在实际应用中,还可以有其他形式的条件,具体此处不做限定。
可以理解的是,图4所示的通信方法除了可以应用于切换场景下,还可以应用于双联接等场景下,具体此处不做限定。例如:第一信息可以为双联接场景下的一些信令(例如辅基站添加、重配置等),第一信息还可以为UE上下文管理的相关信息(例如:取回UE上下文过程)等。
第一信息可以是不完整的UE上下文管理信息,第二信息是完整的UE上下文管理信息,第一配置信息可以为RRC重配信息。
本申请实施例中,通过切换请求信息指示目标基站执行全配置,进一步的,源基站可以通过隐式和/或显式的方式指示目标基站执行全配置。可以避免完整的切换请求信息发送不完整的带来的切换失败。
第二实施例:
第二实施例与第一实施例的不同点在于,第一实施例是在两个基站之间的交互,第二实施例中基站与基站之间通过核心网设备进行通信。
第二实施例应用于第三网络节点向第一网络节点发送第一信息。可选地,第二实施例可以应用于核心网设备与基站之间(例如:NG、S1接口的信令)。
请参阅图5,图5为本申请实施例提供的另一种通信方法的流程示意图。
可选的步骤501、第二网络节点向第三网络节点发送第三信息。
步骤502、第三网络节点向第一网络节点发送第一信息。
步骤503、第一网络节点执行全配置。
可选的步骤504、第一网络节点向第三网络节点发送第一配置信息。
可选的步骤505、第三网络节点向第二网络节点发送第二配置信息。
在一种可能实现的方式中,第一网络节点可以是前述图2所示的目标基站,第二网络节点可以是前述图2所示的源基站,第三网络节点可以是图2中的核心网设备。
在另一种可能实现的方式中,第三网络节点的数量可以是两个,例如,第三网络节点可以包括前述图3所示的源核心网设备以及目标核心网设备。
在可选的步骤501中,第二网络节点向第三网络节点发送第三信息。
可选地,第二网络设备节点向第三网络节点发送第三信息,第三信息包含用于指示第一网络节点执行全配置的信息,第三网络节点根据第三信息生成第一信息。
在一种可能实现的方式中,第三信息可以包括第二指示信息,第二指示信息用于指示第一网络节点执行全配置。第二指示信息是由源基站发送给核心网设备的,核心网设备向目标基站发送第一指示信息,第一指示信息和第二指示信息的功能相同,对于第二指示信息的功能等可以参见第一实施例中的第一指示信息。可以理解,由于第二指示信息和第一指示信息是不同网络设备之间发送的,因此,第二指示信息和第一指示信息可以是不同的字段。
可选地,在切换场景下,第三信息为切换要求信息(handover required),即第三信息用于第一网络节点准备切换相关的资源。
在步骤502中,第三网络节点向第一网络节点发送第一信息。
第三网络节点接收第三信息之后,第三网络节点根据第三信息生成第一信息。
可选地,在切换场景下,第一信息为切换请求信息(handover request)第一信息可以参见第一实施例。
本实施例中的步骤502与前述图4所示实施例步骤401类似,此处不再赘述。
在步骤503中,第一网络节点执行全配置。
本实施例中的步骤503与前述图4所示实施例中的步骤402类似,此处不再赘述。
第一网络节点在执行全配置过程中生成第一配置信息,该第一配置信息用于终端设备与第一网络节点进行通信。
在可选的步骤504中,第一网络节点向第三网络节点发送第一配置信息。本步骤是可选的。
第一网络节点在全配置中生成第一配置信息之后,第一网络节点向第三网络节点发送第一配置信息。
可选地,第一网络节点向第三网络节点发送切换请求确认信息(handover request acknowledge),该切换请求确认信息包括第一配置信息。
可选地,该第四信息还包括第三指示信息,该第三指示信息用于指示第一网络节点已执行全配置。
可选地,在切换场景下,第四信息为切换请求确认信息(handover request acknowledge),即第四信息用于指示第一网络节点已预留资源,该资源用于终端设备与第一网络节点进行通信。
在可选的步骤505中,第三网络节点向第二网络节点发送第二配置信息。本步骤是可选的。
可选地,上述的第一配置信息与第二配置信息包括相同的RRC重配信息。
一种可能实现的方式中,本实施例可以包括步骤502与步骤503(例如:核心网-目标基 站)。另一种可能实现的方式中,本实施例可以包括步骤501、步骤502、步骤503、步骤504以及步骤505(例如:源基站-核心网-目标基站)。
本实施例中,通过切换请求信息指示目标基站执行全配置,进一步的,可以通过隐式和/或显式的方式指示目标基站执行全配置。可以避免完整的切换请求信息发送不完整的带来的切换失败。
第三实施例:
第三实施例是本申请实施例方案二的一种可选的实现方式。与前两个实施例不同的是:
第一实施例与第二实施例是通过第一信息指示第一网络节点执行全配置,可以解决信息发送不完整的带来的弊端。
第三实施例是在满足预设条件的情况下,第二网络节点通过分段的方式向第一网络节点发送第一信息,第一网络节点组装多个分段,实现第二网络节点与第一网络节点之间完整信息的传输。
若满足预设条件,第二网络节点可以向第一网络节点发送第一信息的多个分段,第一网络节点接收并组装多个分段,得到完整的第一信息,实现第二网络节点与第一网络节点之间传输完整数据,实现后续动作顺利进行。
请参阅图6,图6为本申请实施例提供的另一种通信方法的流程示意图。
步骤601、若满足预设条件,第二网络节点向第一网络节点发送第一信息的多个分段。
步骤602、第一网络节点组装多个分段。
一种可能实现的方式中,第二网络节点可以是前述图2所示的第二接入网设备,第一网络节点可以是前述图2所示的第一接入网设备。另一种可能实现的方式中,第二网络节点可以是前述图3所示的第二接入网设备,第一网络节点可以是前述图3所示的第二核心网设备。另一种可能实现的方式中,第二网络节点可以是前述图3所示的第二核心网设备,第一网络节点可以是前述图3所示的第一核心网设备。另一种可能实现的方式中,第二网络节点可以是前述图3所示的第一核心网设备,第一网络节点可以是前述图3所示的第一接入网设备。另一种可能实现的方式中,第二网络节点可以是接入网设备中的CU,第一网络节点可以是接入网设备中的DU。另一种可能实现的方式中,第二网络节点可以CU中的CP(gNB-CU-CP),第一网络节点可以是CU中的UP(gNB-CU-UP)。具体此处不做限定。
一种可能实现的方式中,若图6所示的通信方法应用于基站与基站之间(例如:Xn、X2接口的信令),则第一信息可以为切换场景(例如切换请求信息)下的一些信令、双联接场景下的一些信令(例如辅基站添加、重配置等)、初始UL/DLRRC消息传输、UE上下文管理的相关信息(例如取回UE上下文过程)等。
另一种可能实现的方式中,若图6所示的通信方法应用于基站与核心网之间(例如:NG、S1接口的信令),则第一信息可以为切换请求信息、UE上下文建立、修改等与UE上下文管理相关的信息等。
另一种可能实现的方式中,若图6所示的通信方法应用于CU与DU之间(例如:F1接口的信令),则第一信息可以为UE上下文建立、修改等与UE上下文管理的相关信息等。
另一种可能实现的方式中,若图6所示的通信方法应用于CU中CP与UP之间(例如 gNB-CU-CP与gNB-CU-UP),则第一信息可以为UE上下文建立、修改等与UE上下文管理的相关信息、初始上行链路RRC消息传输、下行链路/上行链路RRC消息传输等。
在本申请第三实施例中,以切换场景为例进行说明,在切换场景下第一网络节点可以为目标基站,第二网络节点为源基站,或者第一网络节点为核心网设备,第二网络节点为源基站。
在步骤601中,若满足预设条件,第二网络节点向第一网络节点发送第一信息的多个分段。
预设条件包括条件一和/或条件二。
方案一:
在一种情况下,源基站和/或目标基站已开启或存在限制传输数据包大小的协议(以下简称限制协议),例如:DTLS。在另一种情况下,网络的处理能力存在限制。对于上述两种情况下,第二网络节点和第一网络节点之间对于传输数据包的大小存在限制,该限制可以为第一阈值。
在此情况下,条件一可以包括以下一个或多个:
源基站确定原本要向目标基站发送的完整的切换请求信息的比特数大于或等于第一阈值。
从空口分段接收的信息的比特数大于或等于第一阈值。
源基站确定UE能力信息的比特数大于或等于第一阈值。
源基站确定RRC重配信息的比特数大于或等于第一阈值。
源基站确定RRC重配信息与UE能力信息的总比特数大于或等于第一阈值。
源基站确定完整的切换请求信息中RRC容器的比特总数大于或等于第一阈值。其中,RRC容器可以包括RRC重配信息、RRC恢复信息和/或UE能力信息。
UE上下文信息的比特总数大于或等于第一阈值。
上述中的第一阈值可以是限制所允许的最大阈值(例如限制协议规定的阈值),也可以是根据实际需要设置的阈值(例如比最大阈值小一点),还可以是根据网络处理能力确定的阈值(例如:源基站的最大处理能力)等,具体此处不做限定。
条件二:
从空口通过分段的方式接收UE能力信息。
本申请实施例中,仅以信息的尺寸大小用比特数描述为例进行示意性说明,信息的尺寸大小也可以用字节数等描述,此处不做限定。
上述的几种条件只是举例,在实际应用中,还可以有其他形式的条件,具体此处不做限定。
本申请第三实施例中,第一信息包括RRC容器,RRC容器中承载的信息包括RRC重配信息和/或终端设备的能力信息。
本申请实施例中,第一信息多个分段的数量可以是两个或两个以上,具体此处不做限定。
可选地,第二网络节点对第一信息的多个分段进行编码,其中,编码规则可以是抽象语法标记(abstract syntax notation one,ASN.1)等,具体此处不做限定。
可选地,多个分段包括一个第二分段,该第二分段为第一信息的第一条分段。
可选地,该第一条分段是指第二分段的编号为第一个(例如:若分段从0开始编号,则第一条分段的编号为0;若分段从1开始编号,则第一条分段的编号为1),即第二分段可以是第二网络节点向第一网络节点最开始发送的一个分段(即第二分段可以是时间上的第一条分 段),也可以不是最开始发送的一个分段(即第二分段可以不是时间上的第一条分段)。
可选地,多个分段中的第一条分段可以包括以下至少一项:
第一数值,该第一数值用于指示第一信息被分成多少个分段(例如:可以用于指示第一网络节点需要接收第一信息的分段数量)。
可选地,第一数值通过下述方法计算得到:
Figure PCTCN2020123022-appb-000001
可以理解的是,如果第一数值不是整数,可以向上取整。
示例性的,如果第一阈值为DTLS协议所规定的最大阈值16K,且第一信息的比特总数为50K,即第一数值为3.15,不是整数。可以向上取整,即第一数值为4,也即是第二网络节点向第一网络节点发送4个分段。
第二字段,第二字段用于指示第一信息是被分段的信息。
第三字段,用于指示该分段为第一信息的一个分段。
示例性的,若第一信息为切换请求信息,则第三字段可以具体用于指示该分段为切换请求信息的一个分段。
第四字段,用于指示该分段为第一信息的第一个分段。UE能力信息。
可选地,第一信息包括的能力信息是完整UE能力信息的精简,例如:第一信息包括一部分载波聚合的能力,该部分载波聚合能力可以支持载波较少的UE能力或者支持带宽较小的带宽组合等,此处不做限定。
可选地,第二网络节点可以将UE能力信息中多个带宽组合分在同一个分段中。
可选地,UE能力信息可以包括特性集合的子集,该特性集合包括带宽(band)组合的具体能力信息(例如:band组合需要引用特性集合中具体的能力信息)。
可选地,第二网络节点从空口接收终端设备发送的UE能力信息的多个分段,UE能力信息的多个分段中可以包括第二数值,该第二数值用于指示第二网络节点需要接收分段的数量或指示第二网络节点还需要接收分段的数量。例如:第二网络节点与第一网络节点传输UE能力信息,第二网络节点在接收到第二数值后。即可知道第二网络节点需要向第一网络节点发送多少个第一信息才能完成整个信息的传输。
示例性的,第二数值与第一数值的数量相同。
RRC重配信息。
可选地,RRC重配信息中的主小区可以在同一个分段中、辅小区可以在同一个分段中以及服务小区分可以在同一个分段中。
RRC容器中的信息(RRC重配信息、RRC恢复信息和/或终端设备的能力信息等)。
可选地,多个分段中的第一个分段可以除了包括以上中的至少一项,还可以包括其他信息。
例如:当第一信息为切换请求信息时,第一个分段还可以包括目标小区ID、UE上下文信息等,具体此处不做限定。
可选地,多个分段中的最后一个分段可以包括以下至少一项:
第二字段,第二字段用于指示第一信息是被分段的信息;
第三字段,用于指示分段为所述第一信息的一个分段;
第四字段,用于指示分段为最后一个分段;
示例性的,若分段从0开始编号,则第一条分段的编号为0,第二条分段的编号为1,以此类推。若分段从1开始编号,则第一条分段的编号为1,第二条分段的编号为2,以此类推。
可以理解的是,第九指示信息可以隐式的指示该分段为分段的信息,或者隐式的指示该分段为第一信息的一个分段。
UE能力信息。
最后一个分段包括UE能力信息的情况可以参考前述第一个分段包括UE能力信息的情况,此处不再赘述。
RRC重配信息。
可选地,RRC重配信息中的主小区、辅小区以及服务小区分可以在同一个分段中。
RRC容器中的信息(RRC重配信息、RRC恢复信息和/或终端设备的能力信息等)。
可选地,多个分段中的最后一个分段可以除了包括以上中的至少一项,还可以包括其他信息(例如:第一数值)。
例如:当第一信息为切换请求信息时,最后一个分段还可以包括目标小区ID、UE上下文信息等,具体此处不做限定。
可选地,除第一条分段、最后一条分段之外,其他的分段可以上述信息中的至少一个。
可选地,第一信息的一个分段由一个第四信息承载,即步骤601可以理解为:若满足预设条件,第二网络节点向第一网络节点发送多个第四信息,一个第四信息用于承载第一信息的一个分段。
可选地,第二网络节点对第一信息进行分段时,可以将相关的UE能力信息分在同一个分段。示例性的,UE能力信息中多个带宽组合分在同一个分段中。
可选地,第二网络节点对第一信息进行分段时,可以将相关的RRC重配信息分在同一个分段。示例性的,可以将主小区,辅小区,服务小区等分在同一个分段中。
在步骤602中,第一网络节点组装多个分段。
第一网络节点接收第一信息的多个分段后,可以组装多个分段,得到第一信息。
在一种可能实现的方式中,第一网络节点可以接收与组装同时进行。第一网络节点可以根据第九指示信息对已经接收的连续分段进行部分组装。示例性的,第一网络节点接收编号为1、2、3、7的分段,第一网络节点可以先组装1、2、3分段。组装的同时,接收其余的分段。可以提升第一网络节点组装多个分段的效率。
在另一种可能实现的方式中,第一网络节点接收所有分段之后再组装。第一网络节点根据第一数值和/或第三指示信息确定收到的多个分段是否完整。示例性的,若第一数值为6,第一网络节点可以确定第一信息包括6个分段,并根据第三指示信息确定已接收到6个第一信息的分段数量,则第一网络节点可以确定已完整接收第一信息的6个分段,并组装6个分段,得到第一信息。
可选地,若第一信息包括的能力信息是完整UE能力信息的精简,例如:第一信息包括一部分载波聚合的能力,该部分载波聚合能力可以支持载波较少的UE能力或者支持带宽较小的带宽组合,或者UE能力信息中多个带宽组合分在同一个分段中等,此处不做限定。
上述方式中,第一网络节点先获取到一部分的UE能力信息,然后根据获取到的部分UE能力,可以为用户终端进行重配置(例如将终端设备与源基站之间的传输链路参数修改为终端 设备与目标基站之间的传输链路参数,以便用户终端可以进行数据传输)。进一步的,第一网络节点对用户终端进行重配置的过程中,还可以继续接收其余的UE能力信息,进而减少第二网络节点的处理时延。
可选地,若相关的RRC重配信息分在同一个分段。示例性的,主小区、辅小区以及服务小区等分在同一个分段中。示例性的,SRB添加修改列表、SRB1以及DRB分在同一个分段中。则第一网络节点在接收到所有分段之前,可以先准备小区组的配置信息,提高第一网络节点的处理效率。
在一种可能实现的方式中,第一网络节点为核心网设备。
可选地,多个分段至少包括一个第一分段,该第一分段为RRC容器中的信息。由于核心网设备不用解析RRC容器,进而减少解析第一分段带来的处理时延。
本实施例中,若满足预设条件,第二网络节点可以向第一网络节点发送第一信息的多个分段,第一网络节点接收并组装多个分段,得到完整的第一信息,实现第二网络节点与第一网络节点之间传输完整数据,实现后续动作顺利进行。
第四实施例:
第四实施例是本申请实施例方案二的一种可选实施方式,第四实施例是第三实施例的一种变形方案,第四实施例对第三实施例中第一信息的多个分段做进一步限定。即第一分段包括RRC容器中的信息,第二分段包括除了Uu口信息外的全部信息(例如信元、IE等),且第二分段为编号为第一个的分段,进而第一网络节点接收第二分段之后,就可以配置相关资源(例如:切换场景下的切换准备工作、预留资源等),进而降低网络时延以及提高处理效率。
请参阅图7,图7为本申请实施例提供的另一种通信方法的流程示意图。
在本申请第四实施例中,以切换场景为例进行说明,在切换场景下第一网络节点可以为目标基站,第二网络节点为源基站,或者第一网络节点为核心网设备,第二网络节点为源基站。
步骤701、若满足预设条件,第二网络节点向第一网络节点发送第一信息的多个分段。
步骤702、第一网络节点组装多个分段。
本实施例中的步骤701与步骤702与前述图6所示实施例中的步骤601与步骤602类似,图7所示实施例是对图6所示实施例进一步的描述,其余部分可参考图6所示实施例。
在步骤701中,若满足预设条件,第二网络节点向第一网络节点发送第一信息的多个分段。
若满足预设条件,第二网络节点向第一网络节点发送第一信息的多个分段。其中预设条件如图6所示实施例中的预设条件类似,此处不再赘述。
第一信息的多个分段包括至少一个第一分段以及一个第二分段。其中,第一分段包括RRC容器中的信息(RRC重配信息、RRC恢复信息和/或终端设备的能力信息等)。进一步的,第一分段仅包括RRC容器中的信息,即第二分段包括第一信息中除了Uu口信息外的全部信息(例如信元、IE等)。其中,RRC容器信息可以理解为Uu口信息,Uu口为终端设备与接入网设备通信的空中接口。
可选地,第二分段也可以包括RRC容器中的信息以及第一信息中除了Uu口信息外的全部信息。
可选地,第二分段中包括第四字段,第四字段用于指示第二分段为第一信息的第一条分段。
如果第一网络节点接收到的信息中包括第四字段,则第一网络节点可以确定接收到的信息为第一信息的第一条分段。第一网络节点可以先根据第一条分段中的信息配置终端设备所需的资源。第一网络节点配置资源的同时可以继续接收第一信息的其他分段。
可选地,在切换场景下,第一网络节点接收到第二分段之后,可以为切换准备资源。即在接收所有分段之前,就可以进行切换的准备工作。从而降低网络时延,减少处理时间、提高处理效率和/或提高服务质量等。
可选地,在其他场景下,第一网络节点接收到第二分段之后,可以为辅基站添加准备资源。并不用收到所有分段,组装/解析之后才进行辅基站添加,从而降低网络时延,减少处理时间、提高处理效率和/或提高服务质量等。
可选地,若第二分段包括一部分RRC重配信息,第一网络节点先获取到一部分的RRC重配信息之后,第一网络节点可以先使用该部分的RRC重配信息为用户终端进行RRC重配信息的delta配置(即在RRC重配信息的基础上增删或修改等操作)。进一步的,第一网络节点进行delta配置的过程中,还可以继续接收其余的RRC重配信息,进而减少第一网络节点的处理时延。
可选地,第二网络节点对第一信息中的RRC容器进行拆分时,示例性的,第二网络节点可以将UE能力信息中多个带宽组合分在同一个分段中,或者将RRC重配信息中的主小区、辅小区以及服务小区分在同一个分段中。进而保证第一信息的每一个分段所含信息的完整性。
在步骤702中,第一网络节点组装多个分段。
本实施例中的步骤702与前述图6所示实施例中的步骤602类似,下面描述进一步的特征。在一种可能实现的方式中,第一网络节点为核心网设备。当第一网络节点为核心网设备,核心网设备收到第一信息的多个分段后,将第一信息的多个分段进行组装、处理并生成第二信息,可以理解,第二信息和第一信息的作用相同,只不过第二信息是经过核心网组装处理之后的信息。
可选地,多个分段至少包括一个第一分段,该第一分段仅包括RRC容器中的信息。当第一分段中的信息全部为RRC容器中的信息,核心网设备不需要对第一分段进行解读,可以直接将第一分段中的信息作为第二信息向其他网络节点发送。由于核心网设备不需要解读第一分段的内容,进而减少解析第一分段带来的处理时延。
可选地,核心网设备接收源基站发送第一信息的多个分段,第一信息的分段数量为第一数值,则核心网设备可以向目标基站发送第二信息的多个分段,该第二信息的分段数量与第一信息的分段数量相同。即核心网设备接收多少个分段的第一信息,就向目标基站发送多少个分段的第二信息。
可以理解的是,第二分段不一定是第一网络节点最先收到的分段,但第二分段不是第一网络节点接收的最后一个分段。即第一网络节点接收到第二分段时,并没有接收完所有的第一分段。
本实施例中,第二分段包括除了Uu口信息外的全部信息(例如信元、IE等),且第二分段为编号为第一个的分段,进而第一网络节点接收第二分段之后,就可以配置相关资源(例如:切换场景下的切换准备工作、预留资源等),进而降低网络时延,减少处理时间、提高处理效率、提高服务质量。
第五实施例
本申请第五实施例提供了一种通信方法,用于向接入网设备提供进行多播/组播业务的区域信息,从而实现多播/组播业务向需要接收该业务的终端设备的有效传输。
多播/组播业务是发送给对于所述业务感兴趣的终端设备的业务。现有技术中,对多播/组播业务感兴趣的终端设备需要在多播/组播服务器确定注册,注册内容可以包括所述终端设备感兴趣的多播/组播业务,以及所述终端设备接入/驻留的小区标识信息。多播/组播服务器可以根据所述终端设备的小区标识信息,确定所述多播/组播业务的传输区域,并将此小区列表下发至核心网。核心网根据小区列表与相应的多播控制实体和基站建立多播/组播会话,并通过多播/组播会话进行多播/组播业务数据的传输。当所述终端设备更换小区时,需要向多播/组播服务器上报其新的小区标识信息,从而多播/组播服务器对所述小区列表进行更新,更新的小区列表将被下发至核心网、多播控制实体,网络设备将根据更新后的小区列表进行多播/组播会话的建立/释放等。
然而目前技术无法解决一些无需在多播/组播服务器注册的多播/组播业务的传输问题。对于无需在多播/组播服务器注册的多播/组播业务(以下称为第一多播/组播业务)。服务器注册不掌握对于第一多播/组播业务感兴趣的终端设备的位置信息。对第一多播/组播业务感兴趣和/或正在接收第一多播/组播业务的终端设备(以下称为第一终端设备)。而第一终端设备需要向核心网注册相关信息,比如所述终端设备的标识信息(比如UE ID),所述终端设备感兴趣的多播/组播业务等。当第一终端设备处于RRC空闲态/非激活态时,核心网仅掌握第一终端设备的跟踪区列表(TA lists)。跟踪区列表中一般包括多个小区,也可是属于多个基站的多个小区,如图8,图8为跟踪区列表示意图。第一终端设备位于跟踪区列表中的某一小区。仅当第一终端设备移动出某一跟踪区列表所述的小区时,才会向核心网上报其新的跟踪区列表。也就是说,核心网不掌握需要接收第一多播/组播的第一终端设备的具体位置信息(比如第一终端设备所接入/驻留的小区),而只掌握第一终端设备的跟踪区列表(也就是可能存在第一终端设备的小区集合)。因此,此时核心网无法确定第一终端设备位于哪一个小区。若核心网与跟踪区列表中的每一个小区所属的接入网建立服务于该小区的多播/组播的会话资源,将会造成大量的资源浪费和无效传输。因此,此情况下核心网就无法与第一终端设备所驻留的小区所属的接入网设备有效建立用于传输第一多播/组播业务的会话资源。此时无法进行第一多播/组播业务的有效/高效传输。
为实现第一多播/组播业务的有效/高效传输,接入网设备可以从核心网接收第一多播/组播业务的区域信息,接入网设备在区域信息所对应的区域发送多播/组播业务通知。对于第一多播/组播业务感兴趣的第一终端设备接收多播/组播业务通知后,可以进入RRC连接态。则接入网设备可以确定第一终端设备的位置信息,并上报至核心网。核心网可以根据第一终端设备的位置信息,与第一终端设备的服务小区/基站建立用于传输第一多播/组播业务的会话资源,进行第一多播/组播业务的数据传输。
此方案可以保证向所有对多播/组播业务感兴趣的终端设备有效传输播/组播业务数据,同时避免网络设备向不存在对于所述业务感兴趣的终端设备的区域的无效传输。此方案可以,提高多播/组播业务通知的可靠性和准确性,提升服务质量,提高多播/组播业务传输效率,节省通信资源。
下面结合图9对本申请第五实施例提供的方法进行说明,图9示出了对多播/组播业区域信息的传输以及播/组播业的通知流程的示意图。
901:接入网设备接收来自于核心网的第一多播/组播业务的第一区域信息。
多播/组播业务的第一区域信息用于指示需要进行多播/组播业务通知的区域,或者说是可能存在正在接收第一多播/组播业务,和/或对多播/组播业务感兴趣的第一终端设备的区域。所述第一区域信息可以包括以下任意一项或多项:小区列表(cell list),跟踪区列表(TA list),基站列表,多播/组播(传输)区域信息/列表等,此处不做限制。
可选的,接入网设备在第一多播/组播业务开始传输、或者说在用于第一多播/组播业务数据传输的第一多播/组播会话建立之前,接收多播/组播业务的第一区域信息。
可选的,接入网设备接收来自于核心网设备的多播/组播业务的区域信息。包括一种可能的方式,对多播/组播业务的终端设备在核心网注册或者说加入多播/组播业务组(以下以注册代替注册或者说加入多播/组播业务组),终端设备的注册内容可以包括以下任意一项多项:所述终端设备的标识信息(比如UE ID等),所述终端设备的跟踪区列表(TA list),所述终端设备接入/驻留的小区标识信息(比如cell list,PID),所述终端设备通过测量得到的满足驻留条件的小区列表信息,所述终端设备感兴趣的多播/组播业务的标识信息(比如,所述多播/组播业务对应的移动用户识别标识group radio network temporary identifier,G-RNTI;临时移动组标识temporary mobile group identity,TMGI等)。另外一种可能的方式,核心网设备从多播/组播业务服务器或者其他网元接收上述信息。核心网设备接收到上述信息之后,一种可能的实施方式,核心网设备根据终端设备注册/上报的内容,确定所述终端设备感兴趣的多播/组播业务,终端设备的位置信息,从而确定需要进行多播/组播业务传输的区域信息。另外一种可能的实施方式,核心网设备根据终端设备注册/上报的内容,确定对某一(些)多播/组播业务感兴趣和/或正在接收所述业务的终端设备信息,包括所述终端设备的位置信息,从而确定需要进行多播/组播业务传输的区域信息。
902:接入网设备在第一区域信息指示的区域发送多播/组播业务通知信息。
所述多播/组播业务通知信息用于通知终端设备多播/组播业务即将开始,或者说通知终端设备做接收多播/组播业务的相关准备,或者说通知终端设备建立RRC连接/进入RRC连接态以接收多播/组播业务,或者说通知终端设备是否需要建立RRC连接/进入RRC连接态以接收多播/组播业务,或者说通知终端设备请求多播/组播业务的配置/控制信息,或者说通知终端设备通过广播信息(比如系统广播system information,多播控制信道MCCH发送的信息)请求所述多播/组播业务的控制/配置信息等。所述多播/组播业务是多播/组播业务通知信息所对应的多播/组播业务,所述多播/组播业务可以为一个或多个多播/组播业务。
可选的,接入网设备根据第一区域信息,在第一区域信息指示的区域发送多播/组播业务通知信息区域信息。比如,接入网设备根据第一区域信息中包括的小区列表(cell list)、跟踪区列表(TA list)、基站列表,多播/组播(传输)区域信息/列表等确定需要发送多播/组播业务通知信息的区域,可是发送多播/组播业务通知信息的小区/基站。
可选的,所述播/组播业务通知信息可以使用其所指示的多播/组播业务标识信息进行加扰,比如使用所述多播/组播业务所对应的移动用户识别标识(group radio network temporary identifier,G-RNTI)进行加扰、或者使用用于通知所述多播/组播业务变化的识别信息进行 加扰(也就是不同的多播/组播业务可能有不同的变化的识别信息)、或者使用预先定义的用于通知多播/组播的识别信息进行加扰等,此处不做限制。
903:终端设备接收多播/组播业务通知信息,并进行接收多播/组播业务的相应准备。
终端设备接收来自于接入网设备的多播/组播业务通知信息。所述终端设备为对所述多播/组播业务通知信息所对应的多播/组播业务感兴趣和或正在接收所述业务的一个或多个终端设备。
所述终端设备可以根据所述多播/组播业务通知信息的指示,建立RRC连接/进入RRC连接态以接收所述多播/组播业务,也可以通过广播信息(比如系统广播system information,多播控制信道MCCH发送的信息)请求所述多播/组播业务的控制/配置信息等,此处不做限制。
可选的,所述终端设备可以通过广播信息(比如系统广播system information,多播控制信道MCCH发送的信息)请求所述多播/组播业务的控制/配置信息。所述终端设备使用所=所述多播/组播业务的控制/配置信息进行所述多述播/组播业务数据的接收。
可选的,进入RRC连接态的所述终端设备可以向接入网设备上报RRC连接的原因为接收所述多播/组播业务、所述终端设备也可以上报其感兴趣的多播/组播业务标识信息。此时上报其感兴趣的多播/组播业务标识信息用于指示终端设备建立RRC连接的原因为欲接收所述多播/组播业务。可选的,接入网设备向核心网设备发送所述终端设备的相关信息,所述相关信息可以包括所述终端设备的RRC状态、所述终端设备的标识信息(比如UE ID)、所述终端设备感兴趣的多播/组播业务、所述终端设备所接入的小区的标识信息、所述终端设备所属的多播/组播区域信息、所述终端设备的数量等,此处不做限制。
904:接入网设备接收来自于核心网的多播/组播会话开始通知信息。
可选的,接入网设备接收来自于核心网的多播/组播会话开始通知信息。
核心网设备根据所述接入网设备上报的所述终端设备的相关信息,确定所述终端设备的位置信息,所述位置信息可以是所述终端设备所述的小区、基站/接入网设备、多播/组播业务区域等。所述核心网设备向所述位置信息相关的接入网设备发送多播/组播会话开始通知信息。
所述多播/组播会话开始通知信息用于指示多播/组播会话开始即将开始,或者说指示所述接入网设备为所述多播/组播建立会话,或者说指示所述接入网设备为所述多播/组播准备会话资源,或者说用于为所述多播/组播建立核心网与入网间的连接等。
可选的,所述接入网设备接收到所述多播/组播会话开始通知信息后,进行所述多播/组播会话开始通知信所要求的行为。并在行为成功进行后,向核心网设备发送多播/组播会话开始相应信息。
在多播/组播会话开始/建立之后,核心网设备通过所述多播/组播会话,向接入网设备发送所述多播/组播业务的数据。由于播/组播会话开始/建立仅面向于存在对所述多播/组播会话感兴趣的终端设备的小区/基站,因此实现所述多播/组播业务数据仅向存在对于所述多播/组播业务感兴趣的终端设备的小区/基站传输,而无需不会向不存在对于所述多播/组播业务感兴趣的终端设备的小区/基站传输。从而提高传输效率,节能传输资源和能源,保证服务质量。
上述方案通过核心网设备向接入网设备提供多播/组播业务的区域信息,实现接入网设备可以向可能存在对多播/组播业务感兴趣的终端设备的区域发送多播/组播业务通知信息。所述终端设备通过接收所述多播/组播业务通知信息,进行接收所述多播/组播业务的准备,比如建 立RRC连接、通过广播控制信道请求所述多播/组播业务的配置/控制信息等。对于进入RRC连接态的所述终端设备,接入网设备可以将这些终端设备位置信息(比如其所位于的小区信息)等上报核心网设备,核心网设备根据所述位置信息确定终端设备所属的小区/基站,建立多播/组播会话。核心网设备通过多播/组播会话向接入网设备发送所述多播/组播业务的数据。接入网设备将所述数据发送至对所述多播/组播业务感兴趣的终端设备。
上述方案可以实现多播/组播业务的有效/高效传输,避免多播/组播业务的无效传输,从而避免通信资源和能源的浪费。并且可以保证对于多播/组播业务感兴趣的终端设备均可接收到多播/组播业务,保证服务质量。
相应于上述方法实施例给出的方法,本申请实施例还提供了相应的装置,包括用于执行上述实施例相应的模块。模块可以是软件,也可以是硬件,或者是软件和硬件结合。
请参阅图10,本申请实施例中通信装置的一个实施例,该通信装置可以是核心网设备或接入网设备,也可以是核心网设备或接入网设备的部件(例如处理器、芯片或芯片系统),该通信装置包括:
收发单元1001,用于向第一网络节点发送第一信息,第一信息用于指示第一网络节点执行全配置;
收发单元1001,还用于接收第一配置信息,第一配置信息为第一网络节点在全配置中生成的配置信息,第一配置信息用于终端设备与第一网络节点通信。
本实施例中,该通信装置中各单元所执行的操作与前述图4至图9所示实施例中第二网络节点或第三网络节点所执行的操作类似,此处不再赘述。
本实施例中,收发单元1001向第一网络节点发送第一信息,该第一信息用于指示第一网络节点执行全配置,收发单元1001接收第一配置信息,第一配置信息为第一网络节点在全配置中生成的配置信息,且该第一配置信息用于终端设备与第一网络节点通信,收发单元1001通过发送第一信息的方式可以实现第一网络节点执行全配置,进而第一网络节点可以成功执行后续动作。
请参阅图11,本申请实施例中通信装置的一个实施例,该通信装置可以是接入网设备,也可以是接入网设备的部件(例如处理器、芯片或芯片系统),该通信装置包括:
收发单元1101,用于接收第一信息,第一信息用于指示第一网络节点执行全配置;
处理单元1102,用于执行全配置,在全配置中生成第一配置信息,第一配置信息在用于与终端设备通信;
收发单元1101,还用于向第二网络节点发送第一配置信息。
本实施例中,该通信装置中各单元所执行的操作与前述图4至图9所示实施例中第一网络节点所执行的操作类似,此处不再赘述。
本实施例中,收发单元1101接收第一信息,该第一信息用于指示第一网络节点执行全配置,处理单元1102执行全配置,在全配置中生成第一配置信息,第一配置信息为第一网络节点在全配置中生成的配置信息,且该第一配置信息用于终端设备与第一网络节点通信,收发单元1101通过向第二网络节点发送第一配置信息的方式可以实现与终端设备通信。
请参阅图12,本申请实施例中通信装置的一个实施例,该通信装置可以是核心网设备或接入网设备,也可以是核心网设备或接入网设备的部件(例如处理器、芯片或芯片系统),该 通信装置包括:
收发单元1201,用于若满足预设条件,向第一网络节点发送第一信息的多个分段,第一信息包括RRC容器,RRC容器中承载的信息包括RRC重配信息和/或终端设备的能力信息;
预设条件为以下至少一项:
能力信息的比特数大于或等于第一阈值,能力信息来自于终端设备;
RRC容器的比特总数大于或等于第一阈值;
第一信息的比特总数大于或等于第一阈值。
本实施例中,该通信装置中各单元所执行的操作与前述图4至图9所示实施例中第二网络节点或第三网络节点所执行的操作类似,此处不再赘述。
本实施例中,若满足预设条件,收发单元1201通过分段的方式发送第一信息,避免在第一信息超过限制的情况下,无法与第一网络节点传输完整的第一信息。
请参阅图13,本申请实施例中通信装置的一个实施例,该通信装置可以是核心网设备或接入网设备,也可以是核心网设备或接入网设备的部件(例如处理器、芯片或芯片系统),该通信装置包括:
收发单元1301,用于接收第一信息的多个分段,第一信息包括RRC容器,RRC容器中承载的信息包括RRC重配信息和/或终端设备的能力信息,多个分段来自于第二网络节点;
处理单元1302,用于组装多个分段。
本实施例中,该通信装置中各单元所执行的操作与前述图4至图9所示实施例中第一网络节点所执行的操作类似,此处不再赘述。
本实施例中,收发单元1301通过分段的方式接收第一信息的多个分段,处理单元1302组装多个分段,得到第一信息,避免在第一信息超过限制的情况下,无法与第二网络节点传输完整的第一信息。
请参阅图14,为本申请的实施例提供的上述实施例中所涉及的通信装置的结构示意图,其中,该通信装置具体可以为前述实施例中的第一网络节点,该通信装置的结构可以参考图14所示的结构。
通信装置包括至少一个处理器1411、至少一个存储器1412、至少一个收发器1413、至少一个网络接口1414和一个或多个天线1415。处理器1411、存储器1412、收发器1413和网络接口1414相连,例如通过总线相连,在本申请实施例中,所述连接可包括各类接口、传输线或总线等,本实施例对此不做限定。天线1415与收发器1413相连。网络接口1414用于使得通信装置通过通信链路,与其它通信设备相连,例如网络接口1414可以包括通信装置与核心网设备之间的网络接口,例如S1接口,网络接口可以包括通信装置和其他网络设备(例如其他接入网设备或者核心网设备)之间的网络接口,例如X2或者Xn接口。
处理器1411主要用于对通信协议以及通信数据进行处理,以及对整个通信装置进行控制,执行软件程序,处理软件程序的数据,例如用于支持通信装置执行实施例中所描述的动作。通信装置可以可以包括基带处理器和中央处理器,基带处理器主要用于对通信协议以及通信数据进行处理,中央处理器主要用于对整个终端设备进行控制,执行软件程序,处理软件程序的数据。图14中的处理器1411可以集成基带处理器和中央处理器的功能,本领域技术人员可以理解,基带处理器和中央处理器也可以是各自独立的处理器,通过总线等技术互联。本领域技术 人员可以理解,终端设备可以包括多个基带处理器以适应不同的网络制式,终端设备可以包括多个中央处理器以增强其处理能力,终端设备的各个部件可以通过各种总线连接。所述基带处理器也可以表述为基带处理电路或者基带处理芯片。所述中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中,也可以以软件程序的形式存储在存储器中,由处理器执行软件程序以实现基带处理功能。
存储器主要用于存储软件程序和数据。存储器1412可以是独立存在,与处理器1411相连。可选的,存储器1412可以和处理器1411集成在一起,例如集成在一个芯片之内。其中,存储器1412能够存储执行本申请实施例的技术方案的程序代码,并由处理器1411来控制执行,被执行的各类计算机程序代码也可被视为是处理器1411的驱动程序。
图14仅示出了一个存储器和一个处理器。在实际的终端设备中,可以存在多个处理器和多个存储器。存储器也可以称为存储介质或者存储设备等。存储器可以为与处理器处于同一芯片上的存储元件,即片内存储元件,或者为独立的存储元件,本申请实施例对此不做限定。
收发器1413可以用于支持通信装置与终端之间射频信号的接收或者发送,收发器1413可以与天线1415相连。收发器1413包括发射机Tx和接收机Rx。具体地,一个或多个天线1415可以接收射频信号,该收发器1413的接收机Rx用于从天线接收所述射频信号,并将射频信号转换为数字基带信号或数字中频信号,并将该数字基带信号或数字中频信号提供给所述处理器1411,以便处理器1411对该数字基带信号或数字中频信号做进一步的处理,例如解调处理和译码处理。此外,收发器1413中的发射机Tx还用于从处理器1411接收经过调制的数字基带信号或数字中频信号,并将该经过调制的数字基带信号或数字中频信号转换为射频信号,并通过一个或多个天线1415发送所述射频信号。具体地,接收机Rx可以选择性地对射频信号进行一级或多级下混频处理和模数转换处理以得到数字基带信号或数字中频信号,所述下混频处理和模数转换处理的先后顺序是可调整的。发射机Tx可以选择性地对经过调制的数字基带信号或数字中频信号时进行一级或多级上混频处理和数模转换处理以得到射频信号,所述上混频处理和数模转换处理的先后顺序是可调整的。数字基带信号和数字中频信号可以统称为数字信号。
收发器也可以称为收发单元、收发机、收发装置等。可选的,可以将收发单元中用于实现接收功能的器件视为接收单元,将收发单元中用于实现发送功能的器件视为发送单元,即收发单元包括接收单元和发送单元,接收单元也可以称为接收机、输入口、接收电路等,发送单元可以称为发射机、发射器或者发射电路等。
图14所示通信装置具体可以用于实现图4至图9对应方法第一实施例~第四实施例中第一网络节点所实现的步骤,并实现第一网络节点对应的技术效果,或者图14所示的通信装置还可以具体用于第五实施例中的核心网设备或接入网所实现的步骤。图14所示通信装置的具体实现方式,均可以参考图4至图9方法实施例中的叙述,此处不再一一赘述。
请参阅图15,为本申请的实施例提供的上述实施例中所涉及的通信装置1500的一种可能的示意图,该通信装置1500具体可以为前述实施例中的通信装置,该通信装置1500可以包括但不限于处理器1501、通信端口1502、存储器1503、总线1504,在本申请的实施例中,处理器1501用于对通信装置1500的动作进行控制处理。
此外,处理器1501可以是中央处理器单元,通用处理器,数字信号处理器,专用集成电路,现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。 其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框,模块和电路。该处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,数字信号处理器和微处理器的组合等等。所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统,装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
需要说明的是,图15所示通信装置具体可以用于实现第一实施例~第四实施例中第二网络节点或第三网络节点所执行的步骤的功能,并实现第二网络节点或第三网络节点对应的技术效果.或者图15所示的通信装置还可以具体用于第五实施例中的核心网设备或接入网所实现的步骤。图15所示通信装置的具体实现方式,均可以参考图4至图9对应的各个方法实施例中的叙述,此处不再一一赘述。
本申请实施例还提供一种存储一个或多个计算机执行指令的计算机可读存储介质,当计算机执行指令被处理器执行时,该处理器执行如前述实施例中通信装置可能的实现方式所述的方法,其中,该通信装置具体可以为前述图4至图9对应方法实施例中的第一网络节点、第二网络节点或第三网络节点,图9对应方法实施例中的接入网设备、核心网设备或终端设备。
本申请实施例还提供一种存储一个或多个计算机的计算机程序产品,当计算机程序产品被该处理器执行时,该处理器执行上述通信装置可能实现方式的方法,其中,该通信装置具体可以为前述图4至图9对应方法实施例中的第一网络节点、第二网络节点或第三网络节点,图9对应方法实施例中的接入网设备、核心网设备或终端设备。
本申请实施例还提供了一种芯片系统,该芯片系统包括处理器,用于支持通信装置实现上述通信装置可能的实现方式中所涉及的功能。在一种可能的设计中,该芯片系统还可以包括存储器,存储器,用于保存该通信装置必要的程序指令和数据。该芯片系统,可以由芯片构成,也可以包含芯片和其他分立器件,其中,该通信装置具体可以为前述图4至图9对应方法实施例中的第一网络节点、第二网络节点或第三网络节点,图9对应方法实施例中的接入网设备、核心网设备或终端设备。
可以理解,本申请中描述的系统、装置和方法也可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、 移动硬盘、只读存储器(read-only memory,ROM)、随机存取存储器(random access memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请中各个实施例之间相同或相似的部分可以互相参考。在本申请中各个实施例、以及各实施例中的各个实施方式/实施方法/实现方法中,如果没有特殊说明以及逻辑冲突,不同的实施例之间、以及各实施例中的各个实施方式/实施方法/实现方法之间的术语和/或描述具有一致性、且可以相互引用,不同的实施例、以及各实施例中的各个实施方式/实施方法/实现方法中的技术特征根据其内在的逻辑关系可以组合形成新的实施例、实施方式、实施方法、或实现方法。以上所述的本申请实施方式并不构成对本申请保护范围的限定。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。

Claims (54)

  1. 一种通信方法,其特征在于,包括:
    向第一网络节点发送第一信息,所述第一信息用于指示第一网络节点执行全配置;
    接收第一配置信息,所述第一配置信息为所述第一网络节点在所述全配置中生成的配置信息,所述第一配置信息用于终端设备与所述第一网络节点通信。
  2. 根据权利要求1所述的方法,其特征在于,
    所述第一信息包括第一字段,所述第一字段用于指示所述第一网络节点执行所述全配置。
  3. 根据权利要求1所述的方法,其特征在于,
    所述第一信息包括RRC重配信息,所述RRC重配信息至少不包括小区组配置信息、无线承载配置信息、测量配置信息中的一个或多个。
  4. 根据权利要求1-3任一项所述的方法,其特征在于,
    所述第一信息用于指示所述第一网络节点执行全配置包括:所述第一信息用于指示第二信息比特数大于或等于第一阈值,所述第二信息用于所述第一网络节点生成第二配置信息,所述第二配置信息用于所述终端设备与所述第一网络节点通信。
  5. 根据权利要求4所述的方法,其特征在于,
    所述第一信息和所述第二信息为切换请求信息。
  6. 根据权利要求1-4任一项所述的方法,其特征在于,
    所述向第一网络节点发送第一信息包括:第三网络节点向所述第一网络节点发送第一信息;
    所述方法还包括:所述第三网络节点接收第三信息,所述第三信息包含用于指示所述第一网络节点执行全配置的信息。
  7. 一种通信方法,其特征在于,包括:
    接收第一信息,所述第一信息用于指示所述第一网络节点执行全配置;
    执行全配置,在所述全配置中生成第一配置信息,所述第一配置信息在用于与终端设备通信;
    向所述第二网络节点发送所述第一配置信息。
  8. 根据权利要求7所述的方法,其特征在于,
    所述第一信息包括第一字段,所述第一字段用于指示执行所述全配置。
  9. 根据权利要求7所述的方法,其特征在于,
    所述第一信息包括RRC重配信息,所述RRC重配信息至少不包括小区组配置信息、无线承载配置信息、测量配置信息中的一个或多个。
  10. 根据权利要求7-9任一项所述的方法,其特征在于,
    所述第一信息用于指示所述第一网络节点执行全配置包括:所述第一信息用于指示第二信息比特数大于或等于第一阈值,所述第二信息用于所述第一网络节点生成第二配置信息,所述第二配置信息用于所述终端设备与所述第一网络节点通信。
  11. 根据权利要求10所述的方法,其特征在于,
    所述第一信息和所述第二信息为切换请求信息。
  12. 一种通信方法,其特征在于,包括:
    若满足预设条件,向第一网络节点发送第一信息的多个分段,所述第一信息包括RRC容器, 所述RRC容器中承载的信息包括RRC重配信息和/或终端设备的能力信息;
    所述预设条件为以下至少一项:
    所述能力信息的比特数大于或等于第一阈值,所述能力信息来自于所述终端设备;
    所述RRC容器的比特总数大于或等于第一阈值;
    所述第一信息的比特总数大于或等于第一阈值。
  13. 根据权利要求12所述的方法,其特征在于,所述向第一网络节点发送第一信息的多个分段包括:
    发送多个第四信息,所述第一信息一个分段由一个第四信息进行承载。
  14. 根据权利要求12或13所述的方法,其特征在于,
    所述多个分段包括:至少一个第一分段,所述第一分段为所述RRC容器中的信息。
  15. 根据权利要求14所述的方法,其特征在于,
    所述多个分段还包括:一个第二分段,所述第二分段是所述第一信息的第一条分段。
  16. 根据权利要求12-15任一项所述的方法,其特征在于,
    所述第一信息的分段包括以下信息中的一个或多个:
    第一数值,用于指示所述分段的数量;
    第二字段,第二字段用于指示第一信息是被分段的信息;
    第三字段,用于指示所述分段为所述第一信息的一个分段;
    第四字段,用于指示所述分段的编号;
    所述能力信息;
    所述RRC容器中的信息。
  17. 一种通信方法,其特征在于,包括:
    接收第一信息的多个分段,所述第一信息包括RRC容器,所述RRC容器中承载的信息包括RRC重配信息和/或终端设备的能力信息,所述多个分段来自于第二网络节点;
    组装所述多个分段。
  18. 根据权利要求17所述的方法,其特征在于,所述接收第一信息的多个分段包括:
    接收多个第四信息,所述第一信息一个的分段由一个第四信息进行承载。
  19. 根据权利要求17或18所述的方法,其特征在于,
    所述多个分段包括:至少一个第一分段,所述第一分段为所述RRC容器中的信息。
  20. 根据权利要求19所述的方法,其特征在于,
    所述多个分段还包括:一个第二分段,所述第二分段是所述第一信息的第一条分段。
  21. 根据权利要求18-20任一项所述的方法,其特征在于,
    所述第一信息的分段包括以下信息中的一个或多个:
    第一数值,用于指示所述分段的数量;
    第二字段,第二字段用于指示第一信息是被分段的信息;
    第三字段,用于指示所述分段为所述第一信息的一个分段;
    第四字段,用于指示所述分段的编号;
    所述能力信息;
    所述RRC容器中的信息。
  22. 一种通信装置,其特征在于,包括:
    收发单元,用于向第一网络节点发送第一信息,所述第一信息用于指示第一网络节点执行全配置;
    所述收发单元,用于接收第一配置信息,所述第一配置信息为所述第一网络节点在所述全配置中生成的配置信息,所述第一配置信息用于终端设备与所述第一网络节点通信。
  23. 根据权利要求22所述的装置,其特征在于,
    所述第一信息包括第一字段,所述第一字段用于指示所述第一网络节点执行所述全配置。
  24. 根据权利要求22所述的装置,其特征在于,
    所述第一信息包括RRC重配信息,所述RRC重配信息至少不包括小区组配置信息、无线承载配置信息、测量配置信息中的一个或多个。
  25. 根据权利要求22-24任一项所述的装置,其特征在于,
    所述第一信息用于指示所述第一网络节点执行全配置包括:所述第一信息用于指示第二信息比特数大于或等于第一阈值,所述第二信息用于所述第一网络节点生成第二配置信息,所述第二配置信息用于所述终端设备与所述第一网络节点通信。
  26. 根据权利要求25所述的装置,其特征在于,
    所述第一信息和所述第二信息为切换请求信息。
  27. 根据权利要求22-25任一项所述的装置,其特征在于,
    所述向第一网络节点发送第一信息包括:第三网络节点向所述第一网络节点发送第一信息;
    所述方法还包括:所述第三网络节点接收第三信息,所述第三信息包含用于指示所述第一网络节点执行全配置的信息。
  28. 一种通信装置,其特征在于,包括:
    收发单元,用于接收第一信息,所述第一信息用于指示所述第一网络节点执行全配置;
    处理单元,用于执行全配置,在所述全配置中生成第一配置信息,所述第一配置信息在用于与终端设备通信;
    所述收发单元,还用于向所述第二网络节点发送所述第一配置信息。
  29. 根据权利要求28所述的装置,其特征在于,
    所述第一信息包括第一字段,所述第一字段用于指示执行所述全配置。
  30. 根据权利要求28所述的装置,其特征在于,
    所述第一信息包括RRC重配信息,所述RRC重配信息至少不包括小区组配置信息、无线承载配置信息、测量配置信息中的一个或多个。
  31. 根据权利要求28-30任一项所述的装置,其特征在于,
    所述第一信息用于指示所述第一网络节点执行全配置包括:所述第一信息用于指示第二信息比特数大于或等于第一阈值,所述第二信息用于所述第一网络节点生成第二配置信息,所述第二配置信息用于所述终端设备与所述第一网络节点通信。
  32. 根据权利要求31所述的装置,其特征在于,
    所述第一信息和所述第二信息为切换请求信息。
  33. 一种通信装置,其特征在于,包括:
    收发单元,用于若满足预设条件,向第一网络节点发送第一信息的多个分段,所述第一信 息包括RRC容器,所述RRC容器中承载的信息包括RRC重配信息和/或终端设备的能力信息;
    所述预设条件为以下至少一项:
    所述能力信息的比特数大于或等于第一阈值,所述能力信息来自于所述终端设备;
    所述RRC容器的比特总数大于或等于第一阈值;
    所述第一信息的比特总数大于或等于第一阈值。
  34. 根据权利要求33所述的装置,其特征在于,所述收发单元,具体用于发送多个第四信息,所述第一信息一个分段由一个第四信息进行承载。
  35. 根据权利要求33或34所述的装置,其特征在于,
    所述多个分段包括:至少一个第一分段,所述第一分段为所述RRC容器中的信息。
  36. 根据权利要求35所述的装置,其特征在于,
    所述多个分段还包括:一个第二分段,所述第二分段是所述第一信息的第一条分段。
  37. 根据权利要求33-36任一项所述的装置,其特征在于,
    所述第一信息的分段包括以下信息中的一个或多个:
    第一数值,用于指示所述分段的数量;
    第二字段,第二字段用于指示第一信息是被分段的信息;
    第三字段,用于指示所述分段为所述第一信息的一个分段;
    第四字段,用于指示所述分段的编号;
    所述能力信息;
    所述RRC容器中的信息。
  38. 一种通信装置,其特征在于,包括:
    收发单元,用于接收第一信息的多个分段,所述第一信息包括RRC容器,所述RRC容器中承载的信息包括RRC重配信息和/或终端设备的能力信息,所述多个分段来自于第二网络节点;
    处理单元,用于组装所述多个分段。
  39. 根据权利要求38所述的装置,其特征在于,所述收发单元,具体用于接收多个第四信息,所述第一信息一个的分段由一个第四信息进行承载。
  40. 根据权利要求38或39所述的装置,其特征在于,
    所述多个分段包括:至少一个第一分段,所述第一分段为所述RRC容器中的信息。
  41. 根据权利要求40所述的装置,其特征在于,
    所述多个分段还包括:一个第二分段,所述第二分段是所述第一信息的第一条分段。
  42. 根据权利要求39-41任一项所述的装置,其特征在于,
    所述第一信息的分段包括以下信息中的一个或多个:
    第一数值,用于指示所述分段的数量;
    第二字段,第二字段用于指示第一信息是被分段的信息;
    第三字段,用于指示所述分段为所述第一信息的一个分段;
    第四字段,用于指示所述分段的编号;
    所述能力信息;
    所述RRC容器中的信息。
  43. 一种通信装置,其特征在于,包括处理器,所述处理器与存储器耦合,所述存储器用 于存储计算机程序或指令,所述处理器用于执行存储器中的所述计算机程序或指令,使得权利要求1至6任一项所述的方法被执行。
  44. 一种通信装置,其特征在于,包括处理器,所述处理器与存储器耦合,所述存储器用于存储计算机程序或指令,所述处理器用于执行存储器中的所述计算机程序或指令,使得权利要求7至11任一项所述的方法被执行。
  45. 一种通信装置,其特征在于,包括处理器,所述处理器与存储器耦合,所述存储器用于存储计算机程序或指令,所述处理器用于执行存储器中的所述计算机程序或指令,使得权利要求12至16任一项所述的方法被执行。
  46. 一种通信装置,其特征在于,包括处理器,所述处理器与存储器耦合,所述存储器用于存储计算机程序或指令,所述处理器用于执行存储器中的所述计算机程序或指令,使得权利要求17至21任一项所述的方法被执行。
  47. 一种通信系统,其特征在于,包括:如权利要求43所述的通信装置,和/或,如权利要求44所述的通信装置。
  48. 一种通信系统,其特征在于,包括:如权利要求45所述的通信装置,和/或,如权利要求46所述的通信装置。
  49. 一种芯片,其特征在于,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行计算机程序或指令,使得权利要求1至6任一项所述的方法被执行,或者使得权利要求7至11任一项所述的方法被执行。
  50. 一种芯片,其特征在于,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行计算机程序或指令,使得权利要求12至16任一项所述的方法被执行,或者使得权利要求17至21任一项所述的方法被执行。
  51. 一种计算机存储介质,其特征在于,所述计算机存储介质中存储有指令,所述指令在计算机上执行时,使得所述计算机执行如权利要求1至6任一项所述的方法,或者使得所述计算机执行如权利要求7至11任一项所述的方法。
  52. 一种计算机存储介质,其特征在于,所述计算机存储介质中存储有指令,所述指令在计算机上执行时,使得所述计算机执行如权利要求12至16任一项所述的方法,或者使得所述计算机执行如权利要求17至21任一项所述的方法。
  53. 一种计算机程序产品,其特征在于,所述计算机程序产品在计算机上执行时,使得所述计算机执行如权利要求1至6任一项所述的方法,或者使得所述计算机执行如权利要求7至11任一项所述的方法。
  54. 一种计算机程序产品,其特征在于,所述计算机程序产品在计算机上执行时,使得所述计算机执行如权利要求12至16任一项所述的方法,或者使得所述计算机执行如权利要求17至21任一项所述的方法。
PCT/CN2020/123022 2020-10-22 2020-10-22 一种通信方法、装置及系统 WO2022082688A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/123022 WO2022082688A1 (zh) 2020-10-22 2020-10-22 一种通信方法、装置及系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/123022 WO2022082688A1 (zh) 2020-10-22 2020-10-22 一种通信方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2022082688A1 true WO2022082688A1 (zh) 2022-04-28

Family

ID=81291160

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/123022 WO2022082688A1 (zh) 2020-10-22 2020-10-22 一种通信方法、装置及系统

Country Status (1)

Country Link
WO (1) WO2022082688A1 (zh)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106160937A (zh) * 2015-04-15 2016-11-23 中兴通讯股份有限公司 一种实现码块分割的方法及装置
US20170295524A1 (en) * 2016-04-08 2017-10-12 Nokia Technologies Oy Apparatuses and methods for indication of full configuration in handover signaling
CN109257141A (zh) * 2017-07-14 2019-01-22 电信科学技术研究院 一种码块分割方法、终端、基站及计算机可读存储介质
CN109995553A (zh) * 2017-12-29 2019-07-09 华为技术有限公司 一种通信方法,设备及其系统
US20190281518A1 (en) * 2018-03-11 2019-09-12 Htc Corporation Method of Configuring a User Equipment Configuration and Related Communication Device
CN110381557A (zh) * 2018-04-13 2019-10-25 华为技术有限公司 一种通信方法、装置、系统及存储介质
WO2019244317A1 (ja) * 2018-06-21 2019-12-26 株式会社Nttドコモ 通信装置、及び通信方法
CN111357204A (zh) * 2017-11-17 2020-06-30 高通股份有限公司 极性代码的上行链路控制信息分段

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106160937A (zh) * 2015-04-15 2016-11-23 中兴通讯股份有限公司 一种实现码块分割的方法及装置
US20170295524A1 (en) * 2016-04-08 2017-10-12 Nokia Technologies Oy Apparatuses and methods for indication of full configuration in handover signaling
CN109257141A (zh) * 2017-07-14 2019-01-22 电信科学技术研究院 一种码块分割方法、终端、基站及计算机可读存储介质
CN111357204A (zh) * 2017-11-17 2020-06-30 高通股份有限公司 极性代码的上行链路控制信息分段
CN109995553A (zh) * 2017-12-29 2019-07-09 华为技术有限公司 一种通信方法,设备及其系统
US20190281518A1 (en) * 2018-03-11 2019-09-12 Htc Corporation Method of Configuring a User Equipment Configuration and Related Communication Device
CN110381557A (zh) * 2018-04-13 2019-10-25 华为技术有限公司 一种通信方法、装置、系统及存储介质
WO2019244317A1 (ja) * 2018-06-21 2019-12-26 株式会社Nttドコモ 通信装置、及び通信方法

Similar Documents

Publication Publication Date Title
US11197216B2 (en) Handling of collision between SR procedure and PDU session establishment procedure for PDU session handover
US11252615B2 (en) Handover method that is based on DC and device
US11425779B2 (en) Configuration method and apparatus, and system
RU2767981C2 (ru) Способ обработки информации и соответствующее устройство
WO2019129117A1 (zh) 通信方法和装置
US20200396652A1 (en) Method, apparatus, computer program product and computer program for conditional handover
US11212720B2 (en) 5GSM handling on invalid PDU session
US20240064600A1 (en) Handover processing method, terminal, and storage medium
WO2019192458A1 (zh) 通信方法和装置
EP4124107A1 (en) Communication method, access network device, terminal device and core network device
CN110708720B (zh) 切换方法、分布单元、终端、集中单元及计算机存储介质
TWI775811B (zh) 通信方法、輔網絡節點和終端
WO2021031035A1 (zh) 一种通信方法及装置
US20220353641A1 (en) Multicast sending and receiving method and apparatus
WO2022082688A1 (zh) 一种通信方法、装置及系统
WO2021163832A1 (zh) 数据传输的方法和装置
WO2023231503A1 (zh) 通信的方法和装置
WO2023066223A1 (zh) 通信方法、通信装置、以及机算机存储介质
WO2024012296A1 (zh) 一种测量配置的方法、接入网设备和终端设备
WO2021056449A1 (zh) 一种会话切换方法、装置及相关设备
WO2024022687A1 (en) Inter cell beam management
CN113873585A (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: 20958270

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20958270

Country of ref document: EP

Kind code of ref document: A1