WO2023011004A1 - 通信方法及通信装置 - Google Patents

通信方法及通信装置 Download PDF

Info

Publication number
WO2023011004A1
WO2023011004A1 PCT/CN2022/098589 CN2022098589W WO2023011004A1 WO 2023011004 A1 WO2023011004 A1 WO 2023011004A1 CN 2022098589 W CN2022098589 W CN 2022098589W WO 2023011004 A1 WO2023011004 A1 WO 2023011004A1
Authority
WO
WIPO (PCT)
Prior art keywords
access network
network device
terminal device
header
header compression
Prior art date
Application number
PCT/CN2022/098589
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 EP22851720.7A priority Critical patent/EP4358579A1/en
Publication of WO2023011004A1 publication Critical patent/WO2023011004A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point

Definitions

  • the present application relates to the technical field of communication, and in particular, to a communication method and a communication device.
  • Multicast broadcast service is a service for multiple terminal equipment (user equipment, UE), such as live broadcast service, public safety service, batch software update service, etc.
  • the MBS data comes from the data server.
  • the data server sends the MBS data to the core network device, then the core network device sends the MBS data to the access network device, and finally the access network device sends the MBS data to at least one UE receiving the MBS service.
  • the MBS service When sending from the core network to the access network equipment, the MBS service is transmitted through a common transmission channel MBS session, and when sending from the access network equipment to the UE, there are two transmission methods: the first one can be point-to-point Multi-point (point to multi-point, PTM) transmission mode; the second can use point-to-point (point to point, PTP) transmission mode.
  • PTM point to multi-point
  • PTP point-to-point
  • the source access network device ie, the source access network device
  • another access network device ie, the target access network device
  • the source access network device and the target access network device transmit independently.
  • the access network device will enable the header compression function of MBS data packets , and the two access network devices (ie, the source access network device and the target access network device) perform header compression independently.
  • the source access network device For a terminal device receiving MBS services, when switching from the source access network device to the target access network device, since the two access network devices establish the header compression context independently, the source access network device The established compression context cannot be used to decompress the header of the data packet transmitted by the target access network device. Based on this, how to ensure the normal communication between the terminal device and the target access network device after handover becomes one of the urgent problems to be solved. one.
  • the present application provides a communication method and a communication device, which can ensure the normal communication between the terminal equipment and the target access network equipment after handover, and improve the reliability of communication.
  • the present application provides a communication method, which is applicable to a target access network device.
  • the method includes: determining that a first terminal device switches from a source access network device to a target access network device; sending first information to the first terminal device, where the first information is used to indicate a first packet header compression context, the The first header compression context is used to compress or decompress the header of the data packet.
  • the target access network device can The first terminal device sends the first information, so that the first terminal device can establish a first packet header compression context according to the received first information, and then keep the packet header compression context synchronization between the first terminal device and the target access network device, and ensure that the first packet header compression context is synchronized.
  • a terminal device After a terminal device is switched to the target access network device, it can normally decompress the data packet whose header has been compressed, which improves the reliability of communication.
  • the switching of the first terminal device from the source access network device to the target access network device may be the process of switching the first terminal device from the source access network device to the target access network device, or the first terminal device switches from the source access network device to the target access network device. After the access network device is switched to the target access network device. That is to say, the target access network device may send the first information to the first terminal device during the handover process of the first terminal device from the source access network device to the target access network device, or, when the first terminal device switches from the source access network device to After the access network device switches to the target access network device, it sends the first information to the first terminal device, which is not limited here.
  • the data packet involved in this application may be a data packet of an MBS service (for example, the data packet may be a data packet with an uncompressed header, or a data packet with a compressed header), etc., and there is no limitation here.
  • the data packets involved in this application may be data packets associated with the MBS service.
  • the method also includes:
  • the target access network device may stop using the packet header established in the target access network device
  • the compression context (or understood as deleting, or resetting, or refreshing, or skipping, or not using, or no longer using the packet header compression context established in the target access network device), that is, the target access network device does not Then send the data packet after header compression processing based on the previously created header compression context (that is, before the first terminal device switches over), but send the data packet without compressing the header when it is necessary to send the data packet.
  • the target access network device establishes (or describes as re-establishing) a new packet header compression context (that is, the first packet header compression context), and sends the first packet header compression context to the first terminal device, that is, the target access network device re-establishes Start the establishment process of the header compression context, and send the data packet after the header compression processing based on the first header compression context after it is determined that the first header compression context is synchronized between the first terminal device and the target access network device.
  • the whole process is easy to operate and has high applicability.
  • the method also includes:
  • the header compression context used when the target access network device compresses or decompresses the header of the data packet compresses or decompresses the header of the data packet.
  • the target access network device may suspend the use of the packet header already established in the target access network device.
  • Compression context can also be understood as skipping use, or temporarily not using, or disabling) the packet header compression context that has been established in the target access network device, or understand that the established packet header compression context in the target access network device
  • the state of the packet header compression context is set to unavailable state, or invalid state), that is, the target access network device temporarily does not send the data packet after the packet header compression processing based on the header compression context that has been created before the first terminal device switches over, Instead, the data packet with the uncompressed header is sent, and further, when a certain condition is subsequently met (for example, it is determined that the packet header compression context of the first terminal device and the target access network device are synchronized), the use is resumed (or understood as use, or Enabling the established packet header compression context in the target access network device, or understanding that the state of the established
  • the method also includes:
  • the target access network device when it is determined that the first terminal device establishes the first packet header compression context, it can be considered that the packet header compression context of the first terminal device and the target access network device are synchronized, therefore, the target access network device
  • the packet header compression context that has been created before the first terminal device switches over may be used again to perform packet header compression processing, and send the data packet with the header compressed to the terminal device.
  • the method also includes:
  • the determining that the first terminal device establishes the first packet header compression context includes:
  • the first terminal device establishes the first packet header compression context.
  • the feedback information may include a header compression context identifier, where one header compression context identifier corresponds to one first packet header compression context. Therefore, after the target access network device receives the feedback information from the first terminal device, the target access network device can determine that the first terminal device has established (or successfully established) the header compression context identifier according to the header compression context identifier in the feedback information.
  • the compression context identifies the corresponding first packet header compression context.
  • the sending the first information to the first terminal device includes:
  • the target access network device can send the first information to the first terminal device through PTP transmission, which can ensure that the first After the handover, the terminal device can correctly decompress the header-compressed data packet received from the target access network device (that is, the data packet whose header is compressed).
  • the sending the first information to the first terminal device through PTP transmission includes:
  • the first information may be carried in MAC CE, or RRC signaling, or packet data convergence layer protocol control protocol data unit (ie, PDCP control PDU) and sent to the first terminal device, without limitation here, the operation High flexibility.
  • the method also includes:
  • the target access network device can simultaneously send data packets to the terminal device through the PTP and PTM transmission paths, specifically, the Send the data packet with uncompressed packet header to the first terminal device based on the PTP transmission method, and send the compressed data packet with the packet header based on the PTM method.
  • the target access network device can send uncompressed data in the packet header to the first terminal device through PTP during implementation packet, to help the switched first terminal device establish a header compression context, and send a header-compressed data packet to the first terminal through PTP, so as to ensure that the progress of the first terminal device receiving data packets through PTP is not slower than that of other terminals The progress of the device receiving packets via PTM.
  • the sending the first information to the first terminal device includes:
  • the target access network device may send the first information to the first terminal device through the source access network device.
  • the target access network device may carry the first information in the handover request acknowledgment message and send it to the source access network device, wherein, after receiving the handover request acknowledgment message, the source access network device sends the first information through a handover command to the first terminal device.
  • the present application provides a communication method, which is applicable to a first terminal device.
  • the method includes: switching from a source access network device to a target access network device; receiving first information from the target access network device, where the first information is used to indicate a first packet header compression context, and the first The header compression context is used to compress or decompress the header of the packet.
  • the method also includes:
  • the receiving the first information from the target access network device includes:
  • the first information from the target access network device is received in a point-to-point PTP transmission manner.
  • the receiving the first information from the target access network device through PTP transmission includes:
  • the method also includes:
  • the compression context of the first header is carried in an uncompressed data packet with a header, the uncompressed data packet with a header corresponds to the first sequence number, and the compressed data packet with a header Corresponding to the second serial number, the first serial number is the same as the second serial number;
  • the method also includes:
  • the duplicate detection function of the switched first terminal device needs to consider whether the header of the data packet has been compressed. Specifically, when the first terminal device receives two data packets containing the same sequence number, the first The terminal device needs to judge whether the headers of the two data packets are compressed. If one of the headers is compressed and the other is not, the compressed data packet will be discarded. If both are compressed or not, then Packets received after discarding.
  • the header compressed data packet includes a header compression context identifier; the method further includes:
  • the first terminal device Before the first terminal device establishes the first header compression context corresponding to the header compression context identifier, save the data packet whose header is compressed;
  • the header compression data packet is saved, and the corresponding packet header can only be processed after the corresponding header compression context is established.
  • the compressed data packets are decompressed.
  • the receiving the first information from the target access network device includes:
  • the present application provides a communication device, which may be a target access network device.
  • the apparatus includes: a processing unit, configured to determine that the first terminal device is switched from the source access network device to the target access network device; a transceiver unit, configured to send first information to the first terminal device, the first terminal device The information is used to indicate the first packet header compression context, and the first packet header compression context is used to compress or decompress the packet header of the data packet.
  • processing unit is further configured to:
  • processing unit is further configured to:
  • the header compression context used when the target access network device compresses or decompresses the header of the data packet compresses or decompresses the header of the data packet.
  • processing unit is further configured to:
  • the transceiving unit is further configured to receive feedback information from the first terminal device, where the feedback information is used to instruct the first terminal device to establish the first packet header compression context;
  • the processing unit is further configured to determine, according to the feedback information, that the first terminal device establishes the first packet header compression context.
  • the transceiver unit is used for:
  • the transceiver unit is specifically configured to:
  • the transceiver unit is also used for:
  • the transceiver unit is also used for:
  • the present application provides a communication device, and the device may be a first terminal device.
  • the apparatus includes: a processing unit, configured to switch from a source access network device to a target access network device; a transceiver unit, configured to receive first information from the target access network device, and the first information is used to indicate A first packet header compression context, where the first packet header compression context is used to compress or decompress the packet header of the data packet.
  • the transceiver unit is also used for:
  • the transceiver unit is used for:
  • the first information from the target access network device is received in a point-to-point PTP transmission manner.
  • the transceiver unit is specifically configured to:
  • the transceiver unit is also used for:
  • the compression context of the first header is carried in an uncompressed data packet with a header, the uncompressed data packet with a header corresponds to the first sequence number, and the compressed data packet with a header Corresponding to the second serial number, the first serial number is the same as the second serial number;
  • the processing unit is also used for:
  • the header compressed data packet includes a header compression context identifier; the processing unit is further configured to:
  • the first terminal device Before the first terminal device establishes the first header compression context corresponding to the header compression context identifier, save the data packet whose header is compressed;
  • the transceiver unit is also used for:
  • the present application provides a communication device, which can be an access network device (such as a target access network device), or a device in the access network device, or can be matched with the access network device device used.
  • the communication device may also be a system on a chip.
  • the communication device can execute the method described in the first aspect.
  • the functions of the communication device may be realized by hardware, or may be realized by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the unit or module can be software and/or hardware.
  • the present application provides a communication device.
  • the device may be a terminal device (such as the first terminal device), or a device in the terminal device, or a device that can be used in conjunction with the terminal device.
  • the communication device may also be a system on a chip.
  • the communication device can execute the method described in the second aspect.
  • the functions of the communication device may be realized by hardware, or may be realized by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the unit or module can be software and/or hardware.
  • the present application provides a communication device, which may be an access network device (such as a target access network device), and the communication device includes a processor and a transceiver, and the processor and the transceiver use for executing computer programs or instructions stored in at least one memory, so that the apparatus implements the method according to any one of the first aspect.
  • a communication device which may be an access network device (such as a target access network device)
  • the communication device includes a processor and a transceiver, and the processor and the transceiver use for executing computer programs or instructions stored in at least one memory, so that the apparatus implements the method according to any one of the first aspect.
  • the present application provides a communication device, which may be an access network device (such as a target access network device), and the communication device includes a processor, a transceiver, and a memory.
  • the processor, the transceiver and the memory are coupled; the processor and the transceiver are used to implement the method according to any one of the first aspect.
  • the present application provides a communication device, which may be a terminal device (such as a first terminal device), and the communication device includes a processor and a transceiver, and the processor and the transceiver are used to perform at least A computer program or instruction stored in a memory, so that the apparatus implements the method according to any one of the first aspect.
  • a communication device which may be a terminal device (such as a first terminal device)
  • the communication device includes a processor and a transceiver, and the processor and the transceiver are used to perform at least A computer program or instruction stored in a memory, so that the apparatus implements the method according to any one of the first aspect.
  • the present application provides a communication device, which may be a terminal device (for example, a first terminal device), and the communication device includes a processor, a transceiver, and a memory.
  • the processor, the transceiver and the memory are coupled; the processor and the transceiver are used to implement the method according to any one of the first aspect.
  • the present application provides a computer-readable storage medium, in which computer programs or instructions are stored.
  • computer programs or instructions are executed by the computer, any one of the first to second aspects can be realized.
  • the present application provides a computer program product including instructions, the computer program product includes computer program code, when the computer program code is run on a computer, any one of the first to second aspects can be realized. item method.
  • Figure 1a is a schematic diagram of a 5G network architecture
  • Figure 1b is a schematic diagram of downlink data transmission between layers
  • Figure 1c is a schematic diagram of a CU-DU separation architecture
  • Figure 1d is a schematic diagram of another CU-DU separation architecture
  • Figure 1e is a schematic diagram of the distribution of an air interface protocol stack
  • FIG. 2 is a schematic diagram of an MBS service transmission process
  • FIG. 3 is a schematic diagram of a switching process
  • FIG. 4 is a schematic diagram of a scenario where a UE receiving a multicast broadcast service performs handover
  • FIG. 5 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a wireless bearer between an access network device and a terminal device provided by an embodiment of the present application
  • FIG. 7 is another schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a scene where a target access network device resets a header compression context provided by an embodiment of the present application
  • FIG. 9 is another schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a scene where the state of the header compression context in the target access network device is affected due to handover according to an embodiment of the present application;
  • FIG. 11 is another schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a scenario in which data packets are sent simultaneously through PTP and PTM transmission paths provided by this embodiment
  • Fig. 13 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • Fig. 15 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • Fig. 16 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • words such as “exemplary” or “for example” are used to mean an example, illustration or description. Any embodiment or design described herein as “exemplary” or “for example” is not to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present related concepts in a concrete manner.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • general packet radio service general packet radio service, GPRS
  • long term evolution long term evolution, LTE
  • LTE frequency division duplex frequency division duplex, FDD
  • LTE Time Division Duplex TDD
  • Universal Mobile Telecommunications System UMTS
  • Worldwide Interoperability for Microwave Access WiMAX
  • Fifth Generation (5G) System or new radio (new radio, NR) and future communication systems, etc. are not limited here.
  • the 5G communication system in the embodiment of this application is taken as an example, and the relevant network elements in the 5G communication system are introduced in detail as follows:
  • FIG. 1a is a schematic diagram of a 5G network architecture provided by an embodiment of the present application.
  • the network architecture can include terminal equipment, (wireless) access network ((radio) access network, (R)AN), core network (core network, CN) and data network (data network, DN ).
  • R wireless access network
  • core network core network
  • CN core network
  • data network data network
  • DN data network
  • the terminal equipment, RAN, CN and DN involved in FIG. 1a will be described in detail below.
  • the terminal equipment part includes terminal equipment 210 in FIG. 1a, and the terminal equipment 210 may also be called user equipment (user equipment, UE).
  • the terminal device 210 in the embodiment of the present application is a device with a wireless transceiver function, which can communicate with one or more core networks (core network, CN) via the access network device in the access network (access network, AN) 240. network elements to communicate.
  • Terminal equipment 210 may also be called an access terminal, terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless network equipment, user agent, or user device, among others.
  • the terminal device 210 may be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it may also be deployed on water, such as a ship; Terminal device 210 may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a smart phone, a cell phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) ), which can be handheld devices with wireless communication functions, computing devices or other devices connected to wireless modems, vehicle-mounted devices, wearable devices, drone devices or terminals in the Internet of Things, Internet of Vehicles, fifth-generation mobile communications ( fifth generation, 5G) network and any form of terminal in the future network, relay user equipment or terminals in the future evolution of the public land mobile network (public land mobile network, PLMN), etc., wherein the relay user equipment, for example, may It is a 5G residential gateway (RG).
  • SIP session initiation protocol
  • PDA personal digital assistant
  • the terminal device 210 may be a virtual reality (virtual reality, VR) terminal, an augmented reality (augmented reality, AR) terminal, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, or a smart grid.
  • the RAN includes access network equipment 240 .
  • the RAN may include one or more RAN devices (or access network devices), and the interface between the access network device and the terminal device may be a Uu interface (or called an air interface).
  • the names of these interfaces may remain unchanged, or may be replaced by other names, which is not limited in this application.
  • An access network device is a node or device that connects a terminal device to a wireless network.
  • the access network device includes but is not limited to: a new generation base station (generation node B, gNB) and an evolved node B ( evolved node B, eNB), next generation evolved node B (next generation eNB, ng-eNB), wireless backhaul equipment, radio network controller (radio network controller, RNC), node B (node B, NB), base station Controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station ((home evolved nodeB, HeNB) or (home node B, HNB)), baseband unit (baseBand unit, BBU), Transmission receiving point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), mobile switching center, etc., are not limited here.
  • the access network equipment can also be a base station in the 6G communication system, or an open base station (Open RAN) or a cloud base station (Cloud RAN).
  • Open RAN the access network equipment involved in the present invention or access The interface in the network equipment may become the internal interface of Open RAN, and the flow and information interaction between these internal interfaces can be realized by software or programs, so the technical solution of the present invention is also applicable to the Open RAN architecture, as long as the realization of the idea is consistent with this
  • the schemes of the inventions are the same or similar, that is, fall within the protection scope of the present invention.
  • the access network device may be a base station, and the solution provided in the embodiment of the present application is schematically described.
  • the control plane protocol layer structure may include radio resource control (radio resource control, RRC) layer, packet data convergence protocol (packet data convergence protocol, PDCP ) layer, radio link control (radio link control, RLC) layer, media access control (media access control, MAC) layer and physical layer (Physical Layer, PHY);
  • the user plane protocol layer structure may include PDCP layer, RLC layer , a MAC layer, and a physical layer.
  • a service data adaptation protocol service data adaptation protocol, SDAP
  • SDAP service data adaptation protocol
  • the data transmission needs to go through the user plane protocol layer, such as the SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer.
  • the SDAP layer, PDCP layer, The RLC layer, the MAC layer, and the physical layer may also be collectively referred to as an access layer.
  • At least one data radio bearer (data radio bearer, DRB) is established between the access network device and the terminal device to transmit data, and each DRB may correspond to a set of functional entities, such as including a PDCP layer entity, the At least one RLC layer entity corresponding to the PDCP layer entity, at least one MAC layer entity corresponding to the at least one RLC layer entity, and at least one physical layer entity corresponding to the at least one MAC layer entity.
  • at least one signaling radio bearer (Signalling radio bearer, SRB) can also be established between the access network device and the terminal device to transmit signaling, and the DRB and the SRB can be collectively called a radio bearer (radio bearer, RB).
  • each layer in the access network equipment and terminal equipment is called radio bearer.
  • a corresponding functional entity performs a corresponding function, such as a PDCP entity of the PDCP layer.
  • FIG. 1b is a schematic diagram of downlink data transmission between layers.
  • the downward arrow in FIG. 1b indicates data transmission, and the upward arrow indicates data reception.
  • the SDAP layer entity obtains the data from the upper layer, it can map the data to the PDCP layer entity of the corresponding DRB according to the QoS flow indicator (QFI) of the data, and the PDCP layer entity can transmit the data to at least one corresponding to the PDCP layer entity.
  • An RLC layer entity is further transmitted by at least one RLC layer entity to the corresponding MAC layer entity, and then the MAC layer entity generates a transmission block, and then performs wireless transmission through the corresponding physical layer entity.
  • the data is encapsulated correspondingly in each layer.
  • the data received by a certain layer from the upper layer of the layer is regarded as the service data unit (service data unit, SDU) of the layer, which becomes a protocol data unit (protocol data unit) after layer encapsulation. unit, PDU), and then passed to the next layer.
  • SDU service data unit
  • PDU protocol data unit
  • the data received by the PDCP layer entity from the upper layer is called PDCP SDU
  • the data sent by the PDCP layer entity to the lower layer is called PDCP PDU
  • the data received by the RLC layer entity from the upper layer is called RLC SDU
  • RLC PDU the data sent by the RLC layer entity to the lower layer It is called RLC PDU.
  • data can be transmitted between different layers through corresponding channels, for example, data can be transmitted between RLC layer entities and MAC layer entities through a logical channel (logical channel, LCH), and between MAC layer entities and physical layer entities can be transmitted through Transport channel (transport channel) to transmit data.
  • LCH logical channel
  • transport channel transport channel
  • the above downlink data may be MBS service data, such as live broadcast service data, public safety service data, or batch software update service data, etc., which is not limited here. That is to say, for the MBS service, the data transmission direction is from the access network device to the terminal device.
  • the terminal device also has an application layer and a non-access layer; wherein, the application layer can be used to provide services to applications installed in the terminal device, for example, the received Downlink data can be sequentially transmitted from the physical layer to the application layer, and then provided to the application program by the application layer; for another example, the application layer can obtain the data generated by the application program, and transmit the data to the physical layer in sequence, and send it to other communication devices.
  • the non-access layer can be used to forward user data, such as forwarding uplink data received from the application layer to the SDAP layer or forwarding downlink data received from the SDAP layer to the application layer.
  • the access network device may include one or more centralized units (centralized unit, CU) and one or more distributed units (distributed unit, DU), and multiple DUs may be centrally controlled by one CU, One DU can also be connected to multiple CUs.
  • the interface between the CU and the DU may be called an F1 interface, where a control plane (control panel, CP) interface may be F1-C, and a user plane (user panel, UP) interface may be F1-U.
  • CU and DU can be divided according to the protocol layer of the wireless network: for example, as shown in Fig. 1c, Fig. 1c is a schematic diagram of a CU-DU separation architecture. Wherein, the functions of the protocol layers above the PDCP layer are set in the CU, and the functions of the protocol layers below the PDCP layer (such as the RLC layer and the MAC layer, etc.) are set in the DU.
  • the above-mentioned division of the processing functions of CU and DU according to the protocol layer is only an example, and it can also be divided according to other methods.
  • the functions of the protocol layers above the RLC layer are set in the CU, the RLC layer and the following protocol layers.
  • the functions of the DU are set in the DU, and for example, the CU or DU can be divided into functions with more protocol layers, and for example, the CU or DU can also be divided into partial processing functions with protocol layers.
  • part of the functions of the RLC layer and the functions of the protocol layers above the RLC layer are set in the CU, and the rest of the functions of the RLC layer and the functions of the protocol layers below the RLC layer are set in the DU.
  • the functions of the CU or DU can also be divided according to the business type or other system requirements, for example, according to the delay, and the functions whose processing time needs to meet the delay requirement are set in the DU, which does not need to meet the delay
  • the required feature set is in the CU.
  • the CU may also have one or more functions of the core network.
  • the CU can be set on the network side to facilitate centralized management; the DU can have multiple radio functions, or the radio functions can be remotely set. This embodiment of the present application does not limit it.
  • the function of the CU may be implemented by one entity, or may also be implemented by different entities.
  • Fig. 1d is a schematic diagram of another CU-DU separation architecture.
  • the functions of the CU can be further divided, that is, the control plane and the user plane are separated and realized by different entities, which are the control plane CU entity (ie, the CU-CP entity) and the user plane CU entity (ie, the CU-UP entity). ), the CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the functions of the RAN device.
  • the interface between CU-CP entity and CU-UP entity can be E1 interface
  • the interface between CU-CP entity and DU can be F1-C interface
  • the interface between CU-UP entity and DU can be F1-U interface.
  • one DU and one CU-UP can be connected to one CU-CP.
  • one DU can be connected to multiple CU-UPs
  • one CU-UP can be connected to multiple DUs.
  • Fig. 1e is a schematic diagram of distribution of an air interface protocol stack.
  • the air interface protocol stack can be RLC, MAC, and PHY in the DU, and PDCP and above protocol layers in the CU.
  • the signaling generated by the CU can be sent to the terminal device through the DU, or the signaling generated by the terminal device can be sent to the CU through the DU.
  • the DU can directly encapsulate the signaling through the protocol layer and transparently transmit it to the terminal device or CU without parsing the signaling.
  • the sending or receiving of the signaling by the DU includes this scenario.
  • signaling at the RRC or PDCP layer will eventually be processed as data at the physical layer and sent to the terminal device, or converted from received data at the physical layer.
  • the signaling at the RRC or PDCP layer can also be considered to be sent by the DU, or sent by the DU and the radio frequency device.
  • CN includes network exposure function (network exposure function, NEF) 231, network storage function (network function repository function, NRF) 232, policy control function (policy control function, PCF) 233, unified data management (unified data management (UDM) network element 234, application function (application function, AF) 235, authentication server function (authentication server function, AUSF) 236, access and mobility management function (access and mobility management function, AMF) 237, session Management function (session management function, SMF) 238, user plane function (user plane function, UPF) 239 and (wireless).
  • NEF network exposure function
  • NRF network function repository function
  • PCF policy control function
  • PCF policy control function
  • UDM unified data management
  • application function application function, AF
  • authentication server function authentication server function
  • AUSF authentication server function
  • AMF access and mobility management function
  • SMF session Management function
  • user plane function user plane function, UPF
  • the AMF network element is a control plane network element provided by the operator network, responsible for access control and mobility management of terminal equipment accessing the operator network, such as including mobility status management, assigning temporary user IDs, authenticating and authorizing users, etc. .
  • the SMF network element is a control plane network element provided by the operator network, and is responsible for managing the PDU session of the terminal device.
  • a PDU session is a channel for transmitting PDUs, and terminal equipment needs to transmit PDUs with DN through the PDU session.
  • the PDU session is established, maintained and deleted by the SMF network element.
  • SMF network elements include session management (such as session establishment, modification and release, including tunnel maintenance between UPF and RAN), selection and control of UPF network elements, service and session continuity (service and session continuity, SSC) mode selection, Session-related functions such as roaming.
  • the UPF network element is the gateway provided by the operator, and is the gateway for communication between the operator's network and the DN.
  • UPF network elements include data packet routing and transmission, packet inspection, quality of service (QoS) processing, lawful interception, uplink packet detection, downlink data packet storage and other user-plane-related functions.
  • QoS quality of service
  • the PCF network element is a control plane function provided by the operator, and is used to provide the policy of the PDU session to the SMF network element.
  • Policies may include accounting-related policies, QoS-related policies, and authorization-related policies.
  • the AF network element is a functional network element that provides various business services, can interact with the core network through other network elements, and can interact with the policy management framework for policy management.
  • the CN may also include other possible network elements, such as network exposure function (network exposure function, NEF), network element unified data repository (unified data repository, UDR) network element.
  • network exposure function network exposure function
  • UDR unified data repository
  • the data network DN 220 which may also be called a packet data network (PDN), is usually a network outside the operator's network, such as a third-party network.
  • the operator network can access multiple data networks DN 220, and various services can be deployed on the data network DN 220, which can provide data and/or voice services for the terminal device 210.
  • the data network DN 220 can be a private network of a smart factory
  • the sensors installed in the workshop of the smart factory can be the terminal equipment 210
  • the control server of the sensors is deployed in the data network DN 220
  • the control server can provide services for the sensors.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • the data network DN 220 can be an internal office network of a certain company, and the mobile phone or computer of the company's employees can be the terminal device 210, and the mobile phone or computer of the employee can access information and data resources on the company's internal office network.
  • Nnef, Nausf, Nnrf, Namf, Npcf, Nudm, Nsmf, Naf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • interface serial numbers refer to the meanings defined in relevant standard protocols, and there is no limitation here.
  • the 5G communication system is taken as an example in Fig. 1a, and the solutions in the embodiments of the present application can also be applied to other possible communication systems, such as LTE communication systems or future sixth generation (the 6th generation) generation, 6G) communication system.
  • the foregoing network element or function may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.
  • MBS Multicast and Broadcast Service
  • MBS data (for example, MBS data can be live broadcast service data, public safety service data or batch software update service data, etc.) comes from the data server, first the data server sends the MBS data to the core network equipment, and then the core network equipment Send the MBS data to the access network device, and finally the access network device sends the MBS data to at least one UE receiving the MBS service.
  • the MBS service is transmitted through a common transmission channel MBS session.
  • the terminal device When sending from the access network equipment to the UE, there are two transmission methods: the first one can use PTM (point to multi-point, point to multipoint) transmission mode; the second can use PTP (point to point, point to point) transmission mode.
  • the terminal device can receive the data packet from the access network device through the PTM transmission mode, or receive the data packet from the access network device through the PTP transmission mode.
  • Packet header compression also known as header compression
  • the basic principle of packet header compression is to reduce the size of the packet header by deleting the original fields in the packet header or replacing the original fields in the packet header with shorter fields.
  • the first is the robust header compression (robust header compression, ROHC) algorithm for IP packet headers
  • the second is for Ethernet packet headers.
  • Ethernet header compression (ethernet header compression, EHC) algorithm the principle of the two is similar, and the compression process is performed at the PDCP layer.
  • ROHC Ethernet header compression
  • the compression end on the sending side and the decompression end on the receiving side generate and save context information (or described as context, etc.) for compression and decompression in advance, where each context corresponds to a context identifier (Context Identifier, CID). That is, at the beginning of data transmission, the sending side sends a complete IP packet header and the corresponding context identifier to the receiving side. In subsequent transmissions, the sending side only needs to send the dynamically changing part of the packet header. The semi-static part or static part does not need to be sent, and the decompression end restores the semi-static or static part according to the saved context information, thereby restoring the complete data packet header and submitting it to the upper layer.
  • CID context identifier
  • the packet header compression contexts at the sending and receiving ends are always synchronized, so that the information compressed at the sending side can be recovered losslessly at the receiving side.
  • the sending side does not turn on the compression function, correspondingly, the receiving side will turn on the decompression function, that is to say, the compression function and the decompression function are turned on or off at the same time.
  • a network device with a compression function is called a compression end, and an example device with a decompression function enabled is called a decompression end (also called a decompression end).
  • the compression end will use different contexts for header compression of data packet headers containing different content or information.
  • the number of contexts is controlled by the maximum context identifier (maxCID) parameter. If the new data packet header cannot match the established context match, but there are no more available context identifiers.
  • the compression side can choose to reuse the existing context (such as the one that has not been used for a long time), that is, create a new context to overwrite the existing context, or not to use the new context. Compress the header of the packet (that is, send the packet with the header uncompressed).
  • the mobility management of the UE in the connected state is controlled by the network device, that is, the network device instructs the UE which cell to switch to and how to perform the switch by sending a handover message.
  • the network device instructs the UE which cell to switch to and how to perform the switch by sending a handover message.
  • FIG. 3 is a schematic diagram of a handover process. As shown in Figure 3, after receiving the handover message, the UE can access the target cell according to the content contained in the handover message. Therefore, the successful sending of the handover message is a necessary condition to ensure successful handover under the traditional handover mechanism.
  • the switching process includes:
  • Step 1 The source access network device sends an RRC reconfiguration message to the UE in the connected state, which includes parameters such as measurement object, report configuration, and measurement identifier.
  • Step 2 After the UE measures a series of cells according to the received RRC reconfiguration message, it forms a measurement report and reports it to the currently connected source access network device.
  • Step 3 After receiving the measurement report reported by the UE, the source access network device will decide whether the UE needs to switch (that is, the source access network device makes a switch judgment). If it is determined to switch, the source access network device will send a switch request message to the target access network device.
  • Step 4 After the target access network device receives the handover request message sent by the source access network device, the target access network device decides whether to allow UE access according to the number of its own connections (that is, the target access network device performs admission control), if allowed, send a handover request response message (or described as a handover confirmation message, or a handover request confirmation message, etc.) to the source access network device, wherein the handover request response message includes the cell wireless network of the new cell Temporary identifier (cell radio network temporary identifier, C-RNTI), target access network device security-related algorithms and other parameters.
  • the new cell Temporary identifier cell radio network temporary identifier, C-RNTI
  • Step 5 After receiving the handover request response message from the target access network device, the source access network device can send a handover command to the UE, where the handover command can include the parameters in the handover request response message in step 4 , that is, the layer equivalent to the source access network device is transparent.
  • the handover command includes information about the target cell and related configuration parameters required by the UE to access the target cell.
  • the handover command includes information about the target cell (such as the physical cell identity (physical cell identifier, PCI) and the frequency information corresponding to the target cell (such as the frequency point corresponding to the target cell.
  • the content contained in the frequency information can refer to the specific description of the FrequencyInfoDL IE in the protocol TS38331)), the target cell The C-RNTI allocated for the UE, random access channel (random access channel, RACH) resource information (for example, dedicated RACH resources and/or common RACH resources) required to access the target cell, etc.
  • random access channel random access channel, RACH
  • Step 6 UE initiates random access to the target access network device according to the handover command.
  • Step 7 UE sends a message of completion of RRC reconfiguration to the target access network device.
  • FIG. 4 is a schematic diagram of a scenario where a UE receiving a multicast broadcast service performs handover.
  • the core network equipment can send data packets of the multicast broadcast service to different access network equipment (access network equipment 1 and access network equipment 2 shown in Figure 4), and then each access network The devices may respectively transmit data packets to at least one UE included in their corresponding cells.
  • the access network device 1 can use the PTM transmission method to send data packets to UE1, UE2 and UE3 in the cell 1, and the access network device 2 can also use the PTM transmission method to send data packets to UE4 and UE5 in the cell 2. data pack.
  • UE3 moves, for example, when UE3 moves from cell 1 to cell 2, UE3 needs to switch from an access network device 1 to access network device 2 to continue receiving multicast broadcast service data packets.
  • the aforementioned access network device 1 is the source access network device
  • the aforementioned access network device 2 is the target access network device.
  • the source access network device and the target access network device are sent independently.
  • the access network device will open the MBS data packet
  • the header compression function, and the two access network devices perform header compression independently.
  • the source access network device when switching from the source access network device to the target access network device, since the two access network devices establish header compression context independently, the source access network device establishes A good compression context cannot be used to decompress the header of the data packet transmitted by the target access network device, so how to ensure that the UE can normally receive the MBS service after handover has become one of the current problems to be solved urgently.
  • an embodiment of the present application provides a communication method, which can realize normal communication in a handover scenario, and is beneficial to improve communication reliability.
  • the method in the embodiment of the present application is not only applicable to the compression and transmission of the header part of the data packet, but also applicable to the compression and transmission of the payload part of the data packet, or may also be applicable to the entire data packet (i.e. The compression and transmission of the packet header part and the data part) are not limited here.
  • the data packet may also be called a message or a data message in some scenarios.
  • whether to enable the compression function can be determined by the access network device or terminal device according to the service characteristics or service QoS requirements or network load conditions.
  • the device can enable the header compression function for the radio bearer of the voice service; or when the network load is heavy or the network resources are tight, the header compression can be enabled for the radio bearer of certain services, and there is no limitation here.
  • the compression function is enabled on the sending side, the decompression function will be enabled on the receiving side; if the compression function is turned off on the sending side, the decompression function will be turned off on the receiving side.
  • the function and the decompression function on the receiving side can be turned on or off together, that is, the compression function and the decompression function are used together.
  • the network device with the compression function enabled may be referred to as the compression end, and the device with the decompression function enabled as an example may be referred to as the decompression end or the decompression end.
  • the sending side if the sending side enables the compression function, it can be understood that the sending side will perform compression processing on the data packets to be sent, and then send the compressed data packets to the receiving side.
  • the sending side disables the compression function, which means that the sending side will not perform compression processing on the data packet to be sent, but will send the complete data packet to the receiving side.
  • enabling the compression function can also be described as enabling the compression function, etc., and there is no limitation here, and not enabling the compression transmission function can also be described as turning off the compression function, or described as disabling the compression function.
  • the compression function is enabled, or it is described as the compression transmission function is turned off, and there is no limitation here.
  • the solution provided in this application is applicable to uplink transmission or downlink transmission.
  • the access network equipment in the downlink transmission, the access network equipment is the compression end, and the terminal equipment is the decompression end; in the uplink transmission, the terminal equipment is the compression end, and the access network equipment is the decompression end.
  • the following embodiment is described as an example of compressing the header of the data packet in the downlink transmission.
  • the compression context is the header compression context.
  • the data packet in the embodiment of the application can also be described as a message; the header in the embodiment of the application can also be described as a packet header or header; the uncompressed data packet in the embodiment of the application can be described as It is a full header data packet, a complete message header data packet, etc., and there is no limitation here; the data packet whose header is compressed in the embodiment of the present application can be described as a header compressed data packet, or can also be described as a compressed packet, or It can also be described as a compressed header data packet, which is not limited here.
  • the header compression context in this application may also be described as a header compression context, or may also be described as a context, which is not limited here.
  • the header compression context identifier in this application can also be described as a header compression context identifier, or as a context identifier, or as a context index, context index value or index value, which is not limited here.
  • FIG. 5 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • the method includes the following steps S501 to S502, wherein, the method execution body shown in FIG. 5 may be a target access network device, or the method execution body shown in FIG. 5 may also be a target access
  • the chip in the network device, etc. is not limited here.
  • the target access network device will be used as an example for description below.
  • the target access network device determines that the first terminal device switches from the source access network device to the target access network device.
  • the switching of the first terminal device from the source access network device to the target access network device may be: the first terminal device prepares to switch from the source access network device to the target access network device (that is, before switching), or, the first During the switching process of the terminal device from the source access network device to the target access network device (that is, during the switching process), or after the first terminal device successfully switches from the source access network device to the target access network device (that is, the switching process) After) etc., not limited here.
  • the switching process of the terminal device from the source access network device to the target access network device that is, during the switching process
  • the first terminal device successfully switches from the source access network device to the target access network device that is, the switching process
  • the target access network device when the target access network device receives the handover request message from the source access network device, it can determine that the handover process starts; when the target access network device determines that the random access is successful, it can It is determined that the handover procedure ends, or, when the target access network device receives the RRC reconfiguration complete message from the source access network device, it may be determined that the handover procedure ends, which is not limited here.
  • the target access network device sends the first information to the first terminal device.
  • the target access network device may send the first information to the first terminal device.
  • the target access network device may receive the Before switching to the target access network device, or when preparing to switch from the source access network device to the target access network device, send the first information to the first terminal device, or, the first terminal device switches from the source access network device to the target access network device During the switching process of the target access network device, the first information is sent to the first terminal device, or, after the first terminal device is successfully switched from the source access network device to the target access network device, the first information is sent to the first terminal device a message.
  • the transmission mode of the first information may be transmitted by using a PTM transmission mode, or may also be transmitted by using a PTP transmission mode, etc., which is not limited here.
  • the target access network device sends the first information through the PTP transmission mode
  • all terminal devices under the target access network device that is, the first terminal device and others that have previously received the MBS service under the target access network device All terminal devices can receive the first information.
  • the target access network device sends the first information to the first terminal device through the PTP transmission mode, only the first terminal device can receive the first information.
  • the terminal device receiving the MBS service under the target access network device cannot receive or obtain the first information.
  • the first information is used to indicate the first header compression context
  • the first header compression context is used to compress or decompress the header of the data packet.
  • the data packets transmitted by the target access network device belong to the same MBS service
  • the MBS service may include at least one MBS service.
  • a wireless bearer can be established between the access network device and each terminal device to transmit information such as data and signaling.
  • the terminal device is switched from the source access network device After reaching the target access network device, the target access network device needs to newly configure a radio bearer for the switched terminal device, that is, the first terminal device.
  • FIG. 6 is a schematic diagram of a wireless bearer between an access network device and a terminal device according to an embodiment of the present application.
  • terminal device 1 and terminal device 2 are terminal devices that receive the data packets of the multicast broadcast service under the target access network device before the handover of terminal device 3, wherein terminal device 1 and the target access network
  • the radio bearer between devices is radio bearer 1
  • the radio bearer between terminal device 2 and the target access network device is radio bearer 2.
  • Terminal device 3 is a terminal device that is switched to the target access network device to receive the same multicast broadcast service, that is, terminal device 1
  • terminal device 2 and terminal device 3 are terminal devices that receive the same multicast broadcast service. Therefore, when the terminal device 3 is switched from the source access network device to the target access network device, the target access network device needs to newly configure a radio bearer for the switched terminal device 3 (radio bearer 3 as shown in FIG. 6 ).
  • the three radio bearers can be used to transmit the same MBS data packet.
  • the compression function is configured and/or executed at the granularity of radio bearers, that is, different radio bearers can be configured with independent compression functions.
  • different terminals The radio bearers that the devices receive data packets are different from each other, but from the perspective of the base station, the base station can transmit data packets to three different terminal devices through the same PTM transmission path in the same radio bearer, so the compression function is for different The devices are executed uniformly, while the decompression function is executed independently by different devices. It can be understood that the PTM transmission paths of the three radio bearers share a set of protocol stacks for unified processing on the base station side.
  • the base station uses this set of protocol stacks (that is, the radio bearer on the base station side) to transmit MBS data packets to terminal devices 1 and 2, and uses the established header compression context to perform header compression on the data packets.
  • Compression After the terminal device 3 is switched over, the base station side uses the set of protocol stacks (that is, the radio bearer on the base station side) to transmit MBS data packets to the terminal devices 1-3, but stops using the established packet header compression context to compress the data. The packet performs header compression, and establishes a new packet header compression context for subsequent header compression of the MBS data packet.
  • the target access network device sends the first information to the first terminal device before, during, or after the handover of the first terminal device.
  • One piece of information can be understood as: the target access network device carries (or bears) the first header compression context in the header uncompressed data packet and sends it to the first access network device, or it can also be understood as The first information for indicating the first header compression context is carried in the header uncompressed data packet, and sent to the first terminal device.
  • the first header compression context may also be carried in the signaling, that is, the first information used to indicate the first header compression context may be carried in the signaling and sent to the first terminal device.
  • the signaling involved may be media access control element (MAC control element, MAC CE), or radio resource control (radio resource control, RRC) signaling, or packet data convergence layer protocol control protocol data unit (PDCP control protocol data unit, PDCP control PDU), etc., there is no limitation here.
  • the sending of the first information by the target access network device to the first terminal device may be understood as:
  • the target access network device may send the first information to the first terminal device through the source access network device, where the first information is carried in the handover command. That is to say, when the target access network device sends the first information during the handover process, the first information may be carried in the handover configuration.
  • the target access network device receives the handover request message (or other Xn interface messages) from the source access network device, it can The handover request message judges whether the terminal equipment needs to receive the MBS service.
  • the MBS service to be received by the first terminal device may be indicated through an existing field or a newly added field in the handover request message. Understandably, if the transmission of the MBS service (or the radio bearer corresponding to the MBS service) has enabled the compression function in the target access network device, the target access network device may respond to the handover request sent to the source access network device
  • the message is either described as a handover confirmation message, or described as an existing field or a newly added field in the handover request confirmation message to indicate the first information corresponding to the MBS service or radio bearer, so that the handover request response message including the first information sent to the source access network device.
  • the source access network device may send or transparently transmit the information carried in the handover request confirmation message to the first terminal device through a handover command.
  • the information carried in the handover request acknowledgment message may include the first information and the like, which is not limited here.
  • the first terminal device may update or replace or refresh the header compression context established under the source access network device according to the first packet header compression context indicated by the first information in the switching command, or cover. Understandably, if the source access network device does not enable the compression function, correspondingly the first terminal device will not enable the decompression function, because the compression function and the decompression function are both turned off or turned on together. Therefore, the context established before the handover does not exist in the first terminal device. Based on this, the establishment of the first packet header compression context by the first terminal device according to the first information may be as follows: after the first terminal device receives the switching command, it can establish, create or newly create the first packet header compression context according to the first information in the switching command.
  • the header compression context established by the first terminal device may be the header compression context that the first terminal device synchronizes with the source access network device when receiving the MBS service under the source access network device. That is to say, the first terminal device can delete the header compression context established when the first terminal device receives the MBS service under the source access network device, and then establish the first packet header according to the first information received from the target access network device Compression context.
  • Deletion here may refer to freeing, deprecating, or skipping the use of the established compression context. Therefore, after it is subsequently determined that the first terminal device is successfully handed over to the target access network device, the target access network device can use the first header compression context, that is, the new header compression context, to compress the header of the data packet to generate The header compressed data packet is sent to all terminal devices under the target access network device, wherein all terminal devices under the target access network device, that is, the first terminal device and others that have received the MBS service under the target access network device before Terminal Equipment.
  • the first terminal device may, according to the The first packet header compression context, that is, the new header compression context, decompresses the header-compressed data packet received from the target access network device, that is, the header compressed data packet.
  • the header uncompressed data packet used to carry the first information, MAC CE, RRC signaling, PDCP control PDU, handover request message or handover command may also include the header compression context identifier corresponding to each header compression context (For convenience of description, it may also be referred to as context identifier for short) or index value and other information, which is not limited here.
  • one header compression context corresponds to one context identifier. Therefore, after the first terminal device receives a data packet with an uncompressed header or MAC CE or RRC signaling or PDCP control PDU or a switching command, the first terminal device can save the correspondence between the first header compression context and the corresponding context identifier.
  • the first information may include multiple header compression contexts and corresponding multiple context identifiers, where each header compression context is used to compress and decompress a corresponding header.
  • the first information is sent to the switched first terminal device, which can make The first terminal device establishes a corresponding context according to the first information, so that the first terminal device and the target access network device can maintain the synchronization of the header compression context after switching, and then can compress the received header from the target access network device
  • the correct decompression of the data packet is beneficial to improve the reliability of the communication.
  • the target access network device updates the header compression context of the terminal device through the handover configuration
  • the terminal device can also maintain the synchronization of the header compression context with the target access network device after the handover, Furthermore, the header compressed data packet received from the target access network device can be correctly decompressed, which is beneficial to improving the reliability of communication.
  • FIG. 7 is another schematic flowchart of the communication method provided by the embodiment of the present application.
  • the method includes the following steps S701 to S703, wherein the method execution body shown in FIG. 7 may be a target access network device, or the method execution body shown in FIG. 7 may also be a target access network device
  • the chip in the network device, etc., is not limited here.
  • the target access network device will be used as an example for description below.
  • the target access network device determines that the first terminal device switches from the source access network device to the target access network device.
  • step S701 in this embodiment of the present application reference may be made to the description of step S501 in Embodiment 1 corresponding to FIG. 5 , and details are not repeated here.
  • the target access network device stops using the header compression context used when the target access network device compresses or decompresses the header of the data packet before the first terminal device switches from the source access network device to the target access network device .
  • the target access network device may also stop using the information that the target access network device compresses the header of the data packet before the first terminal device switches from the source access network device to the target access network device.
  • the header compression context used is because the header compression context of the target access network device has not been established after the first terminal device switches over. Therefore, the target access network device needs to re-establish or establish and save, or establish and store the context.
  • the context re-established by the target access network device can be described as the first packet header compression context, and The first packet header compression context is sent to all terminal devices including the first terminal device, that is, the first packet header compression context is sent through PTM transmission.
  • stop using can be understood as deleting, resetting, refreshing, skipping or no longer using, wherein different descriptions can be replaced with each other, and this application does not limit this.
  • the target access network device determines that the first terminal device establishes the first packet header compression context, in order not to affect the normal transmission of the MBS service, if the target access network device If the network access device needs to send data packets, the target access network device can send uncompressed data packets, that is, the compression function is not enabled, or the compression function is disabled.
  • the target access network device determines that the first terminal device establishes the first packet header compression context, or the target access network device determines that the first terminal device successfully establishes the first packet header compression context. From the perspective of air interface transmission, the switching of the first terminal device will cause the target access network device that is transmitting the MBS data packet in the compressed mode to change to the state of not using the compressed mode to transmit the MBS data packet, that is, the sent MBS data packet is transmitted from The data packet whose header is compressed becomes the data packet whose header is not compressed.
  • the target access network device sends the first information to the first terminal device in a PTM transmission manner.
  • the target access network device with the compression function turned on or the compression function enabled when the first terminal device is about to switch from the source access network device to the target access network device , sending the first information to the first terminal device through the PTM transmission method, or, during the handover process of the first terminal device from the source access network device to the target access network device, sending the first information to the first terminal device through the PTM transmission method A message, or, after the first terminal device successfully switches from the source access network device to the target access network device, send the first information to the first terminal device in a PTM transmission manner.
  • the target access network device sending the first information to the first terminal device through the PTM transmission mode can be understood as: the target access network device carries or bears the compression context of the first header in the uncompressed data packet of the packet header, through Sending to the first access network device through PTM transmission, or it can also be understood as carrying the first information for indicating the compression context of the first header in the uncompressed data packet of the packet header, and sending it to the first access network device through PTM transmission. Terminal Equipment.
  • the first header compression context may also be carried in the signaling, that is, the first information used to indicate the first header compression context may be carried in the signaling, and sent to the first access network device through PTM transmission .
  • the signaling involved may be media access control element (MAC control element, MAC CE), or radio resource control (radio resource control, RRC) signaling, or packet data convergence layer protocol control protocol data unit (PDCP control protocol data unit, PDCP control PDU), etc., there is no limitation here.
  • MAC control element media access control element
  • RRC radio resource control
  • PDCP control protocol data unit packet data convergence layer protocol control protocol data unit
  • the uncompressed header header data packet or signaling used to carry the first information may also include information such as header compression context identifier or context identifier or index value corresponding to the header compression context, which is not limited here.
  • one header compression context corresponds to one context identifier. Therefore, after the first terminal device receives the data packet or signaling with uncompressed header, the first terminal device can save the header compression context included in the data packet or signaling with uncompressed header and the correspondence between the corresponding context identifier relationship, so that when a header-compressed data packet is subsequently received, according to the context identifier carried in the header-compressed data packet, the corresponding first header compression context is determined to decompress the header-compressed data packet.
  • the first information may include multiple header compression contexts and corresponding multiple context identifiers, where each header compression context is used to compress and decompress a corresponding header.
  • the target access network device may start to send the first information before, during or after the handover, for the handover terminal device, that is, the first terminal device, the first terminal device needs to After the completion, the first information may be received, and then the first header compression context is established according to the first information.
  • the first terminal device may establish the first packet header compression context according to the first information:
  • the packet header compression context is updated to be the first packet header compression context.
  • the header compression context established by the first terminal device may be the header compression context that the first terminal device synchronizes with the source access network device when receiving the MBS service under the source access network device.
  • the first terminal device may delete, release or discard the header compression context established when the first terminal device receives the MBS service under the source access network device, and then according to the first information to establish the first header compression context.
  • the source access network device itself does not enable the compression transmission function, when the first terminal device receives the MBS service under the source access network device, it does not establish a header compression context associated with the MBS service. Therefore, the first terminal The establishment of the first packet header compression context by the device according to the first information may be: the first terminal device newly establishes or newly creates the first packet header compression context in the first terminal device according to the first information.
  • this type of terminal equipment can also receive the first information, therefore, this type of terminal equipment can receive the first information according to the received first information
  • the established context is continuously updated to the first packet header compression context indicated by the most recent or newly received first information.
  • this type of terminal device can first compare the first packet header compression context indicated by the first information received this time with that established before the first terminal device switched or based on the first information received this time Whether the header compression context is the same, if the first packet header compression context is not the same as the header compression context established before the first terminal device switched or based on the first information received before this time, use the first packet header compression context to replace the first The header compression context established by the terminal device before switching or based on the first information received before this time.
  • the target access network device may start to compress the packet header corresponding to the first packet header compression context, that is, enable the compression function.
  • the target access network device in the embodiment of the present application uses the PTM transmission method to send the first information, generally, when the target access network device determines all terminal devices under the target access network device, that is, including The compression function can only be enabled after the switched first terminal device and other terminal devices receiving services under the target access network device have established a header compression context synchronized with the target access network device.
  • the access network device 1 shown in FIG. 4 is the source access network device
  • the access network device 2 is the target access network device
  • UE3 is the first terminal device.
  • the other terminal devices that received the MBS service under the target access network device before are UE4 and UE5.
  • the target access network device can communicate with UE4 and UE5 before the target access network device stops using
  • the synchronous header compression context compresses the data packets that need to be sent, but when the data packets need to be sent, send the data packets with uncompressed headers until all terminal devices are guaranteed, that is, UE3, UE4 and UE5 as shown in Figure 4 , after the header compression context synchronized with the target access network device is established, the header of the data packet is then compressed.
  • the header compression data packet includes a context identifier, therefore, for each terminal device under the target access network device, it can determine the corresponding first header compression context according to the context identifier included in the header compression data packet , so as to decompress the header compressed data packet according to the determined first header compression context.
  • the header compression context used before the first terminal device is switched is stopped and the first packet header compression context is re-established. Therefore, from the perspective of air interface transmission, the first packet header compression context is the same as the first packet header compression context.
  • the header compression context used by the terminal device before switching is not necessarily the same, that is, the context information corresponding to the same context identifier is not necessarily the same. Therefore, when the compressed MBS data packet is transmitted again, that is, the sent MBS data packet changes from an uncompressed data packet at the header to a compressed data packet at the header, the compression context used is the same as that used before the first terminal device switches The compression contexts are not the same.
  • each of the above steps is described by taking the handover of a terminal device as an example, that is, a first terminal device.
  • the target access network device needs to perform multiple reset processes for the multiple switched first terminal devices, That is, the steps of disabling the compressed transmission function and sending the first information through the PTM transmission mode are performed again.
  • different reset processes may be independent of each other, that is, each reset process does not affect each other. That is to say, if a terminal device switches over, the target access network device resets and re-establishes part or all of the context.
  • the target access network device needs to Perform a reset, and resend the first information, that is, re-execute the establishment process of the header compression context. If a terminal device is switched over, the target access network device is reset, and another terminal device is switched over before any context is rebuilt, then the target access network device can be reset again or not do anything.
  • FIG. 8 is a schematic diagram of a scene where a target access network device resets a header compression context according to an embodiment of the present application.
  • UE3 and other terminals receive the MBS service from the access network device 1 together, and the access network device 1 enables the header compression function for the MBS service data packet.
  • the access network device 1 and the terminal devices below the access network device 1 (UE1, UE2 and UE3 as shown in Figure 8) establish a mutually synchronized header compression context (line 1 in Figure 8 shown context1-context3), wherein different header compression contexts have different context identifiers.
  • the access network device 2 has enabled the header compression function for the same MBS service data packet.
  • the access network device 2 and the terminal devices below the access network device 2 (UE4 and UE5 as shown in Figure 8)
  • UE4 and UE5 as shown in Figure 8 mutually synchronized header compression contexts (context1-context3 as shown by line 2 in FIG. 8 ) are established, wherein different header compression contexts have different context identifiers.
  • the header compression context saved by UE3 comes from the source access network device, and The target access network device and the source access network device independently generate the header compression context, so UE3 cannot decompress the MBS header compressed data packet sent by the access network device 2 normally. Based on this, for an MBS service
  • the access network device that performs header compression when the terminal device is switched over, the access network device (ie, the target access network device) can reset the existing header compression context, and re-establish the context for all UEs. As shown in FIG. 8, when the target access network device determines that a terminal device (UE3 as shown in FIG.
  • the terminal device can correctly decompress the MBS data packet, and the target access network device can reset, refresh, or delete the established header compression context (context1-context3 shown in line 2 in Figure 8), That is, no longer use, or stop using the header compression context that has been established before, but re-establish the header compression context (context1-context3 shown in line 3 in Figure 8), that is, download all terminal devices to the target access network device Send the first information, so that all terminal devices update the context to context1-context3 shown in line 3 in Figure 8 (as shown in Figure 8, UE3 updates context1-context3 shown in line 1 to context1-context3 shown in line 3 context3, UE4 and UE5 use context1 ⁇ context3 shown in line 2 (context1 ⁇ context3 shown in line 3), and ensure that all terminal devices have established a header compression context that is synchronized with the access network device, and then
  • the target access network device may also send the data packet after the header is compressed by the first header compression context before determining that the first terminal device has established the first header compression context, that is, the header compressed data packet, for example, the target The access network device may send the data packet with the header compressed to the first terminal device through the PTM transmission mode and/or the PTP transmission mode.
  • the first terminal device can save the header compressed data packet first, and then compress the corresponding header after the corresponding header compression context is established. Packets are decompressed.
  • the first terminal device may determine whether the corresponding header compression context has been established through the context identifier included in the received compressed data packet.
  • the first terminal device first saves the header compressed data packet, waits for the corresponding header compression context to be established, and then compresses the corresponding header data packet
  • the decompression may be as follows: after the first terminal device receives the header compression data packet, the first terminal device judges whether the header compression context identifier included in the header compression data packet exists in the available header compression context information, wherein the available The header compression context is the header compression context information that can be used to compress or decompress the header of the data packet.
  • the header compressed data packet is decompressed according to the first header compression context corresponding to the header compression context identifier. Understandably, when the context corresponding to the header compression data packet received by the terminal device has not been established, the terminal device needs to save the compressed data packet first, and then compress the corresponding header data packet after the corresponding header compression context is established.
  • the description of performing decompression may be taken as an embodiment alone, or may be combined with one or more steps in the embodiments of the present application as an optional step, which is not limited here.
  • the sequence number of the data packet received by the terminal device is the same as the sequence number of the previously received data packet or satisfies a certain deviation or satisfies a certain association relationship, it cannot simply However, it is necessary to further determine whether the headers of two data packets with the same sequence number have been compressed.
  • the terminal device in the embodiment of the present application needs to further consider whether the header of the data packet has been compressed when the terminal device receives multiple data packets that include the same serial number or the serial number meets a certain deviation or the serial number satisfies a certain relationship.
  • the sequence number of the data packet can be the sequence number of the PDCP layer, for example, the sequence number of the PDCP layer can be a PDCP sequence number (PDCP sequence number, PDCP SN), etc., or the sequence number can also be the sequence number of the SDAP layer ,
  • the serial number of SDAP layer can be SDAP SN etc., perhaps serial number also can be the serial number of RLC layer, or MAC layer, or PHY layer etc., do not limit here.
  • the embodiments of the present application all take the sequence number of the data packet as the PDCP SN number as an example for schematic illustration.
  • the terminal device judges whether the headers of the two data packets are compressed. If one of the headers is compressed and the other is not, the compressed data packet is discarded, or described as or reserved Uncompressed packets, or described as discarding compressed packets and keeping uncompressed packets; packets received after dropping if both compressed or neither are compressed, or described as keeping The packet received first, or the packet received after being described as discarded and the packet received first kept.
  • the terminal device judges from which transmission path the two data packets are received, and if one of them is received from PTM and the other is received from PTP, the terminal device discards the data packet received from PTM ; If both are received from PTM or PTP, discard the received data packets, etc., and there is no limitation here. It can be understood that the above description of the duplicate detection function of the terminal device may be used alone as an embodiment, or may be combined with one or more steps in the embodiments of the present application as an optional step, which is not limited here.
  • step of discarding in this application can also be an optional step, that is, the terminal device can keep the uncompressed data packet or the data packet received first, or the terminal device skips (skip) and uses the compressed The data packet or the data packet received later, the uncompressed data packet or the data packet received first, etc. are directly used, and there is no limitation here.
  • the execution sequence or timing relationship of the above steps S701 to S703 can be S701 ⁇ S702 ⁇ S703 (that is, first turn off the compression function, and then send the first information), or it can also be S701 ⁇ S703 ⁇ S702 (that is, first send The first information, and then turn off the compression function), or, it can also be S701 ⁇ S703/S702 (that is, the parallel execution of the closing of the compression function described in the step S703 and the sending of the first information described in the step S702), etc., will not be repeated here. List them all. In short, the above numbering of each step does not limit the execution sequence of the solution.
  • the target access network device resets, refreshes or deletes the established header compression context before, during or after the handover of the terminal device, that is, stops using the context created before the handover , and the method of re-establishing the header compression context can realize the synchronization of the header compression context between the terminal device and the target access network device after handover, and then can correctly decompress the header compressed data packet received from the target access network device , which is conducive to improving the reliability of communication.
  • FIG. 9 is another schematic flowchart of a communication method provided by an embodiment of the present application.
  • the method includes the following steps S901 to S904, wherein the method execution body shown in FIG. 9 may be a target access network device, or the method execution body shown in FIG. 9 may also be a target access network device.
  • the chip in the network device, etc., is not limited here.
  • the target access network device will be used as an example for description below.
  • the target access network device determines that the first terminal device switches from the source access network device to the target access network device.
  • step S901 in this embodiment of the present application reference may be made to the description of step S501 in Embodiment 1 corresponding to FIG. 5 , and details are not repeated here.
  • the target access network device suspends using the first header compression context to compress the header of the data packet.
  • the target access network device may suspend (suspend) or suspend the first header compression context to compress the header of the data packet.
  • the first packet header compression context should be understood as the first terminal device used when the target access network device compresses the header of the data packet before the first terminal device switches from the source access network device to the target access network device. Header compression context.
  • the above “suspension of use” can be understood as skipping use, temporarily not using, not continuing to use, disabling, deactivating, or understanding that the target access network device will
  • the state of the packet header compression context is set to an unavailable state or an invalid state, etc., which is not limited in this application. Understandably, in addition to the above-mentioned disabling, or setting the context state invalid, or setting the context state cannot be used to suspend the use of the established packet header compression context in the target access network device, in the specific context of the access network device In implementation, it may also appear in other forms, for example, the access network device may also mark whether the corresponding packet header compression context is available in the form of a mark, an identifier or a label. For example, when a certain context can be used for header compression, mark the available context; or, when a certain context cannot be used for header compression, mark the unusable context, etc., depending on the actual application scenario OK, no limit here.
  • the target access network device sends the first information to the first terminal device.
  • the target access network device may send the first terminal device the first a message.
  • the first information may be sent to the first terminal device when the first terminal device is about to switch from the source access network device to the target access network device, or , the first terminal device sends the first information to the first terminal device during the handover process from the source access network device to the target access network device, or, when the first terminal device successfully switches from the source access network device to the target After accessing the network device, the first information is sent to the first terminal device.
  • the transmission mode of the first information may be transmitted by using a PTM transmission mode, or may also be transmitted by using a PTP transmission mode, etc., which is not limited here.
  • the target access network device sends the first information through the PTP transmission mode
  • all terminal devices under the target access network device that is, the first terminal device and others that have previously received the MBS service under the target access network device All terminal devices can receive the first information.
  • the target access network device sends the first information to the first terminal device through the PTP transmission mode, only the first terminal device can receive the first information.
  • the terminal equipment receiving the MBS service under the target access network equipment cannot receive or obtain the first information.
  • the first information is used to indicate the first header compression context
  • the first header compression context is used to compress or decompress the header of the data packet.
  • the data packets involved in this application may be data packets of the MBS service, or may also be data packets of other services (such as unicast service, or broadcast service, or multicast service, etc.), specifically determined according to actual application scenarios, There is no limitation here.
  • the embodiments of the present application all take the data packet of the MBS service as an example for schematic description.
  • the MBS service may be a live broadcast service, a public safety service, a batch software update service, etc., which are not limited here.
  • the first packet header compression context should be understood as the first terminal device used when the target access network device compresses the header of the data packet before the first terminal device switches from the source access network device to the target access network device. Header compression context.
  • the target access network device sends the first information to the first terminal device before, during, or after the handover of the first terminal device.
  • the information can be understood as: the target access network device carries or bears the compression context of the first header in the uncompressed data packet of the header, and sends it to the first access network device, or it can also be understood as being used to indicate
  • the first information of the first header compression context is carried in the header uncompressed data packet, and sent to the first terminal device.
  • the first header compression context may also be carried in the signaling, that is, the first information used to indicate the first header compression context may be carried in the signaling and sent to the first terminal device.
  • the signaling involved may be media access control element (MAC control element, MAC CE), or radio resource control (radio resource control, RRC) signaling, or packet data convergence layer protocol control protocol data unit (PDCP control protocol data unit, PDCP control PDU), etc., there is no limitation here.
  • MAC control element media access control element
  • RRC radio resource control
  • PDCP control protocol data unit packet data convergence layer protocol control protocol data unit
  • the target access network device determines that the first terminal device establishes a first packet header compression context, and resumes using the first packet header compression context to compress or decompress the packet header of the data packet.
  • the target access network device determines that the first terminal device has established or successfully established a certain header compression context may be as follows: 1 When the target access network device continuously sends the same header compression context N times, it can default or determine the first The terminal device successfully establishes the header compression context, or, (2) the target access network device may determine that the first terminal device successfully establishes the header compression context when receiving feedback information about the compression context from the first terminal device, The feedback information includes the context identifier, indicating that the header compression context corresponding to the context identifier is established.
  • the target access network device may Send the data packet with uncompressed header until the target access network device determines that the first terminal device establishes the first header compression context, and then resumes using the first header compression context to compress the header of the data packet.
  • the above recovery using the first header compression context to compress the header of the data packet may be as follows: when the target access network device determines that the first terminal device has established a certain header compression context, for example, take header compression context 1 as an example for illustration , the target access network device can set the state of the header compression context 1 to an available state, an effective state, or re-enable the header compression context 1, and start to perform header compression on the header of the data packet corresponding to the header compression context 1.
  • the target access network device can perform header compression on data packets corresponding to all contexts, so as to send the packet header through Compressed packets.
  • the process of compressing the data packet corresponding to the established packet header compression context can be separately regarded as a embodiment, or as an optional step combined with one or more steps in the embodiment of the present application, which is not limited here.
  • the target access network device will first suspend the use of the first packet header compression context to compress the data packet, and then send the first information to the first terminal device, and determine the first After the terminal device establishes the corresponding first packet header compression context according to the first information, it resumes using the first packet header compression context to compress the header of the data packet.
  • the switching of the first terminal device will cause Make the target access network device that is transmitting the MBS data packet in the compressed mode switch to temporarily not use the compressed mode to transmit the MBS data packet, that is, the sent MBS data packet changes from the compressed data packet of the header to the uncompressed data of the header. Then, when the target access network device determines that the first packet header compression context is established in the first terminal device, it resumes using the first packet header compression context to compress the corresponding packet header, that is, the sent MBS data packet does not pass through the packet header. The compressed data packet becomes the data packet whose header is compressed.
  • the target access network device does not need to re-establish the header compression context, and the first header compression context is still the first header compression context.
  • a header compression context established before a terminal device switches. That is to say, from the perspective of air interface transmission, the first packet header compression context is the same as the header compression context used by the first terminal device before switching, that is, the context information corresponding to the same context identifier is the same.
  • the compression context used is the same as that before the first terminal device switches The compression context used is the same.
  • terminal devices other than the first terminal device that is, terminal devices that receive MBS data packets under the target access network device before the first terminal device switches, since the first packet header compression context and The header compression context established before the handover by the first terminal device is the same, so no matter whether the target access network device uses PTM or PTP transmission mode to send the first information, the other terminal device does not need to update the established before handover according to the first information. header compression context, but can continue to use the header compression context established before the switch.
  • the other terminal device also The operation of updating the header compression context established before the switch according to the first information can be performed, but since in this embodiment the use of the header compression context used by the first terminal device before the switch is suspended (not stopped), these terminal devices Even if an update operation is done, the corresponding header compression context will not be changed.
  • only one terminal device (such as terminal device 3) switches to the target access network device in a certain period of time, it is assumed that after the terminal device 3 switches to the target access network device, there is no After all the header compression context states of the target access network device become available, effective or enabled, it is switched to other access network devices. At this time, in order to save the context establishment cost, the context state needs to be unavailable, invalid or A disabled header compression context returns to available, enabled or enabled. This is because except for terminal device 3, other terminal devices have established contexts before, and now terminal device 3 is switched away, so it should be restored to its original state.
  • FIG. 10 is a schematic diagram of a scenario in which a handover affects a header compression context state in a target access network device according to an embodiment of the present application.
  • the target access network device and each terminal device under the target access network device have established a mutually synchronized header compression context (context1-context3 as shown in Figure 10), so , the target access network device may use context1-context3 to compress the data packets to be transmitted.
  • terminal device 3 shown in Figure 10 there is a certain terminal device that is successfully handed over from the source access network device to the target access network device.
  • the packet header compression already established in the target access network device The contexts (ie, context1-context3) all change from the available state to the unavailable state. Therefore, the target access network device can only send data packets with uncompressed headers (ie send all data packets with full headers). Further, the target access network device sends the header compression context to the terminal device 3, and when it is determined that the terminal device 3 has established or successfully established any context, the corresponding header compression context state in the target access network device is set as available , take effect or enable, and start to compress the header of the data packet corresponding to the header compression context.
  • the terminal device 3 has successfully established context1 at time t2, therefore, the target access network device can perform compression on the data packet corresponding to context1, and the context that has not been created or has not been established for the terminal device 3 (as shown in Figure 10 shown context2 and context3), the target access network device does not perform compression on the data packets corresponding to context2 and context3, that is, sends uncompressed data packets.
  • the terminal device 3 is switched from the target access network device to other access network devices (that is, the terminal device 3 is switched away from the target access network device), at this time, the target access network device needs to switch the target access network device
  • the context in the unavailable state is set or restored to the available state, that is, after the time t2, restore context2 and context3 from the unavailable state to the available state, and use context1 ⁇ context3 to compress the data packets that need to be transmitted.
  • the target access network device suspends or suspends or disables the packet header compression context established in the target access network device until the target access network device determines that the first terminal device successfully establishes any When using the first packet header compression context, and then restore the scheme of using the first packet header compression context to compress the header of the data packet, for a certain period of time, there are multiple terminal devices switching to the target access network device.
  • the target access network device needs to adjust the header compression context state according to the switching situation of multiple terminal devices. For example, suppose there are two terminal devices switching to the target access network device. Let’s take an example as an example for illustration. The target access network device needs to confirm that the two terminal devices have established the header compression context before setting the corresponding header compression context state to available, effective or enabled.
  • terminal device 1 of the two terminal devices When the target access network device still has an unavailable, invalid or disabled header compression context, but terminal device 1 of the two terminal devices is switched away from the target access network device, then those still cannot be restored Unavailable, disabled or disabled header compression contexts because the end device 2 has not successfully established these header compression contexts. For example, assuming that terminal device 1 switches to make context 1-3 unavailable, and then terminal device 2 also switches in, at this time even if terminal device 1 switches away, because the context of terminal device 2 has not been established yet, context 1-3 Status remains unavailable.
  • the target access network device may also send the data packet after the header is compressed by the first header compression context before determining that the first terminal device has established the first header compression context, that is, the header compressed data packet, based on this , when the context corresponding to the header compressed data packet received by the terminal device has not been established, the terminal device needs to save the compressed data packet first, and then decompress the corresponding header compressed data packet after the corresponding header compression context is established.
  • the above numbering of each step does not limit the execution sequence of the scheme.
  • the target access network device before, during, or after the handover of the terminal device, changes the header compression context state accordingly (that is, suspends the use first, then resumes the use), and according to the context state (that is, suspend use state, and resume use state) to determine whether to perform header compression on the corresponding data packet, which can realize the synchronization of the header compression context between the terminal device and the target access network device after switching, and then be able to receive data packets from the target access network
  • the correct decompression of the header compressed data packets of the network access equipment is conducive to improving the reliability of communication.
  • FIG. 11 is another schematic flowchart of the communication method provided by the embodiment of the present application.
  • the method includes the following steps S1101 to S1102, wherein the method execution body shown in FIG. 11 may be a target access network device, or the method execution body shown in FIG. 11 may also be a target access network device.
  • the chip in the network device, etc., is not limited here.
  • the target access network device will be used as an example for description below.
  • the target access network device determines that the first terminal device switches from the source access network device to the target access network device.
  • step S1101 in this embodiment of the present application reference may be made to the description of step S501 in Embodiment 1 corresponding to FIG. 5 , and details are not repeated here.
  • the target access network device sends the first information to the first terminal device in a point-to-point PTP transmission manner.
  • the target access network device can configure a radio bearer for the terminal device, and the radio bearer includes two There are two transmission paths, one is PTP transmission path and the other is PTM transmission path. That is to say, the transmission includes two transmission paths, one is the PTP transmission path, and the other is the PTM transmission path, where PTP only transmits data for this terminal device, and PTM transmits data for multiple terminal devices including this terminal device .
  • the target access network device can send data packets through one of the transmission paths (such as PTP or PTM), or simultaneously send data packets through two transmission paths (that is, PTP and PTM), and switch to
  • the first terminal device of the target access network device can receive the data packet through one of the transmission paths (such as PTP or PTM), or simultaneously receive the data packet through two transmission paths (ie, PTP and PTM).
  • the data packet sent through PTM is a data packet with a compressed header (that is, a compressed data packet). Therefore, the multiple terminal devices under the target access network device include the switched first terminal device and Other terminal devices originally receiving services under the target access network device can receive these data packets with headers compressed.
  • the multiple terminal devices are terminal devices receiving the same broadcast multicast service.
  • a transmission path when the transmission path is PTM is used to send the first information
  • the target access network device can send the first information to the first terminal device through point-to-point PTP transmission mode, In this case, only the first terminal device can receive the first information, and other terminal devices that have previously received the MBS service under the target access network device cannot receive the first information.
  • the first information is used to indicate the first header compression context
  • the first header compression context is used to compress or decompress the header of the data packet.
  • the data packets involved in this application may be data packets of the MBS service, or may also be data packets of other services (such as unicast service, or broadcast service, or multicast service, etc.), specifically determined according to actual application scenarios, There is no limitation here.
  • the embodiments of the present application all take the data packet of the MBS service as an example for schematic description.
  • the MBS service may be a live broadcast service, a public safety service, a batch software update service, etc., which are not limited here.
  • the first packet header compression context should be understood as the first terminal device used when the target access network device compresses the header of the data packet before the first terminal device switches from the source access network device to the target access network device. Header compression context.
  • the first terminal device may establish the first packet header compression context according to the first information. Understandably, if the source access network device itself has enabled the compression function, the first terminal device may establish the first packet header compression context according to the first information: The packet header compression context of is updated to the first packet header compression context.
  • the header compression context established by the first terminal device may be the header compression context that the first terminal device synchronizes with the source access network device when receiving the MBS service under the source access network device.
  • the first terminal device can delete the header compression context established when the first terminal device receives the MBS service under the source access network device, and then establish the first packet header according to the first information received from the target access network device Compression context. If the source access network device itself does not enable the compression function, the first terminal device does not establish a header compression context associated with the MBS service when receiving the MBS service under the source access network device. Therefore, the first terminal device Establishing the first packet header compression context according to the first information may be: the first terminal device newly establishes the first packet header compression context in the first terminal device according to the first information.
  • the target access network device can send data packets to the terminal device through the PTP and PTM transmission paths at the same time
  • the target access network device can send the first information to the first terminal device through the PTP transmission mode, and at the same time, through
  • the PTM or PTP transmission method sends the data packet after the header is compressed by the first header compression context (that is, the header compressed data packet).
  • the first information, and the header compressed data packet is sent through the PTM transmission mode.
  • the terminal device may perform in parallel to receive the first information and header compressed data packets respectively in the PTP and PTM transmission manners.
  • the target access network device may send the first information to the first terminal device through the PTP transmission method, and then send the compressed header data packet to the first terminal device through the PTP transmission method, or the target access network device may also send the first information to the first terminal device through the PTP transmission method. It is possible to first send the data packet with a compressed header to the first terminal device through the PTP transmission mode, and then send the first information to the first terminal device through the PTP transmission mode, which is not limited here.
  • the advantage of this is that it can ensure that the progress of the first terminal device receiving header compressed data packets through the PTP transmission mode is not slower than the progress of other terminal devices receiving data packets through the PTM transmission mode.
  • the network access device receives data packets of the MBS service.
  • the target access network device determines that the first terminal device has established the same header compression context as the target access network device, that is, the target access network device determines that the header compression context in the first terminal device is the same as the target
  • the target access network device can switch the PTP transmission mode of the first terminal device to PTM transmission through MAC CE or RRC signaling, so that the first device terminal can communicate with other terminals Like the device, it receives compressed data packets through PTM transmission.
  • the target access network device can send data packets to the terminal device through the PTP and PTM transmission paths at the same time, or in the scenario where the target access network device can only send data packets to the terminal device through the PTP transmission path , it is possible that when the first terminal device receives the header compressed data packet, the first header compression context corresponding to the context identifier carried in the header compressed data packet has not been established, that is, the first terminal device and the target access network The existence of the first header compression context between devices is not synchronized. Therefore, for the first terminal device that has not established the first packet header compression context, the first terminal device first saves the header compressed data packet, and then decodes the corresponding header compressed data packet after the corresponding header compression context is established. compression.
  • the first terminal device judges the available header compression context information (that is, the first terminal device creates based on the first information from the target access network device Header compression context), whether there is a header compression context identifier included in the header compression data packet, wherein the available header compression context is the header compression context information that can be used to compress or decompress the header of the data packet.
  • the available header compression context is the header compression context information that can be used to compress or decompress the header of the data packet.
  • the terminal device needs to save the compressed data packet first, and then compress the corresponding header data packet after the corresponding header compression context is established.
  • the description of performing decompression may be taken as an embodiment alone, or may be combined with one or more steps in the embodiments of the present application as an optional step, which is not limited here.
  • FIG. 12 is a schematic diagram of a scenario in which a data packet is sent through a PTP and a PTM transmission path at the same time provided by this embodiment.
  • the target access network device can send the first information to the terminal device (UE1 shown in FIG. 12 ) switching to the target access network device through PTP transmission mode, or described as sending
  • the first packet header compresses the context, and at the same time sends a compressed header packet to UE1 through PTM transmission (or described as sending a compressed header header packet to all terminal devices including UE1 through PTM transmission, wherein all terminal devices include UE1 and Other terminal devices that have received the MBS service under the target access network device before).
  • UE1 needs to save the header compressed data packet first, and then decompress the corresponding header compressed data packet after the corresponding header compression context is established.
  • UE1 may determine whether the corresponding header compression context has been established through the context identifier included in the received compressed data packet.
  • this embodiment is aimed at the duplicate detection function of the terminal device.
  • the sequence number of the data packet received by the terminal device is the same as the sequence number of the previously received data packet or satisfies a certain deviation or satisfies a certain association relationship, It is not possible to simply discard the data packets received later, but it is necessary to further determine whether the headers of two data packets with the same sequence number have been compressed.
  • the terminal device in the embodiment of the present application needs to further consider whether the packet header of the data packet has been compressed or further consider whether the data packet from which path it was received.
  • the sequence number of data packet can be the sequence number of PDCP layer, for example, the sequence number of PDCP layer can be PDCP sequence number (PDCP sequence number, PDCP SN) etc., perhaps, sequence number also can be the sequence number of SDAP layer,
  • the serial number of the SDAP layer can be the SDAP SN, etc., or the serial number can also be the serial number of the RLC layer or the MAC layer or the PHY layer, etc., which is not limited here.
  • the embodiments of the present application all take the sequence number of the data packet as the PDCP SN number as an example for schematic illustration.
  • the terminal device since the PDCP SN in the header compressed data packet is the same as the PDCP SN in the full header data packet (that is, the PDCP SNs are both equal to 10), the terminal device needs to perform repeated detection.
  • the terminal device judges whether the headers of the two data packets are compressed. If one of the headers is compressed and the other is not, the compressed data packet is discarded, or described as or reserved Uncompressed packets, or described as discarding compressed packets and keeping uncompressed packets; packets received after dropping if both compressed or neither are compressed, or described as keeping The packet received first, or the packet received after being described as discarded and the packet received first kept.
  • the terminal device judges from which transmission path the two data packets are received, and if one of them is received from PTM and the other is received from PTP, the terminal device discards the data packet received from PTM ; If both are received from PTM or PTP, discard the received data packets, etc., and there is no limitation here.
  • the above description of the duplicate detection function of the terminal device may be used alone as an embodiment, or may be combined with one or more steps in the embodiments of the present application as an optional step, which is not limited here.
  • the step of discarding in this application can also be an optional step, that is, the terminal device can keep the uncompressed data packet or the data packet received first, or the terminal device can skip (skip) use the compressed The data packet or the data packet received later, the uncompressed data packet or the data packet received first, etc. are directly used, and there is no limitation here.
  • the first header compression context in the embodiment of the present application may be carried or borne in an uncompressed data packet at the header and sent to the first access network device, or it may also be understood as Carrying the first information for indicating the compression context of the first header in the header uncompressed data packet, to be sent to the first terminal device.
  • the first header compression context may also be carried in signaling (or the first information described as indicating the first header compression context may be carried in signaling), for example, the signaling involved may be MAC CE, or RRC signaling, or PDCP control PDU, etc., are not limited here.
  • the header uncompressed data packet (or signaling) used to carry the first information may also include a header compression context identifier corresponding to each header compression context (for convenience of description, it may also be referred to simply as a context identifier ) and other information are not limited here.
  • a header compression context corresponds to one context identifier. Therefore, after the first terminal device receives a data packet or signaling with an uncompressed header, the first terminal device can save the correspondence between the first header compression context and the corresponding context identifier, so that it can subsequently receive data with a compressed header When packing, according to the context identifier carried in the header compressed data packet, determine the corresponding first header compression context to decompress the header compressed data packet.
  • the target access network device can help the terminal device establish a header compression context through PTP transmission before, during or after the handover of the terminal device.
  • the received first information establishes a first packet header compression context, so that the received header compressed data packet can be correctly decompressed, which is beneficial to improving the reliability of communication.
  • the communication device provided by the present application will be described in detail below with reference to FIGS. 13 to 16 .
  • FIG. 13 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device shown in FIG. 13 may be used to execute part or all of the functions of the target access network device in the method embodiments described above in FIG. 5 to FIG. 12 .
  • the device may be a target access network device, or a device in the target access network device, or a device that can be matched and used with the target access network device.
  • the communication device may also be a system on a chip.
  • the communication device shown in FIG. 13 may include a transceiver unit 1301 and a processing unit 1302 .
  • the processing unit 1302 is configured to perform data processing.
  • the transceiver unit 1301 is integrated with a receiving unit and a sending unit.
  • the transceiver unit 1301 may also be called a communication unit.
  • the transceiver unit 1301 may also be split into a receiving unit and a sending unit.
  • the processing unit 1302 below is the same as the transceiver unit 1301 , and details will not be repeated below. in:
  • the processing unit 1302 is configured to determine that the first terminal device is handed over from the source access network device to the target access network device;
  • a transceiver unit 1301, configured to send first information to the first terminal device, where the first information is used to indicate a first header compression context, and the first header compression context is used to compress or decompress headers of data packets compression.
  • FIG. 14 shows a schematic structural diagram of a communication device according to an embodiment of the present application.
  • the communication apparatus shown in FIG. 14 may be used to perform some or all functions of the terminal device (or described as the first terminal device) in the method embodiments described above in FIGS. 5 to 12 .
  • the device may be a terminal device, or a device in the terminal device, or a device that can be matched with the terminal device.
  • the communication device may also be a system on a chip.
  • the communication device shown in FIG. 14 may include a transceiver unit 1401 and a processing unit 1402 . in:
  • the processing unit 1402 is configured to switch from the source access network device to the target access network device;
  • the transceiver unit 1401 is configured to receive first information from the target access network device, where the first information is used to indicate a first header compression context, and the first header compression context is used to compress headers of data packets or unzip.
  • FIG. 15 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • the communication device may be the target access network device described in the embodiment of this application, and is used to implement the functions of the target access network device in Figures 5 to 12 above.
  • the target access network device 15 includes: a baseband device 151 , a radio frequency device 152 , and an antenna 153 .
  • the radio frequency device 152 receives the information sent by the terminal device through the antenna 153, and sends the information sent by the terminal device to the baseband device 151 for processing.
  • the baseband device 151 processes the information of the terminal device and sends it to the radio frequency device 152
  • the radio frequency device 152 processes the information of the terminal device and sends it to the terminal device through the antenna 151 .
  • the baseband device 151 includes one or more processing units 1511 , a storage unit 1512 and an interface 1513 .
  • the processing unit 1511 is configured to support the target access network device to execute the functions of the target access network device in the foregoing method embodiments.
  • the storage unit 1512 is used to store software programs and/or data.
  • the interface 1513 is used for exchanging information with the radio frequency device 152, and the interface includes an interface circuit for inputting and outputting information.
  • the processing unit is an integrated circuit, such as one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.
  • the storage unit 1512 and the processing unit 1511 may be located in the same chip, that is, an on-chip storage element. Alternatively, the storage unit 1512 and the processing unit 1511 may also be located on different chips from the processing unit 1511 , that is, an off-chip storage element.
  • the storage unit 1512 may be one memory, or a general term for multiple memories or storage elements.
  • the target access network device may implement part or all of the steps in the foregoing method embodiments in the form of one or more processing unit schedulers.
  • the one or more processing units may support wireless access technologies of the same standard, or may support wireless access technologies of different standards.
  • FIG. 16 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • the communication device may be the terminal device described in the embodiments of the present application, and is used to realize the functions of the terminal device in FIGS. 5 to 12 above.
  • FIG. 16 only shows main components of a terminal device 1600 .
  • a terminal device 1600 includes a processor, a memory, a control circuit, an antenna, and an input and output device.
  • the processor is mainly used to process communication protocols and communication data, control the entire terminal device 1600, execute software programs, and process data of the software programs.
  • Memory is primarily used to store software programs and data.
  • the control circuit is mainly used for conversion of baseband signal and radio frequency signal and processing of radio frequency signal.
  • Antennas are mainly used to send and receive radio frequency signals in the form of electromagnetic waves.
  • Input and output devices such as touch screens, display screens, microphones, keyboards, etc., are mainly used to receive data input by users and output data to users.
  • the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program.
  • the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the control circuit, and the control circuit performs radio frequency processing on the baseband signal, and sends the radio frequency signal through the antenna in the form of electromagnetic waves.
  • the control circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data .
  • FIG. 16 only shows a memory and a processor.
  • terminal device 1600 may include multiple processors and memories.
  • a storage may also be called a storage medium or a storage device, which is not limited in this embodiment of the present invention.
  • the processor may include a baseband processor and a central processing unit, the baseband processor is mainly used to process communication protocols and communication data, and the central processor is mainly used to control the entire terminal device 1600, Executing the software program, processing the data of the software program.
  • the processor in FIG. 16 integrates the functions of the baseband processor and the central processing unit.
  • the baseband processor and the central processing unit can also be independent processors, interconnected through technologies such as a bus.
  • the terminal device 1600 may include multiple baseband processors to adapt to different network standards, the terminal device 1600 may include multiple central processors to enhance its processing capability, and various components of the terminal device 1600 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 may also be expressed as a central processing circuit or a central processing chip.
  • the function of processing the communication protocol and communication data can be built in the processor, or can be stored in the storage unit in the form of a software program, and the processor executes the software program to realize the baseband processing function.
  • the antenna and the control circuit with the transceiver function may be regarded as the transceiver unit 1610 of the terminal device 1600
  • the processor with the processing function may be regarded as the processing unit 1620 of the terminal device 1600
  • a terminal device 1600 includes a transceiver unit 1610 and a processing unit 1620 .
  • the transceiver unit may also be referred to as a transceiver, a transceiver, a transceiver device, and the like.
  • the device in the transceiver unit 1610 for realizing the receiving function may be regarded as a receiving unit
  • the device in the transceiver unit 1610 for realizing the sending function may be regarded as a sending unit, that is, the transceiver unit 1610 includes a receiving unit and a sending unit.
  • the receiving unit may also be called a receiver, receiver, receiving circuit, etc.
  • the sending unit may be called a transmitter, transmitter, or transmitting circuit, etc.
  • the embodiment of the present application also provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instruction is run on a processor, the method flow of the above-mentioned method embodiment is realized.
  • the embodiment of the present application further provides a computer program product.
  • the computer program product is run on a processor, the method flow of the above method embodiment is implemented.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division.
  • the units described as separate components may or may not be physically separated.
  • the components shown may or may not be physical units, that is, they may be located in one place, or they may be distributed over multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned computer-readable storage medium may be any available medium that can be accessed by a computer.
  • the computer readable medium may include random access memory (random access memory, RAM), read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), Erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically erasable programmable read only memory, EEPROM), compact disc read-only memory (compact disc read-only memory, CD- ROM), universal serial bus flash disk (universal serial bus flash disk), removable hard disk, or other optical disk storage, magnetic disk storage medium, or other magnetic storage device, or can be used to carry or store desired data in the form of instructions or data structures program code and any other medium that can be accessed by a computer.
  • RAM random access memory
  • read-only memory read-only memory
  • ROM programmable read-only memory
  • PROM programmable read-only memory
  • Erasable programmable read-only memory Erasable programmable read-only memory
  • EPROM Er
  • RAM static random access memory
  • dynamic RAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • enhanced SDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory
  • direct rambus RAM direct rambus RAM

Landscapes

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

Abstract

本申请提供了一种通信方法及通信装置，该方法包括：目标接入网设备确定第一终端设备从源接入网设备切换至目标接入网设备；向第一终端设备发送第一信息，第一信息用于指示第一包头压缩上下文，第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。在本申请中，目标接入网设备通过向第一终端设备发送用于指示第一包头压缩上下文的第一信息，使得在切换场景下，第一终端设备可以对后续接收到的包头经过压缩的数据包进行正确的解压缩，有利于提高通信的可靠性。

Description

通信方法及通信装置
本申请要求于2021年08月05日提交中国专利局、申请号为202110898747.3，发明名称为“通信方法及通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及通信装置。
背景技术
多播广播业务(multicast and broadcast service，MBS)是面向多个终端设备(user equipment，UE)的业务，例如直播业务、公共安全业务、批量软件更新业务等。MBS数据来自数据服务器，首先数据服务器将MBS数据发送给核心网设备，然后核心网设备将MBS数据发送给接入网设备，最后接入网设备将MBS数据发送给接收MBS业务的至少一个UE。从核心网向接入网设备发送的时候，MBS业务通过一个公共的传输通道MBS会话进行传输，而从接入网设备向UE发送的时候，有两种传输方式：第一种可以采用点到多点(point to multi-point，PTM)传输方式；第二种可以采用点到点(point to point，PTP)传输方式。
通常而言，进行无线通信的终端设备由于位置发生移动，经常需要从一个接入网设备(即源接入网设备)切换到另一个接入网设备(即目标接入网设备)继续进行无线通信。对于MBS业务来说，源接入网设备和目标接入网设备独立进行发送，对于某些MBS业务，例如语音业务，为了节省传输开销，接入网设备会开启对MBS数据包的头压缩功能，且两个接入网设备(即源接入网设备和目标接入网设备)独立进行头压缩。而对于接收MBS业务的终端设备来说，从源接入网设备切换到目标接入网设备的时候，由于两个接入网设备建立头压缩上下文的过程相互独立，所以在源接入网设备建立好的压缩上下文无法用于对目标接入网设备传输的数据包进行包头解压缩，基于此，如何保证终端设备在切换后，与目标接入网设备间的正常通信成为亟待解决的问题之一。
发明内容
本申请提供了一种通信方法及通信装置，可保证终端设备在切换后，与目标接入网设备间的正常通信，提高了通信的可靠性。
第一方面，本申请提供了一种通信方法，该方法可适用于目标接入网设备。该方法包括：确定第一终端设备从源接入网设备切换至目标接入网设备；向所述第一终端设备发送第一信息，所述第一信息用于指示第一包头压缩上下文，所述第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。
在本申请中，当终端设备(例如，以第一终端设备为例进行示意性说明)由于位置移动，从源接入网设备切换至目标接入网设备时，目标接入网设备可通过向第一终端设备发送第一信息，以使得第一终端设备可以根据接收到的第一信息建立第一包头压缩上下文，进而保持第一终端设备和目标接入网设备的包头压缩上下文同步，保证第一终端设备切换到目标接入网设备以后，能够对包头经过压缩的数据包进行正常的解压缩，提高了通信的可靠性。其中， 第一终端设备从源接入网设备切换至目标接入网设备，可以为第一终端设备从源接入网设备切换到目标接入网设备过程中，或者，第一终端设备从源接入网设备切换到目标接入网设备后。也就是说，目标接入网设备可在第一终端设备从源接入网设备切换到目标接入网设备过程中，向第一终端设备发送第一信息，或者，在第一终端设备从源接入网设备切换到目标接入网设备后，向第一终端设备发送第一信息，在此不做限制。其中，本申请中所涉及的数据包可以为MBS业务的数据包(示例性地，数据包可以为包头未经压缩的数据包，或包头经过压缩的数据包)等，在此不做限制。其中，本申请中涉及的数据包可以是与MBS业务关联的数据包。
在一种可能的实现中，所述方法还包括：
停止使用所述第一终端设备从所述源接入网设备切换至所述目标接入网设备之前，所述目标接入网设备对数据包的包头进行压缩或解压缩时所使用的头压缩上下文；
建立所述第一包头压缩上下文。
在本申请中，第一终端设备切换过来后，目标接入网设备向所述第一终端设备发送第一信息之前，目标接入网设备可停止使用目标接入网设备中已建立好的包头压缩上下文(或理解为删除，或重置，或刷新，或跳过使用，或不使用，或不再使用目标接入网设备中已建立好的包头压缩上下文)，即目标接入网设备不再发送基于之前(即第一终端设备切换过来之前)已创建好的包头压缩上下文进行包头压缩处理后的数据包，而是在需要发送数据包，发送包头未经压缩的数据包。进一步地，目标接入网设备建立(或描述为重新建立)新的包头压缩上下文(即第一包头压缩上下文)，并向第一终端设备发送第一包头压缩上下文，即目标接入网设备重新开始包头压缩上下文的建立过程，并在确定第一终端设备与目标接入网设备间第一包头压缩上下文同步后，再发送基于第一包头压缩上下文进行头压缩处理后的数据包。整个流程操作简便，适用性高。
在一种可能的实现中，所述方法还包括：
暂停使用所述第一包头压缩上下文对数据包的包头进行压缩，所述第一包头压缩上下文为所述第一终端设备从所述源接入网设备切换至所述目标接入网设备之前，所述目标接入网设备对数据包的包头进行压缩或解压缩时所使用的头压缩上下文。
在本申请中，第一终端设备切换过来后，目标接入网设备向所述第一终端设备发送第一信息之前，目标接入网设备可暂停使用目标接入网设备中已建立好的包头压缩上下文(也可以理解为跳过使用，或暂时不使用，或去使能(disabled)目标接入网设备中已建立好的包头压缩上下文，或理解为将目标接入网设备中已建立好的包头压缩上下文的状态设置为不可用状态，或失效状态)，即目标接入网设备暂时不发送基于第一终端设备切换过来之前已创建好的包头压缩上下文进行包头压缩处理后的数据包，而是发送包头未经压缩的数据包，进一步地，当后续满足一定条件(例如确定第一终端设备与目标接入网设备的包头压缩上下文同步)时，再恢复使用(或理解为使用，或使能目标接入网设备中已建立好的包头压缩上下文，或理解为将目标接入网设备中已建立好的包头压缩上下文的状态设置为可用状态，或生效状态)第一终端设备切换过来之前已创建好的包头压缩上下文进行包头压缩处理，并向终端设备发送包头经过压缩的数据包，同样可保证终端设备能够正确解压缩包头经过压缩的数据包，易于操作，适用性高。
在一种可能的实现中，所述方法还包括：
确定所述第一终端设备建立所述第一包头压缩上下文；
恢复使用所述第一包头压缩上下文对数据包的包头进行压缩或解压缩。
在本申请中，当确定所述第一终端设备建立所述第一包头压缩上下文时，可认为第一终端设备与目标接入网设备的包头压缩上下文进行了同步，因此，目标接入网设备可恢复使用第一终端设备切换过来之前已创建好的包头压缩上下文进行包头压缩处理，并向终端设备发送包头经过压缩的数据包。
在一种可能的实现中，所述方法还包括：
接收来自所述第一终端设备的反馈信息，所述反馈信息用于指示所述第一终端设备建立所述第一包头压缩上下文；
所述确定所述第一终端设备建立所述第一包头压缩上下文，包括：
根据所述反馈信息，确定所述第一终端设备建立所述第一包头压缩上下文。
在本申请中，反馈信息中可包括头压缩上下文标识，其中，一个头压缩上下文标识对应一个第一包头压缩上下文。因此，当目标接入网设备接收到来自第一终端设备的反馈信息后，目标接入网设备可根据反馈信息中的头压缩上下文标识，确定第一终端设备建立(或成功建立)了该头压缩上下文标识对应的第一包头压缩上下文。
在一种可能的实现中，所述向所述第一终端设备发送第一信息，包括：
通过点到点PTP传输方式向所述第一终端设备发送所述第一信息。
在本申请中，当第一终端设备从源接入网设备成功切换到目标接入网设备后，目标接入网设备可以通过PTP传输方式向第一终端设备发送第一信息，可以保证第一终端设备在切换后，可以对接收到的来自目标接入网设备的头压缩数据包(即包头经过压缩的数据包)进行正确的解压缩。
在一种可能的实现中，所述通过PTP传输方式向所述第一终端设备发送所述第一信息，包括：
通过PTP传输方式向所述第一终端设备发送媒体接入控制控制元素MAC CE，所述MAC CE中包括所述第一信息；或者
通过PTP传输方式向所述第一终端设备发送无线资源控制RRC信令，所述RRC信令中包括所述第一信息。
在本申请中，第一信息可以承载在MAC CE、或RRC信令、或分组数据汇聚层协议控制协议数据单元(即PDCP控制PDU)中发送给第一终端设备，在此不做限制，操作灵活性高。
在一种可能的实现中，所述方法还包括：
通过点到多点PTM传输方式和/或点对点PTP传输方式向所述第一终端设备发送包头经过压缩的数据包。
在本申请中，当第一终端设备从源接入网设备成功切换到目标接入网设备后，目标接入网设备可以同时通过PTP和PTM传输路径向终端设备发送数据包，具体地，可以基于PTP传输方式向第一终端设备发送包头未经压缩的数据包，基于PTM方式发送包头经过压缩的数据包。如果不允许同时发送，即只能通过一种传输路径发送数据包，则针对该第一终端设备，目标接入网设备可以在实现时通过PTP方式向第一终端设备发送包头未经压缩的数据包，帮助该切换过来的第一终端设备建立头压缩上下文，以及通过PTP方式向第一终端发送包头经过压缩的数据包，保证该第一终端设备通过PTP接收数据包的进度不慢于其他终端设备通过PTM接收数据包的进度。
在一种可能的实现中，所述向所述第一终端设备发送第一信息，包括：
通过所述源接入网设备向所述第一终端设备发送所述第一信息，所述第一信息承载于切换命令。
在本申请中，在第一终端设备从源接入网设备切换至目标接入网设备的切换过程中，目标接入网设备可通过源接入网设备向第一终端设备发送第一信息。具体地，目标接入网设备可将第一信息携带在切换请求确认消息发送给源接入网设备，其中，源接入网设备接收到切换请求确认消息后，通过切换命令将第一信息发送给第一终端设备。可理解的，通过在切换流程中向第一终端设备发送第一信息，可节省传输资源，有利于提高通信效率，保证第一终端设备在切换后，能够对接收到的来自目标接入网设备的头压缩数据包(即包头经过压缩的数据包)进行正确的解压缩。
第二方面，本申请提供了一种通信方法，该方法可适用于第一终端设备。该方法包括：从源接入网设备切换至目标接入网设备；接收来自所述目标接入网设备的第一信息，所述第一信息用于指示第一包头压缩上下文，所述第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。
在一种可能的实现中，所述方法还包括：
向所述目标接入网设备发送反馈信息，所述反馈信息用于指示第一终端设备成功建立所述第一包头压缩上下文。
在一种可能的实现中，所述接收来自所述目标接入网设备的第一信息，包括：
通过点到点PTP传输方式接收来自所述目标接入网设备的所述第一信息。
在一种可能的实现中，所述通过PTP传输方式接收来自所述目标接入网设备的所述第一信息，包括：
通过PTP传输方式接收来自所述目标接入网设备的媒体接入控制控制元素MAC CE，所述MAC CE中包括所述第一信息；或者
通过PTP传输方式接收来自所述目标接入网设备的无线资源控制RRC信令，所述RRC信令中包括所述第一信息。
在一种可能的实现中，所述方法还包括：
通过点到多点PTM传输方式和/或所述PTP传输方式接收来自所述目标接入网设备，且包头经过压缩的数据包。
在一种可能的实现中，所述第一头压缩上下文承载于包头未经压缩的数据包之中，所述包头未经压缩的数据包对应第一序列号，所述包头经过压缩的数据包对应第二序列号，所述第一序列号和所述第二序列号相同；
所述方法还包括：
丢弃所述包头经过压缩的数据包。
在本申请中，切换过来的第一终端设备的重复检测功能需要考虑数据包的包头是否经过了压缩，具体地，当第一终端设备接收到两个包括相同序列号的数据包时，第一终端设备需要判断这两个数据包的包头是否经过了压缩，如果其中一个包头经过了压缩，另一个未压缩，则丢弃压缩的数据包，如果两个都经过了压缩或者都未经过压缩，则丢弃后接收到的数据包。
在一种可能的实现中，所述包头经过压缩的数据包中包括头压缩上下文标识；所述方法还包括：
在所述第一终端设备建立所述头压缩上下文标识对应的第一头压缩上下文之前，保存所述包头经过压缩的数据包；
根据所述头压缩上下文标识对应的第一头压缩上下文解压缩所述包头经过压缩的数据包。
在本申请中，在所述第一终端设备建立所述头压缩上下文标识对应的第一头压缩上下文之前，保存所述头压缩数据包，等待对应的头压缩上下文建立好以后才能对相应的包头经过 压缩的数据包进行解压缩处理。
在一种可能的实现中，所述接收来自所述目标接入网设备的第一信息，包括：
接收所述目标接入网设备通过所述源接入网设备发送的第一信息，所述第一信息承载于切换命令。
第三方面，本申请提供了一种通信装置，该装置可以为目标接入网设备。该装置包括：处理单元，用于确定第一终端设备从源接入网设备切换至所述目标接入网设备；收发单元，用于向所述第一终端设备发送第一信息，所述第一信息用于指示第一包头压缩上下文，所述第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。
在一种可能的实现中，所述处理单元还用于：
停止使用所述第一终端设备从所述源接入网设备切换至所述目标接入网设备之前，所述目标接入网设备对数据包的包头进行压缩或解压缩时所使用的头压缩上下文；
建立所述第一包头压缩上下文。
在一种可能的实现中，所述处理单元还用于：
暂停使用所述第一包头压缩上下文对数据包的包头进行压缩，所述第一包头压缩上下文为所述第一终端设备从所述源接入网设备切换至所述目标接入网设备之前，所述目标接入网设备对数据包的包头进行压缩或解压缩时所使用的头压缩上下文。
在一种可能的实现中，所述处理单元还用于：
确定所述第一终端设备建立所述第一包头压缩上下文；
恢复使用所述第一包头压缩上下文对数据包的包头进行压缩或解压缩。
在一种可能的实现中，所述收发单元，还用于接收来自所述第一终端设备的反馈信息，所述反馈信息用于指示所述第一终端设备建立所述第一包头压缩上下文；
所述处理单元，还用于根据所述反馈信息，确定所述第一终端设备建立所述第一包头压缩上下文。
在一种可能的实现中，所述收发单元用于：
通过点到点PTP传输方式向所述第一终端设备发送所述第一信息。
在一种可能的实现中，所述收发单元具体用于：
通过PTP传输方式向所述第一终端设备发送媒体接入控制控制元素MAC CE，所述MAC CE中包括所述第一信息；或者
通过PTP传输方式向所述第一终端设备发送无线资源控制RRC信令，所述RRC信令中包括所述第一信息。
在一种可能的实现中，所述收发单元还用于：
通过点到多点PTM传输方式和/或点对点PTP传输方式向所述第一终端设备发送包头经过压缩的数据包。
在一种可能的实现中，所述收发单元还用于：
通过所述源接入网设备向所述第一终端设备发送所述第一信息，所述第一信息承载于切换命令。
第四方面，本申请提供了一种通信装置，该装置可以为第一终端设备。该装置包括：处理单元，用于从源接入网设备切换至目标接入网设备；收发单元，用于接收来自所述目标接入网设备的第一信息，所述第一信息用于指示第一包头压缩上下文，所述第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。
在一种可能的实现中，所述收发单元还用于：
向所述目标接入网设备发送反馈信息，所述反馈信息用于指示所述第一终端设备成功建立所述第一包头压缩上下文。
在一种可能的实现中，所述收发单元用于：
通过点到点PTP传输方式接收来自所述目标接入网设备的所述第一信息。
在一种可能的实现中，所述收发单元具体用于：
通过PTP传输方式接收来自所述目标接入网设备的媒体接入控制控制元素MAC CE，所述MAC CE中包括所述第一信息；或者
通过PTP传输方式接收来自所述目标接入网设备的无线资源控制RRC信令，所述RRC信令中包括所述第一信息。
在一种可能的实现中，所述收发单元还用于：
通过点到多点PTM传输方式和/或所述PTP传输方式接收来自所述目标接入网设备，且包头经过压缩的数据包。
在一种可能的实现中，所述第一头压缩上下文承载于包头未经压缩的数据包之中，所述包头未经压缩的数据包对应第一序列号，所述包头经过压缩的数据包对应第二序列号，所述第一序列号和所述第二序列号相同；
所述处理单元还用于：
丢弃所述包头经过压缩的数据包。
在一种可能的实现中，所述包头经过压缩的数据包中包括头压缩上下文标识；所述处理单元还用于：
在所述第一终端设备建立所述头压缩上下文标识对应的第一头压缩上下文之前，保存所述包头经过压缩的数据包；
根据所述头压缩上下文标识对应的第一头压缩上下文解压缩所述包头经过压缩的数据包。
在一种可能的实现中，所述收发单元还用于：
接收所述目标接入网设备通过所述源接入网设备发送的第一信息，所述第一信息承载于切换命令。
第五方面，本申请提供了一种通信装置，该装置可以是接入网设备(例如目标接入网设备)，也可以是接入网设备中的装置，或者是能够和接入网设备匹配使用的装置。其中，该通信装置还可以为芯片系统。该通信装置可执行第一方面所述的方法。该通信装置的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。该单元或模块可以是软件和/或硬件。该通信装置执行的操作及有益效果可以参见上述第一方面所述的方法以及有益效果，重复之处不再赘述。
第六方面，本申请提供了一种通信装置，该装置可以是终端设备(例如第一终端设备)，也可以是终端设备中的装置，或者是能够和终端设备匹配使用的装置。其中，该通信装置还可以为芯片系统。该通信装置可执行第二方面所述的方法。该通信装置的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。该单元或模块可以是软件和/或硬件。该通信装置执行的操作及有益效果可以参见上述第二方面所述的方法以及有益效果，重复之处不再赘述。
第七方面，本申请提供了一种通信装置，该装置可以是接入网设备(例如目标接入网设备)，所述通信装置包括处理器和收发器，所述处理器和所述收发器用于执行至少一个存储器中存储的计算机程序或指令，以使得所述装置实现如第一方面中任意一项的方法。
第八方面，本申请提供了一种通信装置，该装置可以是接入网设备(例如目标接入网设 备)，该通信装置包括处理器、收发器和存储器。其中，处理器、收发器和存储器耦合；处理器和收发器用于实现如第一方面中任意一项的方法。
第九方面，本申请提供了一种通信装置，该装置可以是终端设备(例如第一终端设备)，所述通信装置包括处理器和收发器，所述处理器和所述收发器用于执行至少一个存储器中存储的计算机程序或指令，以使得所述装置实现如第一方面中任意一项的方法。
第十方面，本申请提供了一种通信装置，该装置可以是终端设备(例如第一终端设备)，该通信装置包括处理器、收发器和存储器。其中，处理器、收发器和存储器耦合；处理器和收发器用于实现如第一方面中任意一项的方法。
第十一方面，本申请提供了一种计算机可读存储介质，存储介质中存储有计算机程序或指令，当计算机程序或指令被计算机执行时，实现如第一方面～第二方面中任意一项的方法。
第十二方面，本申请提供一种包括指令的计算机程序产品，所述计算机程序产品中包括计算机程序代码，当计算机程序代码在计算机上运行时，以实现第一方面～第二方面中任意一项的方法。
附图说明
图1a是一种5G网络架构的示意图；
图1b是下行数据在各层间传输的示意图；
图1c是一种CU-DU分离架构的示意图；
图1d是另一种CU-DU分离架构的示意图；
图1e是一种空口协议栈分布示意图；
图2是一种MBS业务传输过程的示意图；
图3是一种切换流程示意图；
图4是接收多播广播业务的UE进行切换的场景示意图；
图5是本申请实施例提供的通信方法的一流程示意图；
图6是本申请实施例提供的接入网设备与终端设备间无线承载的示意图；
图7是本申请实施例提供的通信方法的另一流程示意图；
图8是本申请实施例提供的目标接入网设备重置头压缩上下文的场景示意图；
图9是本申请实施例提供的通信方法的另一流程示意图；
图10是本申请实施例提供的一种由于切换而影响目标接入网设备中头压缩上下文状态的场景示意图；
图11是本申请实施例提供的通信方法的另一流程示意图；
图12是本实施实施例提供的同时通过PTP和PTM传输路径发送数据包的场景示意图；
图13是本申请实施例提供的一种通信装置的结构示意图；
图14是本申请实施例提供的另一种通信装置的结构示意图；
图15是本申请实施例提供的另一种通信装置的结构示意图；
图16是本申请实施例提供的另一种通信装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
在本申请的描述中，除非另有说明，“/”表示“或”的意思，例如，A/B可以表示A或B。本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。此外，“至少一个”是指一个或多个，“多个”是指两个或两个以上。“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(global system of mobile communication，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、第五代(5th generation，5G)系统或新无线(new radio，NR)以及未来的通信系统等，在此不做限制。
为便于理解，本申请实施例5G通信系统为例，以下对5G通信系统中的相关网元进行详细介绍：
请参见图1a，图1a是本申请实施例提供的一种5G网络架构的示意图。如图1a所示，该网络架构可以包括终端设备部分、(无线)接入网((radio)access network，(R)AN)、核心网(core network，CN)和数据网络(data network，DN)。其中，(R)AN(后文描述为RAN)用于将终端设备接入到无线网络，CN用于对终端设备进行管理并提供与DN通信的网关。
下面分别对图1a中所涉及的终端设备、RAN、CN和DN进行详细说明。
一、终端设备
终端设备部分在图1a中包括终端设备210，终端设备210也可以称为用户设备(user equipment，UE)。本申请实施例中的终端设备210是一种具有无线收发功能的设备，可以经接入网(access network，AN)240中的接入网设备与一个或多个核心网(core network，CN)的网元进行通信。终端设备210也可称为接入终端、终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线网络设备、用户代理或用户装置等。终端设备210可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上，如轮船等；还可以部署在空中(例如飞机、气球和卫星上等)。终端设备210可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、智能电话、手机、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)，可以是具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它设备、车载设备、可穿戴设备、无人机设备或物联网、车联网中的终端、第五代移动通信(fifth generation，5G)网络以及未来网络中的任意形态的终端、中继用户设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端等，其中，中继用户设备例如可以是5G家庭网关(residential gateway，RG)。例如终端设备210可以是虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制中的无线终端、无人驾驶中的无线终端、远程医疗中的无线终端、智能电网(smart grid)中的无线终端、运输安全中的无线终 端、智慧城市中的无线终端、智慧家庭中的无线终端等。本申请实施例对此不做限定。
二、RAN
如图1a中所示，RAN包括接入网设备240。需要知晓的是，RAN中可以包括一个或多个RAN设备(或者说接入网设备)，接入网设备与终端设备之间的接口可以为Uu接口(或称为空口)。当然，在未来通信中，这些接口的名称可以不变，或者也可以用其它名称代替，本申请对此不限定。
接入网设备即为将终端设备接入到无线网络的节点或设备，接入网设备例如包括但不限于：5G通信系统中的新一代基站(generation node B，gNB)、演进型节点B(evolved node B，eNB)、下一代演进型节点B(next generation eNB，ng-eNB)、无线回传设备、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站((home evolved nodeB，HeNB)或(home node B，HNB))、基带单元(baseBand unit，BBU)、传输接收点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等，在此不做限制。另外，接入网设备也可以是6G通信系统中的基站，或者是开放型基站(Open RAN)或者云基站(Cloud RAN)，在Open RAN下，本发明涉及的接入网设备间或者接入网设备内的接口可能会变为Open RAN的内部接口，这些内部接口之间的流程和信息交互可以通过软件或者程序实现，所以本发明的技术方案同样适用于Open RAN架构，只要实现思想与本发明的方案相同或者相似，即落在本发明的保护范围之内。其中，本申请实施例可以接入网设备为基站，对本申请实施例所提供的方案进行示意性说明。
(1)协议层结构
接入网设备和终端设备之间的通信遵循一定的协议层结构，例如控制面协议层结构可以包括无线资源控制(radio resource control，RRC)层、分组数据汇聚层协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理层(Physical Layer，PHY)；用户面协议层结构可以包括PDCP层、RLC层、MAC层和物理层，在一种可能的实现中，PDCP层之上还可以包括业务数据适配(service data adaptation protocol，SDAP)层。
以接入网设备和终端设备之间的数据传输为例，数据传输需要经过用户面协议层，比如经过SDAP层、PDCP层、RLC层、MAC层、物理层，其中，SDAP层、PDCP层、RLC层、MAC层、物理层也可以统称为接入层。示例性地，接入网设备和终端设备之间通过建立至少一个数据无线承载(data radio bearer，DRB)来传输数据，每个DRB可以对应一组功能实体集合，比如包括一个PDCP层实体，该PDCP层实体对应的至少一个RLC层实体，至少一个RLC层实体对应的至少一个MAC层实体，至少一个MAC层实体对应的至少一个物理层实体。需要说明的是，接入网设备和终端设备之间还可以通过建立至少一个信令无线承载(signalling radio bearer，SRB)来传输信令，DRB和SRB可以统称为无线承载(radio bearer，RB)。也就是说，可将接入网设备和终端设备中各层对数据包的处理结合起来称为无线承载，对于无线承载里的每个数据，都需要经过各个层的处理，每个层都有相应的功能实体来执行相应的功能，比如PDCP层的PDCP实体。
以下行数据传输为例，图1b是下行数据在各层间传输的示意图，图1b中向下的箭头表示数据发送，向上的箭头表示数据接收。SDAP层实体自上层取得数据后，可以根据数据的服务质量流标识(QoS flow indicator，QFI)将数据映射到相应DRB的PDCP层实体，PDCP层实体可以将数据传送到该PDCP层实体对应的至少一个RLC层实体，进而由至少一个RLC层实体传 输到对应的MAC层实体，再由MAC层实体生成传输块，然后通过对应的物理层实体进行无线传输。数据在各个层中进行相对应的封装，某一层从该层的上层收到的数据视为该层的服务数据单元(service data unit，SDU)，经过层封装后成为协议数据单元(protocol data unit，PDU)，再传递给下一个层。例如PDCP层实体从上层接收到的数据称为PDCP SDU，PDCP层实体发送到下层的数据称为PDCP PDU；RLC层实体从上层接收到的数据称为RLC SDU，RLC层实体发送到下层的数据称为RLC PDU。其中，不同层之间可以通过相应的通道来传输数据，比如RLC层实体与MAC层实体之间可以通过逻辑信道(logical channel，LCH)来传输数据，MAC层实体与物理层实体之间可以通过传输通道(transport channel)来传输数据。可理解的，上述下行数据可以是MBS业务的数据，例如可以是直播业务数据、公共安全业务数据或批量软件更新业务数据等，在此不做限制。也就是说，对于MBS业务来说，数据的传输方向是从接入网设备到终端设备的。
示例性地，根据图1b还可以看出，终端设备还具有应用层和非接入层；其中，应用层可以用于向终端设备中所安装的应用程序提供服务，比如，终端设备接收到的下行数据可以由物理层依次传输到应用层，进而由应用层提供给应用程序；又比如，应用层可以获取应用程序产生的数据，并将数据依次传输到物理层，发送给其它通信装置。非接入层可以用于转发用户数据，比如将从应用层接收到的上行数据转发给SDAP层或者将从SDAP层接收到的下行数据转发给应用层。
(2)CU和DU
本申请实施例中，接入网设备可以包括一个或多个集中式单元(centralized unit，CU)和一个或多个分布式单元(distributed unit，DU)，多个DU可以由一个CU集中控制，一个DU也可以连接多个CU。作为示例，CU和DU之间的接口可以称为F1接口，其中，控制面(control panel，CP)接口可以为F1-C，用户面(user panel，UP)接口可以为F1-U。CU和DU可以根据无线网络的协议层划分：比如图1c所示，图1c是一种CU-DU分离架构的示意图。其中，PDCP层及以上协议层的功能设置在CU，PDCP层以下协议层(例如RLC层和MAC层等)的功能设置在DU。
可以理解的，上述对CU和DU的处理功能按照协议层的划分仅仅是一种举例，也可以按照其他的方式进行划分，比如RLC层以上协议层的功能设置在CU，RLC层及以下协议层的功能设置在DU，又比如可以将CU或者DU划分为具有更多协议层的功能，又比如CU或DU还可以划分为具有协议层的部分处理功能。在一种设计中，将RLC层的部分功能和RLC层以上的协议层的功能设置在CU，将RLC层的剩余功能和RLC层以下的协议层的功能设置在DU。在另一种设计中，还可以按照业务类型或者其他系统需求对CU或者DU的功能进行划分，例如按时延划分，将处理时间需要满足时延要求的功能设置在DU，不需要满足该时延要求的功能设置在CU。在另一种设计中，CU也可以具有核心网的一个或多个功能。示例性地，CU可以设置在网络侧方便集中管理；DU可以具有多个射频功能，也可以将射频功能拉远设置。本申请实施例对此并不进行限定。
示例性地，CU的功能可以由一个实体来实现，或者也可以由不同的实体来实现。例如，如图1d所示，图1d是另一种CU-DU分离架构的示意图。其中，可以对CU的功能进行进一步切分，即将控制面和用户面分离并通过不同实体来实现，分别为控制面CU实体(即CU-CP实体)和用户面CU实体(即CU-UP实体)，CU-CP实体和CU-UP实体可以与DU相耦合，共同完成RAN设备的功能。CU-CP实体与CU-UP实体之间的接口可以为E1接口，CU-CP实体与DU之间的接口可以为F1-C接口，CU-UP实体与DU之间的接口可以为F1-U接口。其中，一个DU和一个 CU-UP可以连接到一个CU-CP。在同一个CU-CP控制下，一个DU可以连接到多个CU-UP，一个CU-UP可以连接到多个DU。
基于图1d，图1e是一种空口协议栈分布示意图。如图1e所示，针对用户面和控制面来说，空口协议栈都可以是RLC、MAC、PHY在DU，PDCP及以上协议层在CU。
需要说明的是：在上述图1c至图1e所示意的架构中，CU产生的信令可以通过DU发送给终端设备，或者终端设备产生的信令可以通过DU发送给CU。DU可以不对该信令进行解析而直接通过协议层封装后透传给终端设备或CU。以下实施例中如果涉及这种信令在DU和终端设备之间的传输，此时，DU对信令的发送或接收包括这种场景。例如，RRC或PDCP层的信令最终会处理为物理层的数据发送给终端设备，或者，由接收到的物理层的数据转变而来。在这种架构下，该RRC或PDCP层的信令，即也可以认为是由DU发送的，或者，由DU和射频装置发送的。
三、CN
如图1a所示，CN包括网络开放功能(network exposure function，NEF)231、网络存储功能(network function repository function，NRF)232、策略控制功能(policy control function，PCF)233、统一数据管理(unified data management，UDM)网元234、应用功能(application function，AF)235、认证服务器功能(authentication server function，AUSF)236、接入与移动性管理功能(access and mobility management function，AMF)237、会话管理功能(session management function，SMF)238、用户面功能(user plane function，UPF)239以及(无线)。为方便说明，本申请实施例后文中所提及的接入网设备(也可以称为基站)是以RAN为例进行说明的。本申请实施例后文中所提及的核心网设备可以理解为CN功能网元的统称。
AMF网元是由运营商网络提供的控制面网元，负责终端设备接入运营商网络的接入控制和移动性管理，例如包括移动状态管理，分配用户临时身份标识，认证和授权用户等功能。
SMF网元是由运营商网络提供的控制面网元，负责管理终端设备的PDU会话。PDU会话是一个用于传输PDU的通道，终端设备需要通过PDU会话与DN互相传送PDU。PDU会话由SMF网元负责建立、维护和删除等。SMF网元包括会话管理(如会话建立、修改和释放，包含UPF和RAN之间的隧道维护)、UPF网元的选择和控制、业务和会话连续性(service and session continuity，SSC)模式选择、漫游等会话相关的功能。
UPF网元是由运营商提供的网关，是运营商网络与DN通信的网关。UPF网元包括数据包路由和传输、包检测、服务质量(quality of service，QoS)处理、合法监听、上行包检测、下行数据包存储等用户面相关的功能。
PCF网元是由运营商提供的控制面功能，用于向SMF网元提供PDU会话的策略。策略可以包括计费相关策略、QoS相关策略和授权相关策略等。
AF网元是提供各种业务服务的功能网元，能够通过其它网元与核心网交互，以及能够和策略管理框架交互进行策略管理。
此外，尽管未示出，CN中还可以包括其它可能的网元，比如网络开放功能(network exposure function，NEF)、网元统一数据仓储(unified data repository，UDR)网元。
四、DN
如图1a所示，数据网络DN 220，也可以称为分组数据网络(packet data network，PDN)，通常是位于运营商网络之外的网络，例如第三方网络。运营商网络可以接入多个数据网络DN 220，数据网络DN 220上可部署多种业务，可为终端设备210提供数据和/或语音等服务。例如，数据网络DN 220可以是某智能工厂的私有网络，智能工厂安装在车间的传感器可为终端设备 210，数据网络DN 220中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，数据网络DN 220可以是某公司的内部办公网络，该公司员工的手机或者电脑可为终端设备210，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
图1a中Nnef、Nausf、Nnrf、Namf、Npcf、Nudm、Nsmf、Naf、N1、N2、N3、N4以及N6为接口序列号。这些接口序列号的含义可参见相关标准协议中定义的含义，在此不做限制。
可以理解的是，图1a中是以5G通信系统为例进行示意的，本申请实施例中的方案还可以适用于其它可能的通信系统中，比如LTE通信系统或者未来的第六代(the 6th generation，6G)通信系统中。上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
下面以数据网络DN是多播广播业务(Multicast and Broadcast Service，MBS)为例对业务数据的传输流程进行说明。可理解的是，MBS是面向多个UE的业务，例如直播业务、公共安全业务、批量软件更新业务等。
请参见图2，图2是一种MBS业务传输过程的示意图。如图2所示，MBS数据(例如MBS数据可以是直播业务数据、公共安全业务数据或批量软件更新业务数据等)来自数据服务器，首先数据服务器将MBS数据发送给核心网设备，然后核心网设备将MBS数据发送给接入网设备，最后接入网设备将MBS数据发送给接收MBS业务的至少一个UE。其中，从核心网向接入网设备发送的时候，MBS业务通过一个公共的传输通道MBS会话进行传输，从接入网设备向UE发送的时候，有两种传输方式：第一种可以采用PTM(point to multi-point，点到多点)传输方式；第二种可以采用PTP(point to point，点到点)传输方式。相应地，针对终端设备而言，终端设备可通过PTM传输方式接收来自接入网设备的数据包，或通过PTP传输方式接收来自接入网设备的数据包。
进一步地，为了使得本申请实施例更加的清楚，下面对本申请实施例涉及的相关技术特征进行解释说明。需要说明的是，这些解释是为了让本申请实施例更容易被理解，而不应该视为对本申请所要求的保护范围的限定。
一、数据包头压缩(也可称为报头压缩)
数据包头压缩的基本原理是：通过删除包头中原有字段或利用更短的字段替代包头中原有字段的方式来减小包头的大小。在无线通信系统中，主要存在两种包头压缩算法：第一种是针对IP数据包包头的鲁棒性头标压缩(robust header compression，ROHC)算法，第二种是针对以太网数据包包头的以太网包头压缩(ethernet header compression，EHC)算法，二者原理类似，压缩处理均在PDCP层进行，为方便理解，这里以ROHC算法为例对压缩处理流程进行说明：
发送侧的压缩端和接收侧的解压缩端提前生成并保存用于压缩和解压缩的上下文信息(或描述为上下文等)，其中，每个上下文对应一个上下文标识(Context Identifier，CID)。即在进行数据传输的开始阶段，发送侧将一个完整的IP包头以及对应的上下文标识发送给接收侧，后续传输中发送侧仅需发送数据包包头中动态变化的部分，对于重复概率较高的半静态部分或者静态部分不需要发送，解压缩端根据保存的上下文信息恢复出半静态或者静态的部分，从而还原出完整的数据包包头向上层递交。在理想情况下，收发两端的包头压缩上下 文一直保持同步，使得在发送侧被压缩的信息可以在接收侧被无损恢复。通常而言，若发送侧为开启了压缩功能，相应地，接收侧会开启解压缩功能，也就是说，压缩功能和解压缩功能是同时开启或同时关闭的，本申请实施例中可将开启了压缩功能的网络设备称为压缩端，将开启了解压缩功能的为例设备称为解压缩端(也可称为解压端)。
通常而言，压缩端会对包含不同内容或者信息的数据包包头使用不同的上下文进行头压缩，上下文的数量由最大上下文标识(maxCID)参数控制，如果新的数据包包头不能与已建立的上下文匹配，但是又没有更多可用的上下文标识了，此时，压缩端可以选择复用已存在的上下文(比如长时间未使用的)，即建立新的上下文覆盖已经存在的上下文，或者，不对新的数据包包头进行压缩(即发送包头未经压缩的数据包)。
二、切换(Handover)技术
在移动通信系统中，连接态UE的移动性管理是由网络设备控制的，即网络设备通过发送切换消息指示UE切换到哪个小区以及如何进行切换。为便于理解，请参见图3，图3是一种切换流程示意图。如图3所示，UE在接收到该切换消息后，可以根据切换消息中包含的内容，接入目标小区，因此，切换消息的成功发送是保证传统切换机制下成功切换的必要条件。具体地，切换流程包括：
第①步：源接入网设备发送RRC重配消息给连接态的UE，其中包含测量对象、报告配置、测量标识等参数。
第②步：UE根据接收到的RRC重配消息对一系列小区进行测量后，形成测量报告上报给当前连接的源接入网设备。
第③步：源接入网设备接收到UE上报的测量报告后将决定UE要不要切换(即源接入网设备进行切换判决)，如确定要切换，则源接入网设备将发送切换请求消息给目标接入网设备。
第④步：目标接入网设备接收到源接入网设备发送的切换请求消息后，目标接入网设备根据自身连接数等情况决定要不要允许UE的接入(即目标接入网设备进行允入控制)，如果允许就发送切换请求响应消息(或描述为切换确认消息，或切换请求确认消息等)给源接入网设备，其中，该切换请求响应消息中包括新小区的小区无线网络临时标识(cell radio network temporary identifier，C-RNTI)、目标接入网设备安全相关算法等参数。
第⑤步：源接入网设备在收到目标接入网设备发来的切换请求响应消息后，可向UE发送切换命令，其中切换命令中可包括第④步中切换请求响应消息中的参数，即相当于源接入网设备这层是透明的。具体的，5G系统中切换命令中包含目标小区的相关信息以及UE接入该目标小区所需的相关配置参数，例如，切换命令中包含目标小区的信息(如，目标小区的物理小区标识(physical cell identifier，PCI)以及目标小区对应的频率信息(如目标小区对应的频点。具体的，5G系统中，频率信息所包含的内容可参考协议TS38331中对FrequencyInfoDL IE的具体描述))、目标小区为UE分配的C-RNTI、接入目标小区所需的随机接入信道(random access channel，RACH)资源信息(如，专用RACH资源和/或公共RACH资源)等。
第⑥步：UE根据切换命令对目标接入网设备发起随机接入。
第⑦步：UE发送RRC重配置完成的消息给目标接入网设备。
可理解的，接收多播广播业务的UE由于发生了移动，经常需要从一个接入网设备切换到另一个接入网设备继续接收多播广播业务。例如，请参见图4，图4是接收多播广播业务的UE进行切换的场景示意图。如图4所示，核心网设备可向不同的接入网设备(如图4所示的接入网设备1和接入网设备2)发送多播广播业务的数据包，进而各接入网设备可分别 向其对应小区中包括的至少一个UE发送数据包。例如，如图4中接入网设备1可采用PTM传输方式向小区1中的UE1，UE2和UE3发送数据包，接入网设备2也可采用PTM传输方式向小区2中的UE4和UE5发送数据包。其中，当UE3发生移动时，例如UE3的位置从小区1移动至小区2时，该UE3需要从一个接入网设备1切换到接入网设备2继续接收多播广播业务的数据包。其中，上述接入网设备1即源接入网设备，上述接入网设备2即目标接入网设备。
其中，对于MBS业务来说，源接入网设备和目标接入网设备是独立进行发送的，对于某些MBS业务，例如语音业务，为了节省传输开销，接入网设备会开启对MBS数据包的头压缩功能，且两个接入网设备独立进行头压缩。而对于接收MBS业务的UE来说，从源接入网设备切换到目标接入网设备的时候，由于两个接入网设备建立头压缩上下文的过程相互独立，所以在源接入网设备建立好的压缩上下文无法用于对目标接入网设备传输的数据包进行包头解压缩，因此如何能保证UE在切换后能正常接收MBS业务成为当前亟待解决的问题之一。
基于此，本申请实施例提供了一种通信方法，该方法可实现切换场景下的正常通信，有利于提高通信的可靠性。其中，本申请实施例中的方法不仅适用于对数据包的包头部分的压缩并传输，也可以适用于对数据包的负载部分进行压缩并传输，或者，也可以适用于对整个数据包(即包头部分和数据部分)的压缩并传输等，在此不做限制，另外数据包在有些场景中也可以称为报文或者数据报文等。通常而言，是否开启压缩功能可以由接入网设备或者终端设备根据业务特性或者业务QoS需求或者网络负荷状况等情况决定，例如，语音业务数据包的包头比例较大，接入网设备或者终端设备可以针对语音业务的无线承载开启头压缩功能；或者当网络负荷比较重，或者网络资源紧张的时候，可以针对某些业务的无线承载开启头压缩，在此不做限制。通常而言，若发送侧开启了压缩功能，则相应地接收侧会开启解压缩功能；若发送侧关闭了压缩功能，则相应地接收侧会关闭解压缩功能，也就是说，发送侧的压缩功能和接收侧的解压缩功能可以是一同开启或一同关闭的，即压缩功能和解压缩功能是配套使用的。本申请实施例中可将开启了压缩功能的网络设备称为压缩端，将开启了解压缩功能的为例设备称为解压缩端或解压端。在本申请实施例中，发送侧开启了压缩功能即可以理解为发送侧会对待发送的数据包进行压缩处理，然后再将经过压缩处理后的数据包发送给接收侧。在本申请实施例中，发送侧关闭压缩功能即可以理解为发送侧不会对待发送的数据包进行压缩处理，而是会发送完整的数据包给接收侧。
需要说明的是，本申请实施例中开启了压缩功能也可以描述为使能了压缩功能等，在此不做限制，未开启压缩传输功能也可以描述为关闭了压缩功能，或者描述为去使能了压缩功能，或者描述为关闭了压缩传输功能等，在此不做限制。
还需要说明的是，本申请提供的方案可适用于上行传输或下行传输。其中，在下行传输中，接入网设备为压缩端，终端设备为解压缩端；在上行传输中，终端设备为压缩端，接入网设备为解压缩端。为方便理解，如下实施例以下行传输对数据包的包头进行压缩为例进行说明，在此示例中，压缩上下文为包头压缩上下文。此外，本申请实施例中的数据包，也可以描述为报文；本申请实施例中的包头，也可以描述为报文头或者报头；本申请实施例中包头未经压缩的数据包可以描述为全头数据包、完整报文头数据包等，在此不做限制；本申请实施例中的包头经过压缩的数据包，可以描述为头压缩数据包，或者也可以描述为压缩包，或者也可以描述为压缩报文头数据包，在此不做限制。本申请中的包头压缩上下文也可以描述为头压缩上下文，或者也可以描述为上下文，在此不做限制。本申请中的头压缩上下文标识也可以描述为包头压缩上下文标识，或者也可以描述为上下文标识，或者也可以描述为上 下文索引、上下文索引值或索引值，在此不做限制。
下面将结合更多的附图对本申请提供的技术方案进行详细说明。
请参见图5，图5是本申请实施例提供的通信方法的一流程示意图。如图5所示，该方法包括如下步骤S501至步骤S502，其中，图5所示的方法执行主体可以为目标接入网设备，或者，图5所示的方法执行主体也可以为目标接入网设备中的芯片等，在此不做限制。为方便描述，下面将以目标接入网设备为例进行说明。
S501、目标接入网设备确定第一终端设备从源接入网设备切换至目标接入网设备。
在一些可行的实施方式中，确定第一终端设备从源接入网设备切换至目标接入网设备。其中，第一终端设备从源接入网设备切换至目标接入网设备可以为：第一终端设备准备从源接入网设备切换至目标接入网设备(即切换前)，或者，第一终端设备从源接入网设备切换至目标接入网设备的切换过程中(即切换过程中)，或者，第一终端设备从源接入网设备成功切换到目标接入网设备之后(即切换后)等，在此不限制。示例性地，请参见上述图3，当目标接入网设备接收到来自源接入网设备的切换请求消息时，可确定切换流程开始；当目标接入网设备确定随机接入成功后，可确定切换流程结束，或者，当目标接入网设备接收到来自源接入网设备的RRC重配置完成消息时，可确定切换流程结束，在此不做限制。
S502、目标接入网设备向第一终端设备发送第一信息。
在一些可行的实施方式中，当确定第一终端设备从源接入网设备切换至目标接入网设备时，目标接入网设备可向第一终端设备发送第一信息。具体地，对于开启了压缩功能的目标接入网设备、或者是对于使能了压缩功能的目标接入网设备而言，该目标接入网设备可在第一终端设备从源接入网设备切换至目标接入网设备前，或准备从源接入网设备切换至目标接入网设备时，向第一终端设备发送第一信息，或者，第一终端设备从源接入网设备切换至目标接入网设备的切换过程中，向第一终端设备发送第一信息，或者，在第一终端设备从源接入网设备成功切换到目标接入网设备之后，向第一终端设备发送第一信息。
其中，第一信息的传输方式可以是采用PTM传输方式进行传输，或者也可以是采用PTP传输方式进行传输等，在此不做限制。具体地，当目标接入网设备通过PTP传输方式发送第一信息时，目标接入网设备下的所有终端设备，即第一终端设备和其他之前就在目标接入网设备下接收MBS业务的终端设备，都可以接收到该第一信息，当目标接入网设备通过PTP传输方式向第一终端设备发送第一信息时，只有第一终端设备可以接收到该第一信息，其他之前就在目标接入网设备下接收MBS业务的终端设备接收不到、或者无法获取该第一信息。
其中，该第一信息用于指示第一包头压缩上下文，第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。本申请实施例中，终端设备1切换前后，目标接入网设备传输的数据包属于相同的MBS业务，该MBS业务可以包含至少一种MBS业务。
通常而言，接入网设备和每个终端设备之间可通过建立无线承载用于传输数据、信令等信息，对于接收MBS业务的终端设备而言，该终端设备从源接入网设备切换至目标接入网设备后，目标接入网设备需要为该切换过来的终端设备，即第一终端设备，新配置无线承载。示例性地，请参见图6，图6是本申请实施例提供的接入网设备与终端设备间无线承载的示意图。如图6所示，终端设备1和终端设备2为终端设备3切换之前就在该目标接入网设备下接收多播广播业务的数据包的终端设备，其中，终端设备1与目标接入网设备间的无线承载为无线承载1，终端设备2与目标接入网设备间的无线承载为无线承载2。终端设备3为切换至目标接入网设备接收相同多播广播业务的终端设备，即终端设备1，终端设备2和终端 设备3为接收相同多播广播业务的终端设备。因此，当终端设备3从源接入网设备切换至目标接入网设备后，目标接入网设备需要为该切换过来的终端设备3新配置无线承载(如图6所示的无线承载3)。其中，该3个无线承载可用于传输相同的MBS数据包。通常而言，压缩功能是以无线承载粒度进行配置和/或执行的，即不同的无线承载可以配置相互独立的压缩功能，对于图6的示例来说，从终端设备的角度描述，不同的终端设备接收数据包的无线承载互不相同，但是从基站角度描述，基站侧可以通过同一个无线承载中的同一个PTM传输路径向不同的3个终端设备进行数据包传输，所以压缩功能是针对不同设备统一执行的，而解压缩功能是不同设备独立执行的。可以理解为3个无线承载的PTM传输路径在基站侧是共用一套协议栈统一进行处理的，具体来说，是共用同一个PDCP实体的，因此是共用压缩功能的。在终端设备3切换过来之前，基站侧使用该套协议栈(即基站侧的无线承载)对终端设备1和2进行MBS数据包的传输，并使用已经建立好的头压缩上下文对数据包进行头压缩；在终端设备3切换过来之后，基站侧使用该套协议栈(即基站侧的无线承载)对终端设备1-3进行MBS数据包的传输，但是停止使用已经建立好的包头压缩上下文对数据包进行头压缩，并建立新的包头压缩上下文用于后续对MBS数据包进行头压缩。
其中，若目标接入网设备是在第一终端设备切换前，或切换过程中，或切换后，将第一信息发送给第一终端设备，则目标接入网设备向第一终端设备发送第一信息可以理解为：目标接入网设备将第一头压缩上下文携带(或称承载)在包头未经压缩的数据包之中，并发送给第一接入网设备，或者，也可以理解为将用于指示第一头压缩上下文的第一信息承载在包头未经压缩的数据包中，并发送给第一终端设备。
可选的，第一头压缩上下文也可以承载于信令中，即用于指示第一头压缩上下文的第一信息可以承载于信令中，并发送给第一终端设备。例如，所涉及的信令可以是媒体接入控制控制元素(MAC control element，MAC CE)，或无线资源控制(radio resource control，RRC)信令，或分组数据汇聚层协议控制协议数据单元(PDCP control protocol data unit，PDCP control PDU)等，在此不做限制。
可选的，若目标接入网设备是在第一终端设备切换过程中，将第一信息发送给第一终端设备，则目标接入网设备向第一终端设备发送第一信息可以理解为：目标接入网设备可以通过源接入网设备向第一终端设备发送第一信息，该第一信息承载于切换命令。也就是说，目标接入网设备在切换过程中发送第一信息时，第一信息可以携带在切换配置。具体地，为便于理解，请一并参见前述图3，如图3所示，当目标接入网设备接收到来自源接入网设备的切换请求消息(或其他Xn接口消息)后，可根据切换请求消息判断终端设备是否需要接收MBS业务。在本申请实施例中，可以通过切换请求消息中的现有字段或者新增字段来指示第一终端设备需要接收的MBS业务。可理解的，如果MBS业务的传输(或者该MBS业务对应的无线承载)在目标接入网设备中开启了压缩功能，则目标接入网设备可在向源接入网设备发送的切换请求响应消息或描述为切换确认消息，或描述为切换请求确认消息等中的现有字段或者新增字段来指示该MBS业务或者无线承载对应的第一信息，以将包括第一信息的切换请求响应消息发送给源接入网设备。其中，当源接入网设备接收到切换请求确认消息以后，可通过切换命令将切换请求确认消息中携带的信息，发送或透传给第一终端设备。其中，切换请求确认消息中携带的信息可包括第一信息等，在此不做限制。
其中，当第一终端设备接收到切换命令后，可根据切换命令中第一信息所指示的第一包头压缩上下文，对在源接入网设备下建立的头压缩上下文进行更新或替换或刷新或覆盖。可理解的，若源接入网设备未开启压缩功能，则相应地第一终端设备也不会开启解压缩功能， 这是因为压缩功能和解压缩功能是一同关闭或一同开启的。因此，第一终端设备中不存在切换之前建立的上下文。基于此，第一终端设备根据第一信息建立第一包头压缩上下文可以为：第一终端设备在接收到切换命令后，可根据切换命令中第一信息，建立、新建或新增建立该第一信息所指示的第一包头压缩上下文。若源接入网设备本身开启了压缩传输功能，则第一终端设备根据第一信息建立第一包头压缩上下文可以为：第一终端设备根据第一信息将第一终端设备中已建立的包头压缩上下文替换或更新或刷新或覆盖为第一包头压缩上下文。其中，第一终端设备已建立的包头压缩上下文可以为第一终端设备在源接入网设备下接收MBS业务时，与源接入网设备进行同步的包头压缩上下文。也就是说，第一终端设备可删除第一终端设备在源接入网设备下接收MBS业务时，建立好的头压缩上下文，进而根据从目标接入网设备接收的第一信息建立第一包头压缩上下文。这里的删除可以指释放、弃用、或跳过使用该建立好的压缩上下文。因此，在后续确定第一终端设备成功切换至目标接入网设备后，目标接入网设备就可以使用第一包头压缩上下文，即新的头压缩上下文，对数据包的包头进行压缩，以生成头压缩数据包发送给目标接入网设备下的所有终端设备，其中，目标接入网设备下的所有终端设备，即第一终端设备和其他之前就在目标接入网设备下接收MBS业务的终端设备。相应地，针对各个接收到了第一信息并根据第一信息建立了对应的第一包头压缩上下文的各个终端设备而言，例如第一终端设备，其可以根据与目标接入网设备进行同步后的第一包头压缩上下文，即新的头压缩上下文，对从目标接入网设备接收到的包头经过压缩的数据包，即头压缩数据包进行解压缩。
其中，上述用于承载第一信息的包头未经压缩的数据包，MAC CE、RRC信令、PDCP control PDU、切换请求消息或切换命令中还可以包括每个包头压缩上下文对应的头压缩上下文标识(为方便描述，也可以简称为上下文标识)或者索引值等信息，在此不做限制。其中，一个头压缩上下文对应一个上下文标识。因此，当第一终端设备接收到包头未经压缩的数据包或MAC CE或RRC信令或PDCP control PDU或切换命令之后，第一终端设备可保存第一包头压缩上下文和对应的上下文标识的对应关系，以便后续接收到包头经过压缩的数据包时，根据包头经过压缩的数据包中携带的上下文标识，确定对应的第一包头压缩上下文对头压缩数据包进行解压缩。可以理解的，第一信息可以包括多个包头压缩上下文以及相对应的多个上下文标识，其中每个包头压缩上下文用于对相应的包头进行压缩和解压缩。
在本申请实施例中，当有终端设备成功切换至目标接入网设备前，切换过程中，或者切换至目标接入网设备后，向切换过来的第一终端设备发送第一信息，可使得第一终端设备根据第一信息建立对应的上下文，从而实现第一终端设备在切换后与目标接入网设备保持头压缩上下文的同步，进而能够对接收到的来自目标接入网设备的头压缩数据包进行正确解压缩，有利于提高通信的可靠性。可选的，若是在切换过程中，目标接入网设备通过切换配置对终端设备的头压缩上下文进行更新，则同样可以实现终端设备在切换后与目标接入网设备保持头压缩上下文的同步，进而能够对接收到的来自目标接入网设备的头压缩数据包进行正确解压缩，有利于提高通信的可靠性。
请参见图7，图7是本申请实施例提供的通信方法的另一流程示意图。如图7所示，该方法包括如下步骤S701至步骤S703，其中，图7所示的方法执行主体可以为目标接入网设备，或者，图7所示的方法执行主体也可以为目标接入网设备中的芯片等，在此不做限制。为方便描述，下面将以目标接入网设备为例进行说明。
S701、目标接入网设备确定第一终端设备从源接入网设备切换至目标接入网设备。
其中，本申请实施例中对步骤S701的描述可以参见图5对应的实施例一中对步骤S501的描述，这里不再进行赘述。
S702、目标接入网设备停止使用第一终端设备从源接入网设备切换至目标接入网设备之前，目标接入网设备对数据包的包头进行压缩或解压缩时所使用的头压缩上下文。
在一些可行的实施方式中，目标接入网设备还可以停止使用第一终端设备从源接入网设备切换至目标接入网设备之前，目标接入网设备对数据包的包头进行压缩时所使用的头压缩上下文，这是因为第一终端设备切换过来以后，没有建立目标接入网设备的头压缩上下文。因此，目标接入网设备需要重新建立或建立并保存，或建立并存储上下文，为方便描述，本申请实施例中可将目标接入网设备重新建立的上下文描述为第一包头压缩上下文，并将第一包头压缩上下文发送给包括第一终端设备在内的所有终端设备，即通过PTM传输方式发送第一包头压缩上下文。
需要说明的是，上述“停止使用”可以理解为删除、重置、刷新、跳过使用或不再使用，其中，不同描述间可以相互替换，本申请对此不做限制。如此，从停止使用切换前目标接入网设备所使用的上下文之后，直到在目标接入网设备确定第一终端设备建立第一包头压缩上下文之前，为了不影响MBS业务的正常传输，若目标接入网设备需要发送数据包，则目标接入网设备可发送包头未经压缩的数据包，即不开启压缩功能，或是关闭压缩功能。一个实施例中，目标接入网设备确定第一终端设备建立第一包头压缩上下文，也可以是目标接入网设备确定第一终端设备成功建立第一包头压缩上下文。从空口传输方面描述，第一终端设备的切换，会导致正在以压缩方式传输MBS数据包的目标接入网设备，转变为不使用压缩方式传输MBS数据包的状态，即发送的MBS数据包从包头经过压缩的数据包，变为包头未经过压缩的数据包。
S703、目标接入网设备通过PTM传输方式向第一终端设备发送第一信息。
在一些可行的实施方式中，对于开启了压缩功能、或者使能了压缩功能的目标接入网设备而言，可在第一终端设备准备从源接入网设备切换至目标接入网设备时，通过PTM传输方式向第一终端设备发送第一信息，或者，第一终端设备从源接入网设备切换至目标接入网设备的切换过程中，通过PTM传输方式向第一终端设备发送第一信息，或者，在第一终端设备从源接入网设备成功切换到目标接入网设备之后，通过PTM传输方式向第一终端设备发送第一信息。
其中，目标接入网设备通过PTM传输方式向第一终端设备发送第一信息可以理解为：目标接入网设备将第一头压缩上下文携带或承载在包头未经压缩的数据包之中，通过PTM传输方式发送给第一接入网设备，或者，也可以理解为将用于指示第一头压缩上下文的第一信息承载在包头未经压缩的数据包中，通过PTM传输方式发送给第一终端设备。可选的，第一头压缩上下文也可以承载于信令中，即用于指示第一头压缩上下文的第一信息可以承载于信令中，并通过PTM传输方式发送给第一接入网设备。例如，所涉及的信令可以是媒体接入控制控制元素(MAC control element，MAC CE)，或无线资源控制(radio resource control，RRC)信令，或分组数据汇聚层协议控制协议数据单元(PDCP control protocol data unit，PDCP control PDU)等，在此不做限制。
其中，上述用于承载第一信息的包头未经压缩的数据包或信令中还可以包括包头压缩上下文对应的头压缩上下文标识或上下文标识或者索引值等信息，在此不做限制。其中，一个头压缩上下文对应一个上下文标识。因此，当第一终端设备接收到包头未经压缩的数据包或信令之后，第一终端设备可保存包头未经压缩的数据包或信令中包括的包头压缩上下文和对 应的上下文标识的对应关系，以便后续接收到包头经过压缩的数据包时，根据包头经过压缩的数据包中携带的上下文标识，确定对应的第一包头压缩上下文对头压缩数据包进行解压缩。可以理解的，第一信息可以包括多个包头压缩上下文以及相对应的多个上下文标识，其中每个包头压缩上下文用于对相应的包头进行压缩和解压缩。
可理解的，虽然目标接入网设备可以在切换前、切换过程中或切换后就开始发送第一信息，但是针对切换的终端设备，即第一终端设备而言，第一终端设备需要在切换完成后，才可能接收到第一信息，进而根据第一信息建立第一包头压缩上下文。其中，若源接入网设备本身开启了压缩传输功能，则第一终端设备根据第一信息建立第一包头压缩上下文可以为：第一终端设备根据第一信息将第一终端设备中已建立的包头压缩上下文更新为第一包头压缩上下文。其中，第一终端设备已建立的包头压缩上下文可以为第一终端设备在源接入网设备下接收MBS业务时，与源接入网设备进行同步的包头压缩上下文。也就是说，第一终端设备可以删除、释放或弃用第一终端设备在源接入网设备下接收MBS业务时，建立好的头压缩上下文，进而根据从目标接入网设备接收的第一信息建立第一包头压缩上下文。若源接入网设备本身并未开启压缩传输功能，则第一终端设备在源接入网设备下接收MBS业务时，是没有建立与该MBS业务关联的头压缩上下文的，因此，第一终端设备根据第一信息建立第一包头压缩上下文可以为：第一终端设备根据第一信息在第一终端设备中新增建立或新建第一包头压缩上下文。
相应地，对于除第一终端设备之外的其他终端设备来说，即针对原本就在目标接入网设备下接收业务的其他终端设备，即其他之前就在目标接入网设备下接收MBS业务的终端设备而言，由于本申请实施例是采用PTM传输方式发送第一信息的，因此，这类终端设备也可以接收到第一信息，因此，这类终端设备可以根据接收到的第一信息不断地将已建立的上下文更新为最近或最新接收到的第一信息指示的第一包头压缩上下文。或者，也可以理解为该类终端设备可以先比较本次接收到的第一信息指示的第一包头压缩上下文与第一终端设备切换前或基于本次之前收到的第一信息所建立好的头压缩上下文是否相同，如果第一包头压缩上下文与第一终端设备切换前或基于本次之前收到的第一信息所建立好的头压缩上下文不相同，则使用第一包头压缩上下文替换第一终端设备切换前或基于本次之前收到的第一信息所建立好的头压缩上下文。
其中，目标接入网设备确定第一终端设备建立完成第一包头压缩上下文后，目标接入网设备可以开始对第一包头压缩上下文对应的包头进行压缩，即开启压缩功能。其中，由于本申请实施例中的目标接入网设备是采用PTM传输方式发送第一信息的，因此，通常情况下是当目标接入网设备确定目标接入网设备下所有终端设备，即包括切换过来的第一终端设备和原本就在目标接入网设备下接收业务的其他终端设备，都建立好与目标接入网设备同步的头压缩上下文以后，才可以开启压缩功能。
示例性地，请一并参见图4，其中，如图4所示的接入网设备1为源接入网设备，接入网设备2为目标接入网设备，UE3为第一终端设备，其中，其他之前就在目标接入网设备下接收MBS业务的终端设备即UE4和UE5，因此，在目标接入网设备发送第一信息之前，目标接入网设备可停止使用之前与UE4和UE5同步的头压缩上下文对需要发送的数据包进行压缩，而是在需要发送数据包时，发送包头未经压缩的数据包，直到确保所有终端设备，即如图4所示的UE3，UE4和UE5，都建立好与目标接入网设备同步的头压缩上下文以后，再对数据包的包头进行头压缩。可理解的，头压缩数据包中包括上下文标识，因此，针对目标接入网设备下各个终端设备而言，其可以根据头压缩数据包中包括的上下文标识，确定出对 应的第一包头压缩上下文，以根据确定出的第一包头压缩上下文对该头压缩数据包进行解压缩。
可理解的，由于该实施例中是停止使用第一终端设备切换前所使用的头压缩上下文，而重新建立的第一包头压缩上下文，所以从空口传输上来看，第一包头压缩上下文与第一终端设备切换前所使用的头压缩上下文并不一定相同，即相同上下文标识对应的上下文信息并不一定相同。所以当再次使用压缩方式传输MBS数据包后，即发送的MBS数据包从包头未经过压缩的数据包，变为包头经过压缩的数据包后，所使用的压缩上下文与第一终端设备切换前使用的压缩上下文并不相同。
可理解的，前述各个步骤均是以一个终端设备的切换为例进行的说明，即一个第一终端设备。可选的，如果有多个终端设备相继切换到目标接入网设备，例如多个第一终端设备，则目标接入网设备需要针对多个切换的第一终端设备进行多次重置过程，即重新执行关闭压缩传输功能以及通过PTM传输方式发送第一信息的步骤。其中，不同的重置过程可以相互独立，即各个重置过程互不影响。也就是说，如果一个终端设备切换过来以后，目标接入网设备进行了重置，且重新建立了部分或全部上下文，如果此时有另一终端设备切换过来，则目标接入网设备需要再次进行重置，并重新发送第一信息，即重新执行头压缩上下文的建立过程。如果一个终端设备切换过来以后，目标接入网设备进行了重置，且在还未重建任何上下文时，有另一终端设备切换来过，此时目标接入网设备可以再次进行重置或者不做任何操作。
示例性地，请参见图8，图8是本申请实施例提供的目标接入网设备重置头压缩上下文的场景示意图。如图8所示，开始时，UE3与其他终端(如图8中的UE1和UE2)一起从接入网设备1接收MBS业务，接入网设备1针对MBS业务数据包开启了头压缩功能，在传输过程中接入网设备1和接入网设备1下面的终端设备(如图8所示的UE 1、UE2和UE 3)建立起了相互同步的头压缩上下文(如图8中线条1所示的context1～context3)，其中不同的头压缩上下文拥有不同的上下文标识。另外，接入网设备2针对相同的MBS业务数据包开启了头压缩功能，在传输过程中接入网设备2和接入网设备2下面的终端设备(如图8所示的UE4和UE5)建立起了相互同步的头压缩上下文(如图8中线条2所示的context1～context3)，其中不同的头压缩上下文拥有不同的上下文标识。当接入网设备1下面的UE3由于位置移动等原因，从接入网设备1切换到接入网设备2进行MBS业务接收的时候，由于UE3保存的头压缩上下文来自源接入网设备，而目标接入网设备与源接入网设备是独立产生头压缩上下文的，所以UE3无法对接入网设备2发送的MBS的头压缩数据包进行正常的解压缩，基于此，对于一个对MBS业务做头压缩的接入网设备，当终端设备切换过来的时候，该接入网设备(即目标接入网设备)可重置已有头压缩上下文，对所有UE重新开始建立上下文。如图8所示，当目标接入网设备确定有终端设备(如图8所示的UE3)从源接入网设备切换过来，而且该终端设备需要接收相同的MBS业务数据包时，为了该终端设备能够正确对MBS数据包进行解压缩，目标接入网设备可以对已经建立好的头压缩上下文(如图8中线条2所示的context1～context3)进行重置，或刷新，或删除，即不再使用，或停止使用之前已经建立好的头压缩上下文，而是重新建立头压缩上下文(如图8中线条3所示的context1～context3)，即向目标接入网设备下所以终端设备发送第一信息，使得所有终端设备更新上下文为如图8中线条3所示的context1～context3(如图8所示，UE3将线条1所示的context1～context3更新为线条3所示的context1～context3，UE4和UE5将线条2所示的context1～context3线条3所示的context1～context3)，并在确保所有终端设备都建立好与接入网设备同步的头压缩上下文以后，再对数据包的包头进行头压缩。
可选的，目标接入网设备也可以在确定第一终端设备建立完成第一包头压缩上下文之前就发送经第一包头压缩上下文对包头进行压缩后的数据包，即头压缩数据包，例如目标接入网设备可以通过PTM传输方式和/或PTP传输方式向第一终端设备发送包头经过压缩的数据包。该种情况下，针对未建立好第一包头压缩上下文的第一终端设备而言，第一终端设备可以先保存该头压缩数据包，等待对应的头压缩上下文建立好以后再对相应的头压缩数据包进行解压缩。其中，第一终端设备可以通过接收到的压缩数据包中包括的上下文标识确定相应的头压缩上下文是否已经建立好。换句话说，针对未建立好第一包头压缩上下文的第一终端设备而言，第一终端设备先保存该头压缩数据包，等待对应的头压缩上下文建立好以后再对相应的头压缩数据包进行解压缩可以为：第一终端设备接收到该头压缩数据包后，第一终端设备判断可用的头压缩上下文信息中是否存在该头压缩数据包中包括的头压缩上下文标识，其中，可用的头压缩上下文为可以用于数据包的包头进行压缩或解压缩的头压缩上下文信息。若存在，则根据该头压缩上下文标识对应的头压缩上下文解压缩该头压缩数据包，若不存在，则保存该头压缩数据包，直到第一终端设备成功建立该头压缩上下文标识对应的第一头压缩上下文时，再根据头压缩上下文标识对应的第一头压缩上下文解压缩该头压缩数据包。可理解的，上述对于终端设备接收到的头压缩数据包对应的上下文未建立好时，终端设备需要先保存该压缩数据包，等待对应的头压缩上下文建立好以后再对相应的头压缩数据包进行解压缩的描述可以单独作为一个实施例，或者作为可选步骤与本申请实施例中的一个或多个步骤进行结合，在此不做限制。
可选的，在本实施例中，当终端设备接收到的数据包的序列号与之前接收的数据包的序列号相同或满足一定偏差或满足某种关联关系时，不能简单地对后面接收到的数据包进行丢弃，而是需要进一步判断两个序列号相同的数据包的包头是否经过了压缩。也就是说，相较于当终端设备接收到的数据包的序列号与之前接收的数据包的序列号相同时，将后面接收到的数据包丢弃的重复检测过程，本申请实施例中终端设备的重复检测过程需要在终端设备接收到多个包括相同序列号或序列号满足一定偏差或序列号满足某种关联关系的数据包时，进一步考虑数据包的包头是否经过了压缩。其中，数据包的序列号可以是是PDCP层的序列号，例如，PDCP层的序列号可以是PDCP序列号(PDCP sequence number，PDCP SN)等，或者，序列号也可以是SDAP层的序列号，例如，SDAP层的序列号可以是SDAP SN等，或者序列号也可以是RLC层，或MAC层，或PHY层的序列号等，在此不做限制。为方便理解，本申请实施例皆以数据包的序列号为PDCP SN号为例进行示意性说明。
举例来说，假设终端设备通过PTM收到一个SN＝10的头压缩数据包，之后通过PTP接收到一个SN＝10的全头数据包，即包头未经压缩的数据包。此时一种实现方式是，终端设备判断这两个数据包的包头是否经过了压缩，如果其中一个包头经过了压缩，另一个未压缩，则丢弃压缩的数据包，或描述为或描述为保留未经压缩的数据包，或描述为丢弃压缩的数据包且保留未经压缩的数据包；如果两个都经过了压缩或者都未经过压缩，则丢弃后接收到的数据包，或描述为保留先接收到的数据包，或描述为丢弃后接收到的数据包且保留先接收到的数据包。另一种实现方式是，终端设备判断这两个数据包是从哪个传输路径接收到的，如果其中一个从PTM接收到，另一个从PTP接收到，则终端设备丢弃从PTM接收到的数据包；如果两个都是从PTM或者PTP接收到，则丢弃后接收到的数据包等，在此不做限制。可理解的，上述对于终端设备的重复检测功能的描述可以单独作为一个实施例，或者作为可选步骤与本申请实施例中的一个或多个步骤进行结合，在此不做限制。可理解的，本申请中丢弃这一步骤也可以为可选步骤，即终端设备可以保留未经压缩的数据包或先接收到的数据包， 或终端设备跳过(skip)使用经过了压缩的数据包或后接收到的数据包，直接使用未经压缩的数据包或先接收到的数据包等，在此不做限制。
可理解的，上述步骤S701～步骤S703的执行顺序或时序关系可以是S701→S702→S703(即先关闭压缩功能，再发送第一信息)，或者也可以是S701→S703→S702(即先发送第一信息，再关闭压缩功能)，或者，也可以是S701→S703/S702(即并行执行S703步骤描述的关闭压缩功能和步骤S702中描述的发送第一信息)等等，在此不再一一列举。简单来说，上述对各个步骤的编号不对方案的执行顺序进行限制。
在本申请实施例中，目标接入网设备通过在终端设备切换前、切换过程中或切换后，对已经建立好的头压缩上下文进行重置或刷新或删除，即停止使用切换之前创建的上下文，并重新建立头压缩上下文的方法可以实现终端设备在切换后与目标接入网设备保持头压缩上下文的同步，进而能够对接收到的来自目标接入网设备的头压缩数据包进行正确解压缩，有利于提高通信的可靠性。
请参见图9，图9是本申请实施例提供的通信方法的另一流程示意图。如图9所示，该方法包括如下步骤S901至步骤S904，其中，图9所示的方法执行主体可以为目标接入网设备，或者，图9所示的方法执行主体也可以为目标接入网设备中的芯片等，在此不做限制。为方便描述，下面将以目标接入网设备为例进行说明。
S901、目标接入网设备确定第一终端设备从源接入网设备切换至目标接入网设备。
其中，本申请实施例中对步骤S901的描述可以参见图5对应的实施例一中对步骤S501的描述，这里不再进行赘述。
S902、目标接入网设备暂停使用第一包头压缩上下文对数据包的包头进行压缩。
在一些可行的实施方式中，目标接入网设备可以暂停使用(suspend)或挂起第一包头压缩上下文对数据包的包头进行压缩。在本申请实施例中，第一包头压缩上下文应该理解为第一终端设备从源接入网设备切换至目标接入网设备之前，目标接入网设备对数据包的包头进行压缩时所使用的头压缩上下文。
需要说明的是，上述“暂停使用”可以理解为跳过使用、暂时不使用、不继续使用、去使能、去激活、或理解为目标接入网设备将目标接入网设备中已建立好的包头压缩上下文的状态设置为不可用状态或失效状态等，本申请对此不做限制。可理解的，除了上述提及的通过去使能，或设置上下文状态失效，或设置上下文状态不可用来暂停使用目标接入网设备中已建立好的包头压缩上下文，在接入网设备的具体实现中，还可能会以其他形式出现，例如接入网设备也可以以标记、标识或者标签形式来标记对应的包头压缩上下文是否可用。例如，当可以使用某一上下文进行头压缩时，将可用使用的上下文标记出来；或者，当不可以使用某一上下文进行头压缩时，将不可以使用的上下文标记出来等，具体根据实际应用场景确定，在此不做限制。
S903、目标接入网设备向第一终端设备发送第一信息。
在一些可行的实施方式中，在一些可行的实施方式中，当确定第一终端设备从源接入网设备切换至目标接入网设备时，目标接入网设备可向第一终端设备发送第一信息。具体地，对于开启了压缩功能的目标接入网设备而言，可在第一终端设备准备从源接入网设备切换至目标接入网设备时，向第一终端设备发送第一信息，或者，第一终端设备从源接入网设备切换至目标接入网设备的切换过程中，向第一终端设备发送第一信息，或者，在第一终端设备从源接入网设备成功切换到目标接入网设备之后，向第一终端设备发送第一信息。
其中，第一信息的传输方式可以是采用PTM传输方式进行传输，或者也可以是采用PTP传输方式进行传输等，在此不做限制。具体地，当目标接入网设备通过PTP传输方式发送第一信息时，目标接入网设备下的所有终端设备，即第一终端设备和其他之前就在目标接入网设备下接收MBS业务的终端设备，都可以接收到该第一信息，当目标接入网设备通过PTP传输方式向第一终端设备发送第一信息时，只有第一终端设备可以接收到该第一信息，其他之前就在目标接入网设备下接收MBS业务的终端设备接收不到，或无法获取该第一信息。
其中，该第一信息用于指示第一包头压缩上下文，第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。其中，本申请涉及的数据包可以是MBS业务的数据包，或者，也可以其他业务(例如单播业务，或广播业务，或组播业务等)的数据包等，具体根据实际应用场景确定，在此不做限制。为方便理解，本申请实施例皆以MBS业务的数据包为例进行示意性说明。示例性地，MBS业务可以是直播业务、公共安全业务、批量软件更新业务等，在此不做限制。在本申请实施例中，第一包头压缩上下文应该理解为第一终端设备从源接入网设备切换至目标接入网设备之前，目标接入网设备对数据包的包头进行压缩时所使用的头压缩上下文。
其中，若目标接入网设备是在第一终端设备切换前，切换过程中，或切换后，将第一信息发送给第一终端设备，则目标接入网设备向第一终端设备发送第一信息可以理解为：目标接入网设备将第一头压缩上下文携带或承载在包头未经压缩的数据包之中，并发送给第一接入网设备，或者，也可以理解为将用于指示第一头压缩上下文的第一信息承载在包头未经压缩的数据包中，并发送给第一终端设备。可选的，第一头压缩上下文也可以承载于信令中，即用于指示第一头压缩上下文的第一信息可以承载于信令中，并发送给第一终端设备。例如，所涉及的信令可以是媒体接入控制控制元素(MAC control element，MAC CE)，或无线资源控制(radio resource control，RRC)信令，或分组数据汇聚层协议控制协议数据单元(PDCP control protocol data unit，PDCP control PDU)等，在此不做限制。
S904、目标接入网设备确定第一终端设备建立第一包头压缩上下文，恢复使用第一包头压缩上下文对数据包的包头进行压缩或解压缩。
在一些可行的实施方式中，确定第一终端设备建立第一包头压缩上下文，恢复使用第一包头压缩上下文对数据包的包头进行压缩或解压缩。这里，目标接入网设备确定第一终端设备建好或成功建立某一条头压缩上下文的方式可以是：①目标接入网设备连续发送N次同一头压缩上下文时，即可默认或确定第一终端设备成功建立了该头压缩上下文，或者，②也可以是目标接入网设备接收到第一终端设备针对该压缩上下文的反馈信息时，确定该第一终端设备成功建立了该头压缩上下文，其中反馈信息中包括上下文标识，指示该上下文标识对应的头压缩上下文建立完成。
可选的，在目标接入网设备确定第一终端设备建立第一包头压缩上下文之前，为了不影响MBS业务的正常传输，若目标接入网设备需要发送数据包，则目标接入网设备可以发送包头未经压缩的数据包，直到目标接入网设备确定第一终端设备建立第一包头压缩上下文时，再恢复使用第一包头压缩上下文对数据包的包头进行压缩。
其中，上述恢复使用第一包头压缩上下文对数据包的包头进行压缩可以为：当目标接入网设备确定第一终端设备建立好某一条头压缩上下文时，例如以头压缩上下文1为例进行说明，目标接入网设备可以该头压缩上下文1的状态置为可用状态、生效状态或者重新使能头压缩上下文1，并开始对该头压缩上下文1对应的数据包的包头进行头压缩。依次类推，直到目标接入网设备中所有已经建立好的上下文的状态变为可用、生效或者使能的时候，目标 接入网设备可以针对所有上下文对应的数据包执行头压缩，以发送包头经过压缩的数据包。可理解的，本申请实施例中描述的确定第一终端设备建立或成功建立或建立好一条包头压缩上下文时，针对该建立好的包头压缩上下文对应的数据包进行压缩的过程，可以单独作为一个实施例，或者作为可选步骤与本申请实施例中的一个或多个步骤进行结合，在此不做限制。
由于本申请实施例中第一终端设备的切换，使得目标接入网设备会先暂停使用第一包头压缩上下文对数据包进行压缩，然后向第一终端设备发送第一信息，并在确定第一终端设备根据第一信息建立好对应的第一包头压缩上下文后，再恢复使用第一包头压缩上下文对数据包的包头进行压缩，因此，从空口传输上来看，第一终端设备的切换，会导致使得正在以压缩方式传输MBS数据包的目标接入网设备，转为暂时不使用压缩方式传输MBS数据包，即发送的MBS数据包从包头经过压缩的数据包，变为包头未经过压缩的数据包，然后，当目标接入网设备确定第一终端设备中第一包头压缩上下文建立完成后，又恢复使用第一包头压缩上下文对相应的包头进行压缩，即发送的MBS数据包从包头未经过压缩的数据包，又变为包头经过压缩的数据包。由于该实施例中是暂停使用(而不是停止使用)第一终端设备切换前所使用的头压缩上下文，所以目标接入网设备并不需要重新建立包头压缩上下文，第一包头压缩上下文仍然是第一终端设备切换前所建立好的头压缩上下文。也就是说，从空口传输上来看，第一包头压缩上下文与第一终端设备切换前所使用的头压缩上下文相同，即相同上下文标识对应的上下文信息相同。所以当恢复使用压缩方式传输MBS数据包后，即发送的MBS数据包从包头未经过压缩的数据包，又变为包头经过压缩的数据包后，所使用的压缩上下文与第一终端设备切换前使用的压缩上下文相同。
需要说明的是，对于除第一终端设备之外的其他终端设备，即第一终端设备切换前就在目标接入网设备下接收MBS数据包的终端设备来说，由于第一包头压缩上下文与第一终端设备切换前所建立好的头压缩上下文相同，所以无论目标接入网设备采用PTM还是PTP传输方式发送第一信息，该其他终端设备可以不用执行根据第一信息更新切换前所建立好的头压缩上下文，而是可以继续使用切换前所建立好的头压缩上下文。可选的，若目标接入网设备采用PTM传输方式发送第一信息，则针对第一终端设备切换前就在目标接入网设备下接收MBS数据包的终端设备而言，该其他终端设备也可以执行根据第一信息更新切换前所建立好的头压缩上下文的操作，不过由于该实施例中是暂停使用(而不是停止使用)第一终端设备切换前所使用的头压缩上下文，这些终端设备即使做了更新操作也不会改变对应的头压缩上下文。
可选的，在一些场景下，例如某段时间仅有一个终端设备(例如终端设备3)切换至目标接入网设备的情况而言，假设终端设备3切换到目标接入网设备后，没有等到目标接入网设备的所有头压缩上下文状态全部变为可用，生效或者使能，便又切换到了其他接入网设备，此时为了节省上下文建立开销，需要将上下文状态为不可用，失效或者去使能的头压缩上下文状态恢复为可用，生效或者使能。这是因为除了终端设备3以外，其他终端设备之前已经建立好了上下文，现在终端设备3又切走了，自然应该恢复原状。
示例性地，请参见图10，图10是本申请实施例提供的一种由于切换而影响目标接入网设备中头压缩上下文状态的场景示意图。如图10所示，在t1时刻之前，目标接入网设备与目标接入网设备下面的各个终端设备建立起了相互同步的头压缩上下文(如图10中所示的context1～context3)，因此，目标接入网设备可采用context1～context3对需要传输的数据包进行压缩。在t1时刻，存在某一个终端设备(如图10所示的终端设备3)从源接入网设备成功切换至目标接入网设备，因此，导致目标接入网设备中已建立好的包头压缩上下文(即 context1～context3)全部从可用状态变为不可用状态，因此，目标接入网设备只能发送包头未经压缩的数据包(即全头发送所有数据包)。进一步地，目标接入网设备向终端设备3发送头压缩上下文，并在确定终端设备3建立好或成功建立了任一条上下文时，将目标接入网设备中对应的头压缩上下文状态置为可用，生效或者使能，并开始对该头压缩上下文对应的数据包的包头进行头压缩。如图10中，t2时刻终端设备3成功建立了context1，因此，目标接入网设备可对context1对应的数据包执行压缩，针对终端设备3未创建或未建立好的上下文(如图10中所示的context2和context3)，目标接入网设备不对context2和context3对应的数据包执行压缩，即发送未经压缩的数据包。在t3时刻，终端设备3从目标接入网设备切换到了其他接入网设备(即终端设备3从目标接入网设备切走)，此时，目标接入网设备需要将目标接入网设备中不可用状态的上下文设置或恢复为可用状态，即在t2时刻之后，将context2和context3从不可用状态恢复为可用状态，并采用context1～context3对需要传输的数据包进行压缩。
可选的，在目标接入网设备采用暂停使用或挂起或去使能目标接入网设备中已建立好的包头压缩上下文，直到目标接入网设备确定第一终端设备成功建立任一条第一包头压缩上下文时，再恢复使用该条第一包头压缩上下文对数据包的包头进行压缩的方案的情况下，针对某段时间相继有多个终端设备切换至目标接入网设备的情况而言，目标接入网设备需要根据多个终端设备的切换情况对头压缩上下文状态进行调整，例如假设有两个终端设备切换至目标接入网设备，示例性地，以终端设备1和终端设备2切换过来为例进行示意性说明，则目标接入网设备需要确定这两个终端设备均建立好头压缩上下文，才可以将对应的头压缩上下文状态置为可用，生效或者使能。当目标接入网设备中还存在不可用、或失效或去使能的头压缩上下文时，这两个终端设备中的终端设备1却从目标接入网设备切换走了，那么依然不能恢复那些不可用，失效或去使能的头压缩上下文，这是因为终端设备2还未成功建立这些头压缩上下文。举例来说，假设终端设备1切换来导致上下文1-3不可用，然后终端设备2也切换来，此时即使终端设备1切换走，由于终端设备2的上下文还没有建立好，上下文1-3状态依然为不可用。
可选的，目标接入网设备也可以在确定第一终端设备建立完成第一包头压缩上下文之前就发送经第一包头压缩上下文对包头进行压缩后的数据包，即头压缩数据包，基于此，针对终端设备接收到的头压缩数据包对应的上下文未建立好时，终端设备需要先保存该压缩数据包，等待对应的头压缩上下文建立好以后再对相应的头压缩数据包进行解压缩的描述，以及针对终端设备重复检测过程的描述可以参见上述图7中描述，在此不再进行赘述。
可选的，上述对各个步骤的编号不对方案的执行顺序进行限制。
在本申请实施例中，终端设备切换前，切换过程中或切换后，目标接入网设备对头压缩上下文状态进行相应的改变(即先暂停使用，后续恢复使用)，并根据上下文状态(即是暂停使用状态，还有恢复使用状态)决定是否对相应的数据包执行头压缩，可以实现终端设备在切换后与目标接入网设备保持头压缩上下文的同步，进而能够对接收到的来自目标接入网设备的头压缩数据包进行正确解压缩，有利于提高通信的可靠性。
请参见图11，图11是本申请实施例提供的通信方法的另一流程示意图。如图11所示，该方法包括如下步骤S1101至步骤S1102，其中，图11所示的方法执行主体可以为目标接入网设备，或者，图11所示的方法执行主体也可以为目标接入网设备中的芯片等，在此不做限 制。为方便描述，下面将以目标接入网设备为例进行说明。
S1101、目标接入网设备确定第一终端设备从源接入网设备切换至目标接入网设备。
其中，本申请实施例中对步骤S1101的描述可以参见图5对应的实施例一中对步骤S501的描述，这里不再进行赘述。
S1102、目标接入网设备通过点到点PTP传输方式向第一终端设备发送第一信息。
在一些可行的实施方式中，终端设备(即本申请实施例中描述的第一终端设备)切换到目标接入网设备以后，目标接入网设备可以配置无线承载给终端设备，无线承载包含两条传输路径，一条为PTP传输路径，另一条为PTM传输路径。也就是说，传输包含两条传输路径，一条为PTP传输路径，另一条为PTM传输路径，其中PTP只针对该终端设备传输数据，而PTM针对包含该终端设备在内的多个终端设备传输数据。在本申请实施例中，目标接入网设备可以通过其中一条传输路径(例如PTP或PTM)发送数据包，或者通过两条传输路径(即PTP和PTM)同时发送数据包，相应地，切换至该目标接入网设备的第一终端设备可以通过其中一条传输路径(例如PTP或PTM)接收数据包，或者通过两条传输路径即PTP和PTM)同时接收数据包。本申请实施例中，通过PTM发送的数据包是包头经过压缩的数据包(即压缩数据包)，因此，目标接入网设备下的多个终端设备，即包括切换过来的第一终端设备和原本就在目标接入网设备下接收业务的其他终端设备都可以接收到这些包头经过压缩的数据包。可选的，多个终端设备是接收相同广播组播业务的终端设备。其中，当采用一条传输路径(该传输路径为PTM时)发送第一信息时，由于所有终端设备都可以收到PTM传输路径发送的信息，所以第一信息通过PTM发送会对其他终端设备产生不必要的影响，基于此，本申请实施例提出了对于开启了压缩功能的目标接入网设备而言，目标接入网设备可以通过点到点PTP传输方式向第一终端设备发送第一信息，这种情况下只有第一终端设备可以接收到该第一信息，其他之前就在目标接入网设备下接收MBS业务的终端设备接收不到该第一信息。
其中，该第一信息用于指示第一包头压缩上下文，第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。其中，本申请涉及的数据包可以是MBS业务的数据包，或者，也可以其他业务(例如单播业务，或广播业务，或组播业务等)的数据包等，具体根据实际应用场景确定，在此不做限制。为方便理解，本申请实施例皆以MBS业务的数据包为例进行示意性说明。示例性地，MBS业务可以是直播业务、公共安全业务、批量软件更新业务等，在此不做限制。在本申请实施例中，第一包头压缩上下文应该理解为第一终端设备从源接入网设备切换至目标接入网设备之前，目标接入网设备对数据包的包头进行压缩时所使用的头压缩上下文。
相应地，针对第一终端设备而言，当第一终端设备通过PTP传输方式接收到来自目标接入网设备的第一信息后，第一终端设备可以根据第一信息建立第一包头压缩上下文。可理解的，若源接入网设备本身开启了压缩功能，则第一终端设备根据第一信息建立第一包头压缩上下文可以为：第一终端设备根据第一信息将第一终端设备中已建立的包头压缩上下文更新为第一包头压缩上下文。其中，第一终端设备已建立的包头压缩上下文可以为第一终端设备在源接入网设备下接收MBS业务时，与源接入网设备进行同步的包头压缩上下文。也就是说，第一终端设备可删除第一终端设备在源接入网设备下接收MBS业务时，建立好的头压缩上下文，进而根据从目标接入网设备接收的第一信息建立第一包头压缩上下文。若源接入网设备本身并未开启压缩功能，则第一终端设备在源接入网设备下接收MBS业务时，是没有建立与该MBS业务关联的头压缩上下文的，因此，第一终端设备根据第一信息建立第一包头压缩上下文可以为：第一终端设备根据第一信息在第一终端设备中新增建立第一包头压缩上下文。
可选的，若目标接入网设备可以同时通过PTP和PTM传输路径向终端设备发送数据包，则目标接入网设备可以在通过PTP传输方式向第一终端设备发送第一信息的同时，通过PTM或PTP传输方式发送经第一包头压缩上下文对包头进行压缩后的数据包(即头压缩数据包)，也就是说，目标接入网设备可以并行执行采用PTP传输方式向第一终端设备发送第一信息，和通过PTM传输方式发送头压缩数据包。相应地，终端设备可以并行执行采用PTP和PTM传输方式分别接收第一信息和头压缩数据包。
可选的，若目标接入网设备不支持或不可以同时通过PTP和PTM传输路径向终端设备发送数据包时，或描述为不能并行执行PTP和PTM传输，而是只能通过PTP传输方式发送进行传输，则目标接入网设备可以通过PTP传输方式向第一终端设备发送第一信息，再通过PTP传输方式向第一终端设备发送包头经过压缩的数据包，或者，目标接入网设备也可以先通过PTP传输方式向第一终端设备发送包头经过压缩的数据包，再通过PTP传输方式向第一终端设备发送第一信息，在此不做限制。这样做的好处是可以保该证第一终端设备通过PTP传输方式接收头压缩数据包的进度不慢于其他终端设备通过PTM传输方式接收数据包的进度，这里其他终端设备即原本就在目标接入网设备下接收MBS业务的数据包。可理解的，等到目标接入网设备确定第一终端设备建立好与目标接入网设备相同的头压缩上下文的时候，即目标接入网设备确定第一终端设备中的头压缩上下文与该目标接入网设备中的头压缩上下文完全同步时，目标接入网设备可以通过MAC CE或者RRC信令将第一终端设备的PTP传输方式切换为PTM传输，进而使得第一设备终端可以与其他终端设备一样，通过PTM传输方式接收压缩数据包。
可选的，无论是在目标接入网设备可以同时通过PTP和PTM传输路径向终端设备发送数据包的场景，还是在目标接入网设备只能通过PTP传输路径向终端设备发送数据包的场景，都可能存在当第一终端设备收到头压缩数据包时，该头压缩数据包中携带的上下文标识对应的第一包头压缩上下文并未建立好的情况，即第一终端设备与目标接入网设备间的存在第一包头压缩上下文并未同步。因此，针对未建立好第一包头压缩上下文的第一终端设备而言，第一终端设备先保存该头压缩数据包，等待对应的头压缩上下文建立好以后再对相应的头压缩数据包进行解压缩。或者，也可以理解为第一终端设备接收到该头压缩数据包后，第一终端设备判断可用的头压缩上下文信息(即第一终端设备基于来自目标接入网设备的第一信息所创建的头压缩上下文)中是否存在该头压缩数据包中包括的头压缩上下文标识，其中，可用的头压缩上下文为可以用于数据包的包头进行压缩或解压缩的头压缩上下文信息。一个实施例中，若存在，则根据该头压缩上下文标识对应的头压缩上下文解压缩该头压缩数据包；又一个实施例中，若不存在，则保存该头压缩数据包，直到第一终端设备成功建立该头压缩上下文标识对应的第一头压缩上下文时，再根据头压缩上下文标识对应的第一头压缩上下文解压缩该头压缩数据包。可理解的，上述对于终端设备接收到的头压缩数据包对应的上下文未建立好时，终端设备需要先保存该压缩数据包，等待对应的头压缩上下文建立好以后再对相应的头压缩数据包进行解压缩的描述可以单独作为一个实施例，或者作为可选步骤与本申请实施例中的一个或多个步骤进行结合，在此不做限制。
示例性地，请参见图12，图12是本实施实施例提供的同时通过PTP和PTM传输路径发送数据包的场景示意图。如图12所示，目标接入网设备目标接入网设备可以通过PTP传输方式向切换至目标接入网设备的终端设备(如图12所示的UE1)发送第一信息，或描述为发送第一包头压缩上下文，同时通过PTM传输方式向UE1发送包头经过压缩的数据包(或者描述为通过PTM传输方式向UE1在内所有终端设备发送包头经过压缩的数据包，其中所有 终端设备包括UE1和其他之前就在目标接入网设备下接收MBS业务的终端设备)。此时，针对UE1而言，UE1需要先保存该头压缩数据包，等待对应的头压缩上下文建立好以后再对相应的头压缩数据包进行解压缩。其中，UE1可以通过接收到的压缩数据包中包括的上下文标识确定相应的头压缩上下文是否已经建立好。
可选的，本实施例针对终端设备的重复检测功能而言，当终端设备接收到的数据包的序列号与之前接收的数据包的序列号相同或满足一定偏差或满足某种关联关系时，不能简单地对后面接收到的数据包进行丢弃，而是需要进一步判断两个序列号相同的数据包的包头是否经过了压缩。也就是说，相较于当终端设备接收到的数据包的序列号与之前接收的数据包的序列号相同时，将后面接收到的数据包丢弃的重复检测过程，本申请实施例中终端设备的重复检测过程需要在终端设备接收到多个包括相同序列号或序列号满足一定偏差或序列号满足某种关联关系的数据包时，进一步考虑数据包的包头是否经过了压缩或进一步考虑数据包是从哪个路径接收到的。其中，数据包的序列号可以是PDCP层的序列号，例如，PDCP层的序列号可以是PDCP序列号(PDCP sequence number，PDCP SN)等，或者，序列号也可以是SDAP层的序列号，例如，SDAP层的序列号可以是SDAP SN等，或者序列号也可以是RLC层或MAC层或PHY层的序列号等，在此不做限制。为方便理解，本申请实施例皆以数据包的序列号为PDCP SN号为例进行示意性说明。
举例来说，假设终端设备通过PTM收到一个PDCP SN＝10的头压缩数据包，之后通过PTP接收到一个PDCP SN＝10的全头数据包(用于帮助终端设备建立头压缩上下文)。其中，由于该头压缩数据包中的PDCP SN与该全头数据包中的PDCP SN相同(即PDCP SN都等于10)，因此，终端设备需要进行重复检测。
对于重复检测
方式1：考虑数据包的包头是否经过了压缩
此时一种实现方式是，终端设备判断这两个数据包的包头是否经过了压缩，如果其中一个包头经过了压缩，另一个未压缩，则丢弃压缩的数据包，或描述为或描述为保留未经压缩的数据包，或描述为丢弃压缩的数据包且保留未经压缩的数据包；如果两个都经过了压缩或者都未经过压缩，则丢弃后接收到的数据包，或描述为保留先接收到的数据包，或描述为丢弃后接收到的数据包且保留先接收到的数据包。
方式2：考虑数据包是从哪个路径接收到的
另一种实现方式是，终端设备判断这两个数据包是从哪个传输路径接收到的，如果其中一个从PTM接收到，另一个从PTP接收到，则终端设备丢弃从PTM接收到的数据包；如果两个都是从PTM或者PTP接收到，则丢弃后接收到的数据包等，在此不做限制。
可理解的，上述对于终端设备的重复检测功能的描述可以单独作为一个实施例，或者作为可选步骤与本申请实施例中的一个或多个步骤进行结合，在此不做限制。可理解的，本申请中丢弃这一步骤也可以为可选步骤，即终端设备可以保留未经压缩的数据包或先接收到的数据包，或终端设备跳过(skip)使用经过了压缩的数据包或后接收到的数据包，直接使用未经压缩的数据包或先接收到的数据包等，在此不做限制。
需要说明的是，在实际实现时，本申请实施例中的第一头压缩上下文可携带或承载在包头未经压缩的数据包之中发送给第一接入网设备，或者，也可以理解为将用于指示第一头压缩上下文的第一信息承载在包头未经压缩的数据包中，以发送给第一终端设备。可选的，第一头压缩上下文也可以承载于信令中(或描述为用于指示第一头压缩上下文的第一信息可以承载于信令中)，例如，所涉及的信令可以是MAC CE，或RRC信令，或PDCP control PDU 等，在此不做限制。
可选的，上述用于承载第一信息的包头未经压缩的数据包(或信令)中还可以包括每个包头压缩上下文对应的头压缩上下文标识(为方便描述，也可以简称为上下文标识)等信息，在此不做限制。其中，一个头压缩上下文对应一个上下文标识。因此，当第一终端设备接收到包头未经压缩的数据包或信令之后，第一终端设备可保存第一包头压缩上下文和对应的上下文标识的对应关系，以便后续接收到包头经过压缩的数据包时，根据包头经过压缩的数据包中携带的上下文标识，确定对应的第一包头压缩上下文对头压缩数据包进行解压缩。
在本申请实施中，目标接入网设备在终端设备切换前、切换过程中或切换后可以通过PTP传输帮助终端设备建立头压缩上下文，因此，可保证终端设备在切换后，可以对通过PTP接收到的第一信息建立第一包头压缩上下文，进而能够对接收到的头压缩数据包进行正确的解压缩，有利于提高通信的可靠性。
下面将结合图13～图16对本申请提供的通信装置进行详细说明。
请参见图13，图13是本申请实施例提供的一种通信装置的结构示意图。图13所示的通信装置可以用于执行上述图5～图12所描述的方法实施例中目标接入网设备的部分或全部功能。该装置可以是目标接入网设备，也可以是目标接入网设备中的装置，或者是能够和目标接入网设备匹配使用的装置。其中，该通信装置还可以为芯片系统。图13所示的通信装置可以包括收发单元1301和处理单元1302。其中，处理单元1302，用于进行数据处理。收发单元1301集成有接收单元和发送单元。收发单元1301也可以称为通信单元。或者，也可将收发单元1301拆分为接收单元和发送单元。下文的处理单元1302和收发单元1301同理，下文不再赘述。其中：
在一种实现方式中，处理单元1302，用于确定第一终端设备从源接入网设备切换至所述目标接入网设备；
收发单元1301，用于向所述第一终端设备发送第一信息，所述第一信息用于指示第一包头压缩上下文，所述第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。
该通信装置的其他可能的实现方式，可参见上述图5～图12对应的方法实施例中对接入网设备功能的相关描述，在此不赘述。
请参见图14，图14示出了本申请实施例的一种通信装置的结构示意图。图14所示的通信装置可以用于执行上述图5～图12所描述的方法实施例中终端设备(或描述为第一终端设备)的部分或全部功能。该装置可以是终端设备，也可以是终端设备中的装置，或者是能够和终端设备匹配使用的装置。其中，该通信装置还可以为芯片系统。图14所示的通信装置可以包括收发单元1401和处理单元1402。其中：
在一种实现方式中，处理单元1402，用于从源接入网设备切换至目标接入网设备；
收发单元1401，用于接收来自所述目标接入网设备的第一信息，所述第一信息用于指示第一包头压缩上下文，所述第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。
该通信装置的其他可能的实现方式，可参见上述图5～图12对应的方法实施例中对接入网设备功能的相关描述，在此不赘述。
请参见图15，图15是本申请实施例提供的另一种通信装置的结构示意图。如图15所示，该通信装置可以为本申请实施例中描述的目标接入网设备，用于实现上述图5～图12中目标 接入网设备的功能。该目标接入网设备15包括：基带装置151，射频装置152、天线153。在上行方向上，射频装置152通过天线153接收终端设备发送的信息，将终端设备发送的信息发送给基带装置151进行处理。在下行方向上，基带装置151对终端设备的信息进行处理，并发送给射频装置152，射频装置152对终端设备的信息进行处理后经过天线151发送给终端设备。
基带装置151包括一个或多个处理单元1511，存储单元1512和接口1513。其中处理单元1511用于支持目标接入网设备执行上述方法实施例中目标接入网设备的功能。存储单元1512用于存储软件程序和/或数据。接口1513用于与射频装置152交互信息，该接口包括接口电路，用于信息的输入和输出。在一种实现中，所述处理单元为集成电路，例如一个或多个ASIC，或，一个或多个DSP，或，一个或者多个FPGA，或者这些类集成电路的组合。这些集成电路可以集成在一起，构成芯片。存储单元1512与处理单元1511可以位于同一个芯片中，即片内存储元件。或者存储单元1512与处理单元1511也可以为与处理单元1511处于不同芯片上，即片外存储元件。所述存储单元1512可以是一个存储器，也可以是多个存储器或存储元件的统称。
目标接入网设备可以通过一个或多个处理单元调度程序的形式实现上述方法实施例中的部分或全部步骤。例如实现图5，图7，图9，和/或图11中目标接入网设备的相应的功能。所述一个或多个处理单元可以支持同一种制式的无线接入技术，也可以支持不同种制式的无线接入制式。
请参见图16，图16是本申请实施例提供的另一种通信装置的结构示意图。如图16所示，该通信装置可以为本申请实施例中描述的终端设备，用于实现上述图5～图12中终端设备的功能。为了便于说明，图16仅示出了终端设备1600的主要部件。如图16所示，终端设备1600包括处理器、存储器、控制电路、天线以及输入输出装置。处理器主要用于对通信协议以及通信数据进行处理，以及对整个终端设备1600进行控制，执行软件程序，处理软件程序的数据。存储器主要用于存储软件程序和数据。控制电路主要用于基带信号与射频信号的转换以及对射频信号的处理。天线主要用于收发电磁波形式的射频信号。输入输出装置，例如触摸屏，显示屏，麦克风，键盘等主要用于接收用户输入的数据以及对用户输出数据。
以终端设备1600为手机为例，当终端设备1600开机后，处理器可以读取存储单元中的软件程序，解释并执行软件程序的指令，处理软件程序的数据。当需要通过无线发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至控制电路，控制电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端设备1600时，控制电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。
本领域技术人员可以理解，为了便于说明，图16仅示出了一个存储器和处理器。在一些实施例中，终端设备1600可以包括多个处理器和存储器。存储器也可以称为存储介质或者存储设备等，本发明实施例对此不做限制。
作为一种可选的实现方式，处理器可以包括基带处理器和中央处理器，基带处理器主要用于对通信协议以及通信数据进行处理，中央处理器主要用于对整个终端设备1600进行控制，执行软件程序，处理软件程序的数据。图16中的处理器集成了基带处理器和中央处理器的功能，本领域技术人员可以理解，基带处理器和中央处理器也可以是各自独立的处理器，通过总线等技术互联。终端设备1600可以包括多个基带处理器以适应不同的网络制式，终端设备 1600可以包括多个中央处理器以增强其处理能力，终端设备1600的各个部件可以通过各种总线连接。所述基带处理器也可以表述为基带处理电路或者基带处理芯片。所述中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中，也可以以软件程序的形式存储在存储单元中，由处理器执行软件程序以实现基带处理功能。
在一个例子中，可以将具有收发功能的天线和控制电路视为终端设备1600的收发单元1610，将具有处理功能的处理器视为终端设备1600的处理单元1620。如图16所示，终端设备1600包括收发单元1610和处理单元1620。收发单元也可以称为收发器、收发机、收发装置等。可选的，可以将收发单元1610中用于实现接收功能的器件视为接收单元，将收发单元1610中用于实现发送功能的器件视为发送单元，即收发单元1610包括接收单元和发送单元。示例性的，接收单元也可以称为接收机、接收器、接收电路等，发送单元可以称为发射机、发射器或者发射电路等。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在处理器上运行时，上述方法实施例的方法流程得以实现。
本申请实施例还提供一种计算机程序产品，当所述计算机程序产品在处理器上运行时，上述方法实施例的方法流程得以实现。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的计算机可读存储介质，可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括随机存取存储器(random access memory，RAM)、只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦可编程只读存储器(electrically erasable programmable read only memory，EEPROM)、紧凑型光盘只读存储器(compact disc read-only memory，CD-ROM)、通用串行总线闪存盘(universal serial bus flash disk)、移动硬盘、或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。另外，通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率 同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)或直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
以上所述，仅为本申请的具体实施方式，但本申请实施例的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请实施例揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请实施例的保护范围之内。因此，本申请实施例的保护范围应所述以权利要求的保护范围为准。

Claims (38)

  1. 一种通信方法，其特征在于，包括：
    确定第一终端设备从源接入网设备切换至目标接入网设备；
    向所述第一终端设备发送第一信息，所述第一信息用于指示第一包头压缩上下文，所述第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    停止使用所述第一终端设备从所述源接入网设备切换至所述目标接入网设备之前，所述目标接入网设备对数据包的包头进行压缩或解压缩时所使用的头压缩上下文；
    建立所述第一包头压缩上下文。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    暂停使用所述第一包头压缩上下文对数据包的包头进行压缩，所述第一包头压缩上下文为所述第一终端设备从所述源接入网设备切换至所述目标接入网设备之前，所述目标接入网设备对数据包的包头进行压缩或解压缩时所使用的头压缩上下文。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    确定所述第一终端设备建立所述第一包头压缩上下文；
    恢复使用所述第一包头压缩上下文对数据包的包头进行压缩或解压缩。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    接收来自所述第一终端设备的反馈信息，所述反馈信息用于指示所述第一终端设备建立所述第一包头压缩上下文；
    所述确定所述第一终端设备建立所述第一包头压缩上下文，包括：
    根据所述反馈信息，确定所述第一终端设备建立所述第一包头压缩上下文。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，所述向所述第一终端设备发送第一信息，包括：
    通过点到点PTP传输方式向所述第一终端设备发送所述第一信息。
  7. 根据权利要求6所述的方法，其特征在于，所述通过PTP传输方式向所述第一终端设备发送所述第一信息，包括：
    通过PTP传输方式向所述第一终端设备发送媒体接入控制控制元素MAC CE，所述MAC CE中包括所述第一信息；或者
    通过PTP传输方式向所述第一终端设备发送无线资源控制RRC信令，所述RRC信令中包括所述第一信息。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，所述方法还包括：
    通过点到多点PTM传输方式和/或点到点PTP传输方式向所述第一终端设备发送包头经过压缩的数据包。
  9. 根据权利要求1-8中任一项所述的方法，其特征在于，所述向所述第一终端设备发送第一信息，包括：
    通过所述源接入网设备向所述第一终端设备发送所述第一信息，所述第一信息承载于切换命令。
  10. 一种通信方法，其特征在于，包括：
    从源接入网设备切换至目标接入网设备；
    接收来自所述目标接入网设备的第一信息，所述第一信息用于指示第一包头压缩上下文，所述第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    向所述目标接入网设备发送反馈信息，所述反馈信息用于指示第一终端设备建立所述第一包头压缩上下文。
  12. 根据权利要求10或11所述的方法，其特征在于，所述接收来自所述目标接入网设备的第一信息，包括：
    通过点到点PTP传输方式接收来自所述目标接入网设备的所述第一信息。
  13. 根据权利要求12所述的方法，其特征在于，所述通过PTP传输方式接收来自所述目标接入网设备的所述第一信息，包括：
    通过PTP传输方式接收来自所述目标接入网设备的媒体接入控制控制元素MAC CE，所述MAC CE中包括所述第一信息；或者
    通过PTP传输方式接收来自所述目标接入网设备的无线资源控制RRC信令，所述RRC信令中包括所述第一信息。
  14. 根据权利要求10-13中任一项所述的方法，其特征在于，所述方法还包括：
    通过点到多点PTM传输方式和/或所述PTP传输方式接收来自所述目标接入网设备，且包头经过压缩的数据包。
  15. 根据权利要求10-14中任一项所述的方法，其特征在于，所述第一头压缩上下文承载于包头未经压缩的数据包之中，所述包头未经压缩的数据包对应第一序列号，所述包头经过压缩的数据包对应第二序列号，所述第一序列号和所述第二序列号相同；
    所述方法还包括：
    丢弃所述包头经过压缩的数据包。
  16. 根据权利要求10-14中任一项所述的方法，其特征在于，所述包头经过压缩的数据包中包括头压缩上下文标识；所述方法还包括：
    在所述第一终端设备建立所述头压缩上下文标识对应的第一头压缩上下文之前，保存所述包头经过压缩的数据包；
    根据所述头压缩上下文标识对应的第一头压缩上下文解压缩所述包头经过压缩的数据包。
  17. 根据权利要求10-16中任一项所述的方法，其特征在于，所述接收来自所述目标接入网设备的第一信息，包括：
    接收所述目标接入网设备通过所述源接入网设备发送的第一信息，所述第一信息承载于切换命令。
  18. 一种通信装置，其特征在于，所述通信装置为目标接入网设备，包括：
    处理单元，用于确定第一终端设备从源接入网设备切换至所述目标接入网设备；
    收发单元，用于向所述第一终端设备发送第一信息，所述第一信息用于指示第一包头压缩上下文，所述第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。
  19. 根据权利要求18所述的装置，其特征在于，所述处理单元还用于：
    停止使用所述第一终端设备从所述源接入网设备切换至所述目标接入网设备之前，所述目标接入网设备对数据包的包头进行压缩或解压缩时所使用的头压缩上下文；
    建立所述第一包头压缩上下文。
  20. 根据权利要求18所述的装置，其特征在于，所述处理单元还用于：
    暂停使用所述第一包头压缩上下文对数据包的包头进行压缩，所述第一包头压缩上下文为所述第一终端设备从所述源接入网设备切换至所述目标接入网设备之前，所述目标接入网设备对数据包的包头进行压缩或解压缩时所使用的头压缩上下文。
  21. 根据权利要求20所述的装置，其特征在于，所述处理单元还用于：
    确定所述第一终端设备建立所述第一包头压缩上下文；
    恢复使用所述第一包头压缩上下文对数据包的包头进行压缩或解压缩。
  22. 根据权利要求21所述的装置，其特征在于，
    所述收发单元，还用于接收来自所述第一终端设备的反馈信息，所述反馈信息用于指示所述第一终端设备建立所述第一包头压缩上下文；
    所述处理单元，还用于根据所述反馈信息，确定所述第一终端设备建立所述第一包头压缩上下文。
  23. 根据权利要求18-22中任一项所述的装置，其特征在于，所述收发单元用于：
    通过点到点PTP传输方式向所述第一终端设备发送所述第一信息。
  24. 根据权利要求23所述的装置，其特征在于，所述收发单元具体用于：
    通过PTP传输方式向所述第一终端设备发送媒体接入控制控制元素MAC CE，所述MAC CE中包括所述第一信息；或者
    通过PTP传输方式向所述第一终端设备发送无线资源控制RRC信令，所述RRC信令中包括所述第一信息。
  25. 根据权利要求18-24中任一项所述的装置，其特征在于，所述收发单元还用于：
    通过点到多点PTM传输方式和/或点对点PTP传输方式向所述第一终端设备发送包头经 过压缩的数据包。
  26. 根据权利要求18-25中任一项所述的装置，其特征在于，所述收发单元还用于：
    通过所述源接入网设备向所述第一终端设备发送所述第一信息，所述第一信息承载于切换命令。
  27. 一种通信装置，其特征在于，所述通信装置为第一终端设备，包括：
    处理单元，用于从源接入网设备切换至目标接入网设备；
    收发单元，用于接收来自所述目标接入网设备的第一信息，所述第一信息用于指示第一包头压缩上下文，所述第一包头压缩上下文用于对数据包的包头进行压缩或解压缩。
  28. 根据权利要求27所述的装置，其特征在于，所述收发单元还用于：
    向所述目标接入网设备发送反馈信息，所述反馈信息用于指示所述第一终端设备建立所述第一包头压缩上下文。
  29. 根据权利要求27或28所述的装置，其特征在于，所述收发单元用于：
    通过点到点PTP传输方式接收来自所述目标接入网设备的所述第一信息。
  30. 根据权利要求29所述的装置，其特征在于，所述收发单元具体用于：
    通过PTP传输方式接收来自所述目标接入网设备的媒体接入控制控制元素MAC CE，所述MAC CE中包括所述第一信息；或者
    通过PTP传输方式接收来自所述目标接入网设备的无线资源控制RRC信令，所述RRC信令中包括所述第一信息。
  31. 根据权利要求27-30中任一项所述的装置，其特征在于，所述收发单元还用于：
    通过点到多点PTM传输方式和/或所述PTP传输方式接收来自所述目标接入网设备，且包头经过压缩的数据包。
  32. 根据权利要求27-31中任一项所述的装置，其特征在于，所述第一头压缩上下文承载于包头未经压缩的数据包之中，所述包头未经压缩的数据包对应第一序列号，所述包头经过压缩的数据包对应第二序列号，所述第一序列号和所述第二序列号相同；
    所述处理单元还用于：
    丢弃所述包头经过压缩的数据包。
  33. 根据权利要求27-31中任一项所述的装置，其特征在于，所述包头经过压缩的数据包中包括头压缩上下文标识；所述处理单元还用于：
    在所述第一终端设备建立所述头压缩上下文标识对应的第一头压缩上下文之前，保存所述包头经过压缩的数据包；
    根据所述头压缩上下文标识对应的第一头压缩上下文解压缩所述包头经过压缩的数据包。
  34. 根据权利要求27-33中任一项所述的装置，其特征在于，所述收发单元还用于：
    接收所述目标接入网设备通过所述源接入网设备发送的第一信息，所述第一信息承载于切换命令。
  35. 一种通信装置，其特征在于，所述通信装置为目标接入网设备，包括处理器和收发器，所述处理器和所述收发器用于执行至少一个存储器中存储的计算机程序或指令，以使得所述装置实现如权利要求1～9中任一项所述的方法。
  36. 一种通信装置，其特征在于，所述通信装置为第一终端设备，包括处理器和收发器，所述处理器和所述收发器用于执行至少一个存储器中存储的计算机程序或指令，以使得所述装置实现如权利要求10～17中任一项所述的方法。
  37. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被计算机执行时，实现如权利要求1～9中任一项所述的方法，或，实现如权利要求10～17中任一项所述的方法。
  38. 一种计算机程序产品，其特征在于，所述计算机程序产品中包括计算机程序代码，当所述计算机程序代码在计算机上运行时，以实现权利要求1～9中任一项所述的方法，或以实现如权利要求10～17中任一项所述的方法。
PCT/CN2022/098589 2021-08-05 2022-06-14 通信方法及通信装置 WO2023011004A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22851720.7A EP4358579A1 (en) 2021-08-05 2022-06-14 Communication method and communication apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110898747.3A CN115915265A (zh) 2021-08-05 2021-08-05 通信方法及通信装置
CN202110898747.3 2021-08-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/427,829 Continuation US20240179560A1 (en) 2021-08-05 2024-01-31 Communication method and communication apparatus

Publications (1)

Publication Number Publication Date
WO2023011004A1 true WO2023011004A1 (zh) 2023-02-09

Family

ID=85154248

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/098589 WO2023011004A1 (zh) 2021-08-05 2022-06-14 通信方法及通信装置

Country Status (3)

Country Link
EP (1) EP4358579A1 (zh)
CN (1) CN115915265A (zh)
WO (1) WO2023011004A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117062257A (zh) * 2023-10-11 2023-11-14 腾讯科技（深圳）有限公司 基于多通道的数据传输方法、终端设备以及目标网关

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1655536A (zh) * 2004-02-12 2005-08-17 三星电子株式会社 在多媒体广播/多播业务系统中恢复报头解压缩的方法
CN111742577A (zh) * 2019-01-25 2020-10-02 联发科技（新加坡）私人有限公司 用于移动性增强的双协议
CN112930695A (zh) * 2018-10-31 2021-06-08 苹果公司 在切换期间路径转变之后的鲁棒标头压缩指示

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1655536A (zh) * 2004-02-12 2005-08-17 三星电子株式会社 在多媒体广播/多播业务系统中恢复报头解压缩的方法
CN112930695A (zh) * 2018-10-31 2021-06-08 苹果公司 在切换期间路径转变之后的鲁棒标头压缩指示
CN111742577A (zh) * 2019-01-25 2020-10-02 联发科技（新加坡）私人有限公司 用于移动性增强的双协议

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INC: "DAPS handover UP remaining key issues", 3GPP DRAFT; R2-2004947, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. E-Meeting; 20200601 - 20200609, 22 May 2020 (2020-05-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051888481 *
SHARP: "RoHC handling for inter-gNB and intra-gNB DAPS handover", 3GPP DRAFT; R2-2003665, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online Meeting ;20200420 - 20200430, 10 April 2020 (2020-04-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051871567 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117062257A (zh) * 2023-10-11 2023-11-14 腾讯科技（深圳）有限公司 基于多通道的数据传输方法、终端设备以及目标网关
CN117062257B (zh) * 2023-10-11 2024-02-09 腾讯科技（深圳）有限公司 基于多通道的数据传输方法、终端设备以及目标网关

Also Published As

Publication number Publication date
CN115915265A (zh) 2023-04-04
EP4358579A1 (en) 2024-04-24

Similar Documents

Publication Publication Date Title
US11546811B2 (en) Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
US10925106B2 (en) Mobile communication system, control apparatus, base station, and user terminal supporting dual connectivity
JP7043506B2 (ja) ロングタームエボリューション通信システムのためのマルチテクノロジアグリゲーションアーキテクチャ
WO2019029643A1 (zh) 通信方法、基站、终端设备和系统
EP3447978A1 (en) Data transmission method and device
WO2014110810A1 (zh) 传输数据的方法、基站和用户设备
EP3664507B1 (en) Communication methods for a master base station and a terminal
WO2015032043A1 (zh) 传输数据的方法、装置和系统
JP2017508364A (ja) セカンダリ基地局及びマスター基地局によって実行される通信方法、並びに対応する基地局
US20230180027A1 (en) User plane data processing method and base station
WO2022110168A1 (zh) 通信配置的方法和通信装置
EP4171074A1 (en) Communication method and communication apparatus
WO2022052851A1 (zh) 一种服务质量QoS的监测方法
WO2021185350A1 (zh) 一种通信方法、接入网设备、终端设备和核心网设备
CN115699816A (zh) 用于在双连接下进行侧行链路中继通信的方法
WO2023011004A1 (zh) 通信方法及通信装置
CN112470544A (zh) 终端装置、基站装置以及方法
WO2021208863A1 (zh) 数据传输方法及通信装置
CN117121556A (zh) 用于时间敏感联网的切换技术
US20240179560A1 (en) Communication method and communication apparatus
WO2022206418A1 (zh) 通信方法及通信装置
WO2023185608A1 (zh) 一种数据传输的方法及通信装置
WO2023078321A1 (zh) 一种通信方法及装置
WO2020164614A1 (zh) 一种辅助信息及其传递的方法和装置
WO2023155763A1 (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: 22851720

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022851720

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022851720

Country of ref document: EP

Effective date: 20240116

NENP Non-entry into the national phase

Ref country code: DE