WO2022205191A1 - 一种pdcp实体的接收窗口的配置方法及其装置 - Google Patents

一种pdcp实体的接收窗口的配置方法及其装置 Download PDF

Info

Publication number
WO2022205191A1
WO2022205191A1 PCT/CN2021/084700 CN2021084700W WO2022205191A1 WO 2022205191 A1 WO2022205191 A1 WO 2022205191A1 CN 2021084700 W CN2021084700 W CN 2021084700W WO 2022205191 A1 WO2022205191 A1 WO 2022205191A1
Authority
WO
WIPO (PCT)
Prior art keywords
value
receiving window
pdcp entity
variable
terminal device
Prior art date
Application number
PCT/CN2021/084700
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 CN202180000755.XA priority Critical patent/CN115552930B/zh
Priority to PCT/CN2021/084700 priority patent/WO2022205191A1/zh
Priority to US18/552,569 priority patent/US20240179729A1/en
Priority to EP21933855.5A priority patent/EP4319211A4/en
Publication of WO2022205191A1 publication Critical patent/WO2022205191A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and apparatus for configuring a receiving window of a PDCP entity.
  • the terminal device When the terminal device starts to receive the service data of the Multicast Broadcast Service (MBS), the terminal device needs to first establish the Packet Data Convergence Protocol (Packet Data) of the radio bearer (MBS Radio Bearer, MRB) corresponding to the received MBS service data.
  • Packet Data Packet Data Convergence Protocol
  • MRB Radio Bearer
  • PDCP Convergence Protocol
  • the boundary value of the PDCP receiving window cannot be updated in real time based on the number value of the PDCP sending window, so that when a new UE joins to receive the MBS service, the MBS service data cannot be received.
  • the embodiments of the present application provide a method and device for configuring a receiving window of a PDCP entity, which can be used to solve the problems of low reliability and poor continuity of MBS service data transmission in the related art.
  • an embodiment of the present application proposes a method for configuring a receiving window of a PDCP entity.
  • the method is executed by a terminal device.
  • the method includes: determining an adjustment parameter corresponding to a variable of the receiving window of the PDCP entity; based on the adjustment parameter, configure the variable of the receiving window of the PDCP entity.
  • the terminal device determines the adjustment parameters corresponding to the variables of the receiving window of the PDCP entity, and realizes the adjustment and configuration of the receiving window variables of the PDCP entity based on the obtained adjustment parameters.
  • the variable of the receiving window of the PDCP entity is adjusted based on the received adjustment parameters, so that the variable of the receiving window of the PDCP entity can be updated in time, so that new terminal equipment can join to receive MBS data at any time, ensuring that the MBS Continuity and reliability of data transmission.
  • a method for configuring a receiving window of a PDCP entity proposed in the first aspect of the present application may also have the following technical features:
  • the determining the variable adjustment parameter of the receiving window of the PDCP entity includes: receiving indication information sent by a network device, where the indication information carries the adjustment parameter.
  • the method for configuring the receiving window of the PDCP entity further includes: in response to the adjustment parameter including the window length and/or boundary value of the receiving window, according to the window length and/or boundary value, configure the variable of the receiving window.
  • the method for configuring the receiving window of the PDCP entity further includes: in response to the boundary value being a candidate lower boundary value of the receiving window, configuring the lower boundary value of the receiving window to be the selected lower boundary value. the candidate lower boundary value.
  • the method for configuring the receiving window of the PDCP entity further includes: in response to the boundary value being an upper boundary value of the receiving window, according to the window length and the target upper boundary value, A candidate lower boundary value of the receiving window is determined, and the lower boundary value of the receiving window is configured as the candidate lower boundary value.
  • the method for configuring the receiving window of the PDCP entity further includes: in response to the adjustment parameter including the candidate number value of the service data unit SDU of the next PDCP entity to be received, configuring the receiving window The number value of the SDU of the next PDCP entity to be received is configured as the candidate number value.
  • the method for configuring the receiving window of the PDCP entity further includes: in response to the adjustment parameter including the HFN value, determining the SN value in the packet header of the first PDCP data packet received by the PDCP entity;
  • the variables of the receiving window are configured according to the HFN value and the SN value.
  • the configuring the variable of the receiving window according to the HFN value and the SN value includes: configuring the HFN part of the variable of the receiving window according to the HFN value; SN value, configure the SN part of the variable of the receiving window.
  • the configuring the HFN part of the variable of the receiving window according to the HFN value includes: setting the lower boundary value of the receiving window and/or the number value of the next PDCP SDU to be received The HFN part, configured as the HFN value.
  • the configuring the SN part of the variable of the receiving window according to the SN value includes: determining a first sum of the SN value and a first target value; according to the first sum The value configures the SN part of the variable of the receive window.
  • the configuring the SN part of the variable of the receiving window according to the first sum value includes: in response to a target condition satisfied by the first sum value, determining a corresponding target condition corresponding to the target condition.
  • Candidate configuration value configure the lower boundary value of the receiving window and/or the SN part of the number value of the next PDCP SDU to be received as the candidate configuration value.
  • the determining the target configuration value corresponding to the target condition in response to the target condition satisfied by the first sum value includes: in response to the first sum value satisfying the target configuration value greater than the SN value
  • the target condition of the maximum allowable value of the SN value is determined as the candidate configuration value; or, in response to the first sum value satisfying the target condition less than the zero value, the maximum allowable value of the SN value, the first a second sum value of the sum value and a second target value, the second sum value being used to determine the candidate configuration value; or, in response to the first sum value satisfying a target condition greater than half of the maximum allowable value,
  • the first sum value is used to determine the candidate configuration value.
  • the method for configuring the receiving window of the PDCP entity further includes: determining the number value carried in the header of the first PDCP data packet received by the PDCP entity as the adjustment parameter; The number value carried in the packet header is used to configure the variable of the receiving window.
  • configuring the variable of the receiving window according to the serial number value carried in the packet header includes: setting the lower boundary value of the receiving window and/or the SDU of the next PDCP entity to be received
  • the serial number value is configured as the serial number value carried in the packet header; or, determine the third sum of the serial number value carried in the packet header and the third target value, and set the lower boundary value of the receiving window and/or the next
  • the number value of the SDU of the PDCP entity to be received is configured as the third sum value.
  • the receiving the indication information sent by the network device includes: receiving a broadcast message or a broadcast multicast service MBS control channel message, where the broadcast message or the MBS control channel message is used to carry the indication information .
  • the method before the determining the adjustment parameter corresponding to the variable of the receiving window of the PDCP entity, the method further includes: determining a trigger event that satisfies the adjustment of the variable of the receiving window; wherein the trigger event is one of the following events At least one of: receiving an adjustment instruction sent by a network device, where the adjustment instruction is used to instruct the terminal device to adjust the variable of the receiving window; or, create a new PDCP entity for the MBS radio bearer MRB; or, rebuild or reconfigure PDCP entity of MRB.
  • an embodiment of the present application further proposes a method for configuring a receiving window of a PDCP entity, the method is executed by a network device, and the method includes: configuring adjustment parameters corresponding to variables of the receiving window of the PDCP entity; Sending indication information, wherein the indication information is used to instruct the terminal device to configure the variable of the receiving window of the PDCP entity based on the adjustment parameter, and the indication information carries the adjustment parameter.
  • a method for configuring a receiving window of a PDCP entity proposed in the second aspect of the present application may also have the following technical features:
  • the adjustment parameter includes a window length and/or a boundary value of the receiving window.
  • the adjustment parameter includes a candidate number value of the service data unit SDU of the PDCP entity to be received next.
  • the adjustment parameter includes an HFN value.
  • the adjustment parameter includes a serial number value carried in the packet header of the first PDCP data packet received by the PDCP entity.
  • the sending the indication information to the terminal device includes: sending a broadcast message or a broadcast multicast service MBS control channel message to the terminal device, wherein the broadcast message or the MBS control channel message is used to carry the Instructions.
  • the method before the sending the indication information to the terminal device, the method further includes: sending to the terminal device an adjustment instruction for instructing the terminal device to adjust the variable of the receiving window.
  • an embodiment of the present application provides an apparatus for configuring a receiving window of a PDCP entity, and the apparatus has part or all of the functions of a terminal device in the method described in the first aspect above, such as an apparatus for configuring a receiving window of a PDCP entity
  • the functions of the device may have the functions of some or all of the embodiments in this application, and may also have the functions of independently implementing any of the embodiments of this application.
  • the functions can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform the corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may further include a storage module for coupling with the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.
  • the processing module may be a processor
  • the transceiver module may be a transceiver or a communication interface
  • the storage module may be a memory
  • an embodiment of the present application proposes an apparatus for configuring a receiving window of a PDCP entity, and the apparatus has part or all of the functions of a network device in the method described in the second aspect, such as an apparatus for configuring a receiving window of a PDCP entity
  • the functions of the device may have the functions of some or all of the embodiments in this application, and may also have the functions of independently implementing any of the embodiments of this application.
  • the functions can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the apparatus for configuring the receiving window of the PDCP entity may include a transceiver module and a processing module, and the processing module is configured to support the communication apparatus to perform the corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may further include a storage module for coupling with the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.
  • the processing module may be a processor
  • the transceiver module may be a transceiver or a communication interface
  • the storage module may be a memory
  • an embodiment of the present application provides a communication device, the communication device includes a processor, and when the processor calls a computer program in a memory, the method described in the first aspect is executed.
  • an embodiment of the present application provides a communication device, where the communication device includes a processor, and when the processor invokes a computer program in a memory, the method described in the second aspect above is executed.
  • an embodiment of the present application provides a communication device, the device includes a processor and a memory, where a computer program is stored in the memory, and the processor executes the computer program stored in the memory, so that the The apparatus performs the method described in the first aspect above.
  • an embodiment of the present application provides a communication device, the device includes a processor and a memory, a computer program is stored in the memory, and the processor executes the computer program stored in the memory, so that the The apparatus performs the method described in the second aspect above.
  • an embodiment of the present application provides a communication device, including: a processor and an interface circuit; the interface circuit is configured to receive code instructions and transmit them to the processor; the processor is configured to run the Code instructions to perform the method described in the first aspect above.
  • the present application provides a communication device, comprising: a processor and an interface circuit; the interface circuit is configured to receive a code instruction and transmit it to the processor; the processor is configured to execute the code instruction to perform the method described in the second aspect above.
  • an embodiment of the present application provides a communication system, where the system includes the communication device described in the third aspect and the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect and The communication device of the sixth aspect, or the system includes the communication device of the seventh aspect and the communication device of the eighth aspect, or the system includes the communication device of the ninth aspect and the tenth aspect. the communication device described.
  • an embodiment of the present application provides a computer-readable storage medium for storing instructions, and when the instructions are executed, the method described in the first aspect above is implemented.
  • an embodiment of the present application provides a computer-readable storage medium for storing instructions, and when the instructions are executed, the method described in the second aspect above is implemented.
  • the present application further provides a computer program product comprising a computer program, which, when run on a computer, causes the computer to execute the method described in the first aspect.
  • the present application further provides a computer program product comprising a computer program, which, when run on a computer, causes the computer to execute the method described in the second aspect above.
  • the present application proposes a chip system
  • the chip system includes at least one processor and an interface for supporting a terminal device to implement the functions involved in the first aspect, for example, determining or processing data involved in the above method and at least one of information.
  • the chip system further includes a memory for storing necessary computer programs and data of the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present application provides a chip system
  • the chip system includes at least one processor and an interface for supporting a network device to implement the functions involved in the second aspect, for example, determining or processing data involved in the above method and at least one of information.
  • the chip system further includes a memory for storing necessary computer programs and data of the network device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present application provides a computer program, which, when executed on a computer, causes the computer to execute the method described in the first aspect.
  • the present application provides a computer program, which, when executed on a computer, causes the computer to execute the method described in the second aspect above.
  • FIG. 1 is a schematic diagram of the architecture of a communication system proposed by an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to an embodiment of the present application
  • FIG. 3 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application
  • FIG. 4 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application
  • FIG. 5 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application
  • FIG. 6 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application
  • FIG. 7 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application.
  • FIG. 10 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application.
  • FIG. 11 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application.
  • FIG. 12 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application.
  • FIG. 13 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of an apparatus for configuring a receiving window of a PDCP entity according to an embodiment of the present application
  • 15 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • 16 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • Multicast Broadcast Service (MBS)
  • the MBS can be sent through the Physical Downlink Shared Channel (PDSCH) scheduled by the Physical Downlink Control Channel (PDCCH), and the PDCCH for scheduling the MBS service can be indicated by the specific scheduling identifier of the MBS service.
  • PDSCH Physical Downlink Shared Channel
  • PDCCH Physical Downlink Control Channel
  • G-RNTI Group Radio Network Temporary Identity
  • PDCP Packet Data Convergence Protocol
  • PDCP Packet Data Convergence Protocol
  • RRC Radio Resource Management
  • IP Internet Protocol
  • the PDCP sublayer also provides in-order submission and duplicate packet detection functions to upper layers.
  • the PDCP sublayer provides signaling transmission services for the upper-layer RRC, and implements encryption and consistency protection of RRC signaling, as well as decryption and consistency checking of RRC signaling in the reverse direction.
  • FIG. 1 is a schematic structural diagram of a communication system proposed by an embodiment of the present application.
  • the communication system may include, but is not limited to, a network device and a terminal device.
  • the number and shape of the devices shown in FIG. 1 are only for examples and do not constitute limitations to the embodiments of the present application. In practical applications, two or more devices may be included. network equipment, two or more terminal equipment.
  • the communication system shown in FIG. 1 includes a network device 101 and a terminal device 102 as an example.
  • LTE long term evolution
  • 5G fifth generation
  • NR 5G new radio
  • the network device 101 in this embodiment of the present application is an entity on the network side for transmitting or receiving signals.
  • the network device 101 may be an evolved base station (evolved NodeB, eNB), a transmission point (transmission reception point, TRP), a next generation base station (next generation NodeB, gNB) in an NR system, or a base station in other future mobile communication systems Or an access node in a wireless fidelity (WiFi) system, etc.
  • the embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.
  • the network device proposed in the embodiments of the present application may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU).
  • the structure of the network equipment such as the protocol layer of the base station, can be split, and the functions of some protocol layers are centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the CU centrally controls the DU.
  • the terminal device 102 in this embodiment of the present application is an entity on the user side that is used to receive or transmit signals, such as a mobile phone.
  • a terminal device may also be referred to as a terminal device (terminal), a user equipment (UE), a mobile station (mobile station, MS), a mobile terminal device (mobile terminal, MT), and the like.
  • the terminal device can be a car with a communication function, a smart car, a mobile phone (mobile phone), a wearable device, a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, augmented reality (augmented reality (AR) terminal equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical surgery, smart grid ( Wireless terminal equipment in smart grid), wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, wireless terminal equipment in smart home, etc.
  • the embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal device.
  • FIG. 2 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to an embodiment of the present application. The method is executed by a terminal device. As shown in FIG. 2 , the method includes:
  • S201 Determine an adjustment parameter corresponding to a variable of a receiving window of the PDCP entity.
  • the PDCP is divided into a receiving entity for data reception and a transmitting entity for data transmission.
  • the receiving entity of PDCP can reorder the data packets of the received PDU according to the order of the PDCP number value (COUNT). After the reordering
  • COUNT PDCP number value
  • the PDCP data packets can be sequentially delivered to the high-level protocol entity according to COUNT.
  • the PDCP entity can implement data encryption and decryption, timer discarding, retransmission and reordering during re-establishment.
  • variable of the receiving window of the PDCP entity may include at least one of the following: the lower boundary of the receiving window, marked as "RX_NEXT”, the COUNT of the service data unit (Server Data Unit, SDU) of the PDCP entity to be received next value, marked as "RX_DELIV", the Hyper Frame Number (HFN) value of the SDU data packet of the next PDCP entity to be received, the serial number (Serial Number, SN) value.
  • Fig. 3 is a schematic diagram of the receiving window of the PDCP entity. As shown in Fig.
  • the variable of the lower boundary of the receiving window is "RX_DELIV", and the "RX_DELIV” identifies the first PDU data packet that has not been delivered to the high-level protocol entity. Packet number.
  • the PDCP entity updates the variable "RX_DELIV" of the lower boundary of the receiving window according to the COUNT of the PDU data packets submitted to the high-level protocol entity. For the PDU data packets waiting to be received, the PDCP entity will start the reordering timer. When the reordering timer expires, the PDCP entity ignores the "COUNT of the PDU data packets waiting to be received" and updates the lower boundary of the receiving window.
  • the "RX_REORD” variable identifies the packet COUNT that started the reorder timer. Among them, “RX_NEXT” marks the data packet COUNT of the next PDU data packet to be received. As shown in FIG. 3 , the initial values of "RX_DELIV” and “RX_NEXT" of the PDCP entity are "0". When the PDU data packet numbered "1" is received, it means that the PDU data packet numbered "0" has not been received.
  • the PDCP entity updates "RX_NEXT” to "2", and sets “RX_REORD” to “2" in response to the need to start the reordering timer.
  • the adjustment parameter of the variable of the receiving window of the PDCP entity may include at least one of the following: the window length of the receiving window, the boundary value of the receiving window, the HFN value in the header of the first data packet received by the PDCP entity, The SN value in the header of the first data packet and the COUNT value in the header of the first data packet.
  • the terminal device may determine the adjustment parameter corresponding to the variable of the receiving window of the PDCP entity according to the instruction of the network device. In other implementations, the terminal device may determine adjustment parameters corresponding to the variables of the receiving window of the PDCP entity according to the agreement.
  • the terminal device may configure the variable for the receiving window of the PDCP entity according to the adjustment parameter.
  • the terminal device may directly configure the variable of the receiving window of the PDCP entity according to the determined adjustment parameter.
  • the terminal device and the network device enter into a protocol agreement, and agree on a calculation formula for calculating the adjustment parameters. After the adjustment parameters are determined, based on the calculation formula agreed in the protocol, the specific value of the variable of the receiving window of the PDCP entity can be calculated.
  • the configuration value is a variable of the receiving window of the PDCP entity based on the calculated configuration value.
  • the terminal device determines the adjustment parameters corresponding to the variables of the receiving window of the PDCP entity, and realizes the adjustment and configuration of the receiving window variables of the PDCP entity based on the obtained adjustment parameters.
  • the variable of the receiving window of the PDCP entity is adjusted based on the received adjustment parameters, so that the variable of the receiving window of the PDCP entity can be updated in time, so that new terminal equipment can join to receive MBS data at any time, ensuring that the MBS Continuity and reliability of data transmission.
  • FIG. 4 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to an embodiment of the present application. The method is executed by a terminal device. As shown in FIG. 4 , the method includes:
  • S401 Determine an adjustment parameter corresponding to a variable of a receiving window of the PDCP entity.
  • the terminal device may receive indication information sent by the network device, where the indication information carries the adjustment parameter.
  • the network device may send indication information to the terminal device, where the indication information carries an adjustment parameter, and the adjustment parameter may be used to adjust the receiving window variable of the PDCP entity. Accordingly, the terminal device may receive the network Indication information sent by the device that carries adjustment parameters.
  • the adjustment parameters For the specific introduction of the adjustment parameters, reference may be made to the description of the relevant content in each embodiment of the present application, which will not be repeated this time.
  • the terminal device may receive a broadcast message sent by the network device, where the broadcast message carries indication information.
  • the network device can configure the PDCP entity of MRB-1 for the terminal device through Radio Resource Control (RRC) signaling.
  • RRC Radio Resource Control
  • the RRC signaling carries the variable corresponding to the receiving window of the PDCP entity.
  • the terminal device receives the RRC signaling sent by the network device, and can determine the adjustment parameter corresponding to the variable of the receiving window of the PDCP entity.
  • the terminal device may receive a broadcast multicast service MBS control channel message, where the MBS control channel message is used to carry indication information.
  • a network device can transmit MBS control signaling through a multicast control channel (Multimedia Control Channel, MCCH).
  • MCCH is a logical channel of the air interface.
  • the network device sends control signaling through the MCCH to configure the PDCP entity of MRB-1 for the terminal device. It can be understood that the control signaling carries the corresponding adjustment parameter of the variable of the receiving window, and the terminal device receives the control signaling sent by the network device, and can determine the adjustment parameter corresponding to the variable of the receiving window of the PDCP entity.
  • the adjustment parameter sent by the network device may include the length of the receiving window, the boundary value of the receiving transmission window, or both the above-mentioned adjustment parameters.
  • the boundary value of the receiving window may be a candidate lower boundary value of the receiving window, or may be a candidate upper boundary value of the receiving window, and may also include a candidate upper boundary value of the receiving window and a candidate lower boundary value of the receiving window.
  • the terminal device may adjust the variable of the receiving window based on the candidate lower boundary value.
  • the terminal device may directly configure the lower boundary value of the receiving window as the candidate lower boundary value, that is, the terminal device configures RX_DELIV as the candidate lower boundary value.
  • the bearer identifier of the RRC signaling can be RRC Connection Reconfiguration signaling.
  • the network device can send control signaling through the MCCH to configure the PDCP of MRB-1 for the terminal device.
  • the variable of the receiving window is adjusted according to the window length and the candidate upper boundary value.
  • the terminal device determines the candidate lower boundary value of the receiving window based on the window length and the candidate upper boundary value, and configures the lower boundary value of the receiving window as the candidate lower boundary value.
  • the terminal device when the adjustment parameter corresponding to the receiving window variable sent by the network device to the terminal device is the candidate upper boundary value of the receiving window, in order to realize the adjustment configuration for the lower boundary value of the receiving window, the terminal device also needs to length, the candidate lower boundary value, and the value of the variable of the lower boundary of the receiving window is directly configured as the candidate lower boundary value, that is, the terminal device configures RX_DELIV as the candidate lower boundary value.
  • the network device can send RRC signaling to the terminal.
  • the device configures the PDCP entity of MRB-1, and the RRC signaling carries the candidate upper boundary value of the receiving window as 7.
  • the network device can send control signaling through the MCCH, which is The terminal equipment configures the PDCP entity of MRB-1, wherein the control signaling carries the candidate upper boundary value of the receiving window as 7.
  • the method for configuring the receiving window of the PDCP entity proposed in the present application receives the indication information carrying the adjustment parameter sent by the network device, and adjusts the lower boundary value of the receiving window of the PDCP entity based on the obtained adjustment parameter.
  • the adjustment of the lower boundary value of the receiving window can be realized, so that the receiving window variable of the PDCP entity can be updated in time, thereby realizing New terminal equipment can be added to receive MBS data at any time, which ensures the continuity and reliability of MBS data transmission.
  • variable adjustment method for the receiving window of the PDCP entity may further include FIG. 5 , which is a schematic flowchart of a method for configuring the receiving window of the PDCP entity according to an embodiment of the application, and the method is executed by a terminal device, As shown in Figure 5, the method includes:
  • step S501 reference may be made to the description of the relevant content in any embodiment of the present application, which will not be repeated here.
  • the adjustment parameter includes the candidate number value of the SDU of the next PDCP entity to be received.
  • the terminal device in response to the obtained adjustment parameter being the candidate number value of the service data unit (service data unit, SUD) of the next PDCP entity to be received, the terminal device may, based on the candidate number value of the SDU, perform a The variables of the entity's receive window are adjusted.
  • the terminal device can directly configure the candidate number value of the SDU with the number of the SDU of the PDCP entity to be received next corresponding to the receive window of the PDCP entity, that is, the terminal device configures the RX_NEXT of the receive window as the candidate number value.
  • the method for configuring the receiving window of the PDCP entity proposed in the present application configures the SDU number value of the next PCDP entity to be received as the candidate number value, which can realize the adjustment of the SDU number value of the PCDP entity, so that the receiving window variable of the PDCP entity is It is updated in time, so that new terminal equipment can be added at any time to receive MBS data, which ensures the continuity and reliability of MBS data transmission.
  • FIG. 6 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to an embodiment of the present application. The method is executed by a terminal device. As shown in FIG. 6 , the method includes:
  • S601 Determine the adjustment parameter corresponding to the variable of the receiving window of the PDCP entity.
  • Step S601 can participate in the above-mentioned related details, which will not be repeated here.
  • the adjustment parameter includes the HFN value of the SDU of the PDCP entity to be received next.
  • the number value (COUNT) of the SDU of the next PDCP entity to be received is composed of the HFN value and the PDCPSN value, as shown in Figure 7, where the PDCP SN value can be carried in the header of the first PDCP data packet
  • the SN value is determined by the HFN value, and the HFN value can be indicated to the terminal device by the network device through the RRC signaling or the control signaling sent by the MCCH.
  • the adjustment parameter also needs to include the SN value
  • the PDCP entity on the terminal device side can receive the PDCP data packet sent by the network device, and when receiving When the first PDCP data packet is reached, the terminal device may determine the SN value in the adjustment parameter based on the SN value carried in the header of the first PDCP data packet.
  • the PDCP SN value will be reversed after reaching the maximum value.
  • the terminal device can adjust the variable of the receiving window of the PDCP entity based on the adjustment parameter SN value and the HFN value, wherein the variable of the receiving window adjustment may be the lower boundary value of the receiving window, or the lower boundary value of the receiving window.
  • the variable of the receiving window adjustment may be the lower boundary value of the receiving window, or the lower boundary value of the receiving window.
  • the lower boundary value of the receiving window and/or the HFN part of the number value of the next PDCP SDU to be received is configured as an HFN value.
  • the terminal device After the terminal device obtains the HFN value configured by the network device, based on the obtained HFN value, it adjusts and configures the HFN part included in the lower boundary value of the receiving window and/or the number value of the next PDCP SDU to be received.
  • the configuration can also be adjusted according to the lower boundary value of the receiving window and other parameters.
  • the configuration can also be adjusted according to the HFN part and other parameters included in the number value of the next PDCP SDU to be received.
  • the value of the HFN part is adjusted to 2.
  • a first sum value of the SN value and the first target value is determined.
  • the first target value is an integer value indicated by the network device or agreed by the protocol.
  • the SN value can be parsed from the packet header of the first PDCP data packet, and further, the SN value in the packet header is added to the first target value to obtain the result value. is the first sum value. Further, the SN part of the variable of the receiving window is configured according to the first sum value.
  • different conditions may be preset according to the maximum allowable value of the SN value, and when different conditions are met, the SN part may correspond to different candidate configuration values.
  • the terminal device may first determine the target condition satisfied by the first sum value, and determine the configuration value corresponding to the target condition as a candidate configuration value for configuring the variable of the receiving window. Further, the terminal configures the lower boundary value of the receiving window and/or the SN part of the number value of the next PDCP SDU to be received as a candidate configuration value.
  • a value of zero is determined as a candidate configuration value in response to the first sum value satisfying a target condition of being greater than a maximum allowable value of the SN value. Further, the terminal device configures the value of the SN part in the variable of the receiving window to be 0. That is to say, the terminal device may configure the SN part in the lower boundary value RX_DELIV of the receiving window to 0, or configure the SN part in the number value RX_NEXT of the next PDCP SDU to be received as 0.
  • the candidate configuration value for the SN part of the value RX_NEXT may be 0.
  • the terminal device in response to the first sum value satisfying a target condition of being less than a zero value, a maximum allowable value of the SN value, a second sum value of the first sum value and the second target value are determined, and the second sum value is determined as a candidate configuration value. Further, the terminal device configures the value of the SN part in the variable of the receiving window as the second sum value. That is, the terminal device may configure the SN part in the lower boundary value RX_DELIV of the receiving window as the second sum value, or configure the SN part in the number value RX_NEXT of the next PDCP SDU to be received as the second sum value value.
  • the network device configures another integer value for the header of the first PDCP data packet received by the PDCP entity, and the integer value may also be agreed in a pre-signed agreement and is the second target value.
  • the maximum value that the SN value of the PDCP can take, the first sum value, and the second target value can be added to obtain the second sum value.
  • the second sum value may be determined as a candidate configuration value adjusted by the SN part in the variables of the receiving window.
  • the candidate configuration value of the SN part in the lower boundary value RX_DELIV of the receiving window may be 7, or the candidate configuration value of the SN part in the number value RX_NEXT of the next PDCP SDU to be received may be 7.
  • the first sum value is determined as a candidate configuration value in response to the first sum value satisfying a target condition of being greater than half of the maximum allowed value. Further, the terminal device configures the value of the SN part in the variable of the receiving window as the first sum value. That is, the terminal device may configure the SN part in the lower boundary value RX_DELIV of the receiving window as the first sum value, or may configure the SN part in the number value RX_NEXT of the next PDCP SDU to be received as the first sum value and value.
  • the first sum value when the first sum value is greater than the maximum value in the first half of the value range of the SN value in the PDCP, the first sum value may be determined as the SN in the variable of the receiving window Part of the tuning candidate configuration value.
  • the first half of the possible values in is [0, 3], where half of the maximum allowed value is 3.
  • the terminal device determines the first sum value as the adjustment candidate configuration value of the SN part in the variable of the receiving window, for example, the SN part candidate configuration value in the lower boundary value RX_DELIV of the receiving window may be 5, or the next waiting
  • the candidate configuration value of the SN part in the number value RX_NEXT of the received PDCP SDU may be 5.
  • the value of the SN part in a certain variable of the receiving window can be adjusted based on the obtained candidate configuration value.
  • the configuration of the SN part in the lower boundary value RX_DELIV of the receiving window may be 0, or the configuration of the SN part in the number value RX_NEXT of the next PDCP SDU to be received may be configured. is 0.
  • the candidate configuration value is the second sum value
  • the SN part in the lower boundary value RX_DELIV of the receiving window can be configured as 7, or the next PDCP SDU to be received can be configured.
  • the number value of the SN part in RX_NEXT is configured as 7.
  • the candidate configuration value is the first sum value
  • the SN part in the lower boundary value RX_DELIV of the receiving window can be configured as 7, or the next PDCP SDU to be received can be configured.
  • the number value of the SN part in RX_NEXT is configured as 7.
  • the lower boundary value of the receiving window of the PDCP entity after receiving the new terminal device can be kept within a reasonable range, thereby effectively reducing the data. loss of packets.
  • the method for configuring the receiving window of the PDCP entity proposed in the present application adjusts the variable of the receiving window of the PDCP entity based on the acquired SN value and the HFN value, so as to realize the timely update of the receiving window variable of the PDCP entity, so that new terminal
  • the device can join to receive MBS data at any time, which ensures the continuity and reliability of MBS data transmission.
  • FIG. 8 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application.
  • the method executing the main body is a terminal device. As shown in FIG. 8 , the method includes:
  • S801 Determine the serial number value carried in the packet header of the first PDCP data packet received by the PDCP entity as an adjustment parameter.
  • the content of the packet header of the first PDCP data packet received by the PDCP entity can be changed to directly indicate the serial number value to the terminal device, and the serial number value can be used as the adjustment parameter of the variable of the receiving window.
  • variable of the receiving window may be adjusted and configured according to the obtained adjustment parameter.
  • the lower boundary value of the receiving window and/or the serial number value of the SDU of the next PDCP entity to be received is configured as the serial number value carried in the packet header.
  • the SN part in the lower boundary value RX_DELIV of the receiving window can be configured to 4, or the number value of the next PDCP SDU to be received can be set to RX_NEXT
  • the SN part of the configuration is 4.
  • the network device configures another integer value for the header of the first PDCP data packet received by the PDCP entity, and the integer value may also be agreed in a pre-signed agreement and is the third target value.
  • the number value indicated by the packet header of the first PDCP data packet may be added to the third target value, thereby obtaining the third sum value.
  • the third target value c is set to 1
  • the SN part in the lower boundary value RX_DELIV of the receiving window may be configured as 5, or the SN part in the number value RX_NEXT of the next PDCP SDU to be received may be configured as 5.
  • the lower boundary value of the receiving window of the PDCP entity after receiving the new terminal device can be kept within a reasonable range, thereby effectively reducing the loss of data packets.
  • the method for adjusting the receiving window of the PDCP entity proposed in the present application uses the number value indicated by the packet header of the first PDCP data packet as the candidate configuration value to adjust and configure the variables of the receiving window, so as to realize the timely realization of the receiving window variables of the PDCP entity.
  • the update enables new terminal devices to join at any time to receive MBS data, which ensures the continuity and reliability of MBS data transmission.
  • FIG. 9 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to an embodiment of the present application. The method is executed by a terminal device. As shown in FIG. 9 , the method includes:
  • S901 Receive indication information sent by a network device, where the indication information carries adjustment parameters.
  • Step S901 can participate in the above-mentioned related details, which will not be repeated here.
  • S902 Determine a trigger event that satisfies the variable for adjusting the receiving window.
  • variable adjustment of the receiving window of the PDCP entity may be performed based on a trigger event, where the trigger event may be configured by a network device or agreed by a preset protocol.
  • the trigger event is receiving an adjustment instruction sent by the network device, and the adjustment instruction is used to instruct the terminal device to adjust the variable of the receiving window.
  • the network device may send a trigger event configuration instruction to the terminal device, and the terminal device starts to adjust the variables of the receiving window based on the acquired adjustment instruction.
  • the trigger event is to create a PDCP entity of the MBS radio bearer MRB.
  • a new PDCP entity for the MBS radio bearer MRB may be used as a trigger event.
  • an instruction to start adjustment may be triggered to the terminal device.
  • the terminal device is based on the acquired The variable that indicates to start adjusting the receive window.
  • the triggering event is the PDCP entity that re-establishes or reconfigures the MRB.
  • the re-establishment or re-configuration of the PDCP entity of the MRB may be used as a trigger event, and the re-establishment and re-configuration have the same function in implementation.
  • the MBS service may be sent through a specific radio bearer (MBS Radio Bearer, MRB), wherein the protocol stack structure of the radio bearer that bears the MBS service may be a common MBS bearer or a separate MBS bearer.
  • MBS Radio Bearer MRB
  • the common MBS bearer includes one PDCP associated with one Radio Link Control (Radio Link Control, RLC) entity, and the data of the RLC entity is sent through G-RNTI PDCCH scheduling.
  • the MBS bearer is separated, including 1 PDCP associated with 2 RLC entities.
  • the data of one RLC entity is sent through G-RNTI PDCCH scheduling, which can be understood as a multicast bearer, and the data of the other RLC entity is transmitted through the wireless network temporary identification (Cell-Radio Network Temporary Identifier, C-RNTI) PDCCH scheduling transmission can be understood as a unicast bearer.
  • C-RNTI Cell-Radio Network Temporary Identifier
  • the PDCP entity of the MRB can be reconfigured from "unicast bearer” to "multicast bearer”.
  • the network device reconfigures the sending mode of MBS service-1, and reconfigures the sending mode of the MBS service-1 through RRC signaling 1 send.
  • the behavior of the reconfiguration can be used as a trigger event, and then the adjustment of the variables of the receiving window can be started.
  • the reconfiguration of the PDCP entity of the MRB it can be reconfigured from "separate MBS bearer" to "normal MBS bearer".
  • the bearer type of MRB-1 is "separate MBS bearer"
  • the network device reconfigures the bearer type of MRB-1 to "normal MBS bearer" through RRC signaling ".
  • the behavior of the reconfiguration can be used as a trigger event, and then the adjustment of the variables of the receiving window can be started.
  • the data reception of "split MBS bearer" may be converted from a unicast path to a multicast path.
  • the bearer type of MRB-1 is "separate MBS bearer", including unicast path and multicast path
  • the terminal device receives MBS through the unicast path of MRB-1 Business-1.
  • the network device changes the receiving path of the MBS service-1 of the MRB-1 from the unicast path to the multicast path by sending the instruction signaling.
  • the behavior of the reconfiguration can be used as a trigger event, and then the adjustment of the variables of the receiving window can be started.
  • the above trigger event may include at least one of the above steps S802 to S804.
  • the terminal device may start to adjust the variable of the receiving window of the PDCP entity based on the occurrence of the trigger event.
  • the detailed adjustment method can be found in the above-mentioned related details, which will not be repeated here.
  • the method for adjusting the receiving window of the PDCP entity proposed in the present application enables the variable adjustment of the receiving window of the PDCP entity to start by triggering an event, which ensures the stable implementation of the variable update of the receiving window, thereby ensuring the continuity of MBS data transmission and reliability.
  • FIG. 10 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application. As shown in FIG. 10 , the method includes:
  • S1001 Receive multicast bearer configuration information sent by a network device for configuring an MBS service.
  • the configuration information sent by the network device is received in the terminal device, and the configuration information is used to configure the multicast bearer configuration information of the MBS service.
  • the multicast bearer configuration information includes: MBS service information.
  • the MBS service information includes at least one of the following.
  • the MBS service information may be an MBS service identifier.
  • the MBS service can be sent through the PDSCH scheduled by the PDCCH, and the PDCCH of the scheduled MBS service can be indicated by a specific scheduling identifier of the MBS service, wherein the MBS service identifier can be a temporary mobile group identity (Temporary Mobile Group Identity, TMGI), It can also be an MBS session identifier (MBS Session ID), or an MBS service flow identifier (MBS QoS flow ID).
  • TMGI Temporal Mobile Group Identity
  • MBS Session ID MBS session identifier
  • MBS QoS flow ID MBS service flow identifier
  • the MBS service information may be an MBS bearer identifier, for example, MRB-1.
  • the MBS service information may be configured for a protocol entity carried by the MBS, such as PDCP configuration.
  • the MBS service can be sent through a specific MRB, and the MRB that can carry the MBS service can include a common MBS bearer or a separate MBS bearer.
  • a common MBS bearer includes a PDCP associated with an RLC entity, and the data of the RLC entity is sent through G-RNTI PDCCH scheduling.
  • the MBS bearer is separated, including one PDCP associated with two RLC entities, the data of one RLC entity is sent through G-RNTI PDCCH scheduling, that is, multicast, and the data of one RLC entity is sent through C-RNTI PDCCH scheduling, that is, unicast.
  • the terminal device needs to establish a PDCP entity to receive the information sent by the MBS service.
  • a corresponding MRB is established, and then a corresponding PDCP entity is established based on the MRB.
  • the MRB may use a common MBS bearer, and further, based on the structure of the common MBS bearer, a corresponding PDCP entity is established.
  • the network device sends the configuration information of the MBS service to the terminal device through signaling corresponding to the terminal device.
  • the MBS may adopt a common MBS bearer or a separate MBS bearer, and then establish a corresponding PDCP entity.
  • the network device sends the configuration information of the MBS service to the terminal device through the system information and the MBS control channel information.
  • S1003 Determine the adjustment parameter corresponding to the variable of the receiving window of the PDCP entity.
  • Steps S1003 to S1004 may participate in the above-mentioned related details, which will not be repeated here.
  • the method for configuring the receiving window of the PDCP entity proposed in this application establishes corresponding PDCP entities based on different MRBs, provides a bearer for the terminal equipment to receive MBS service information, ensures the stable implementation of variable update of the receiving window, and further ensures the MBS data Continuity and reliability of transmission.
  • the present application also proposes a method for adjusting the receiving window of the PDCP entity, and the main body of the method is a network device, as shown in FIG.
  • a schematic flowchart of a method for adjusting a receiving window of a PDCP entity according to another embodiment, the method includes:
  • the receiving window of the PDCP entity needs to be adjusted at any time according to the joining situation of the terminal equipment.
  • the network equipment is dynamically adjusted based on the terminal equipment to be The terminal device configures the adjustment parameter of the variable of the receiving window of the PDCP entity of the specific bearer.
  • variable of the receiving window may include at least one item: the window length of the receiving window, the boundary value of the receiving window, the HFN value in the header of the first data packet received by the PDCP entity, the first data The SN value in the header of the packet, and the COUNT value in the header of the first data packet.
  • the adjustment parameter of the variable of the receiving window may include at least one item: a candidate configuration value of the window length of the receiving window, a candidate configuration value of the boundary value of the receiving window, and the first data packet received by the PDCP entity.
  • the adjustment parameter includes a window length and/or a boundary value of the receiving window.
  • the change of the lower boundary value of the receiving window may affect the number of terminal devices that can be accommodated in it, and the network device may configure adjustment parameters for the terminal device based on the capacity requirements of the terminal devices in the receiving window.
  • the adjustment parameters configured by the network device and sent to the terminal device may include the candidate configuration value of the lower boundary value, the candidate configuration value of the upper boundary value and the window length.
  • the candidate configuration value of the upper boundary value and the window length obtain the candidate configuration value of the lower boundary value, so as to achieve the purpose of adjusting the lower boundary value of the receiving window.
  • the adjustment parameter includes a candidate number value of the service data unit SDU of the PDCP entity to be received next.
  • the SDU number value of the next PDCP entity to be received is composed of an SN value and an HFN value
  • the terminal device can implement the receiving window variable based on the SN value carried in the SDU number value of the next PCDP entity to be received
  • the HFN part of the receiving window variable can be adjusted based on the HFN value carried in the SDU number value of the next PCDP entity to be received, and then the receiving window variable can be adjusted.
  • the adjustment parameter may include the HFN value.
  • the network device can configure the HFN value for the terminal device through RRC signaling.
  • the adjustment parameter may include a serial number value carried in the packet header of the first PDCP data packet received by the PDCP entity.
  • the candidate configuration value of the SN part in the variable of the receiving window can be determined based on the SN value carried in the number value of the SDU of the next PDCP entity to be received. Further, the number value of the SDU of the next PDCP entity to be received The SN value needs to be determined by the SN value carried in the header of the first PDCP data packet received by the PDCP entity. In order to realize the adjustment of the SN part in the variable of the receiving window, the network device needs to configure the SN value in the packet header of the first PDCP data packet received by the terminal device.
  • S1202 Send indication information to the terminal device, where the indication information is used to instruct the terminal device to configure the variable of the receiving window of the PDCP entity based on the adjustment parameter, and the indication information carries the adjustment parameter.
  • the network device generates indication information based on the adjustment parameters configured for the variable of the window to be received by the PDCP entity, and sends the indication information to the terminal device, so that the terminal device can realize the reception based on the adjustment parameters carried in the indication information. Adjustment of the variables of the window.
  • a broadcast message or a broadcast multicast service MBS control channel message is sent to the terminal device, wherein the broadcast message or the MBS control channel message is used to carry the indication information.
  • the network device can send a broadcast message or a broadcast multicast service MBS control channel message to the terminal device, and can carry the indication information in the broadcast message or the MBS control channel message. parameter indication information, and then complete the adjustment of the variables of the receiving window.
  • a common MBS bearer can be used, and the transmission mode of the broadcast multicast service can be selected, so that the network device can send the configuration information to the terminal device, and the terminal device enters the connected state and receives the configuration information sent by the MBS service, so as to receive the MBS service. the purpose of the data.
  • a normal MBS bearer or a separate MBS bearer may be used, and a broadcast transmission mode may be selected, and the network device may send the receiving configuration information of the MBS service to the terminal device through system information and MBS control channel information.
  • the system message may be a system information block (System Information Block, SIB), and the MBS control channel information may be MCCH.
  • the terminal device can receive the transmission configuration information of the MBS service in an idle (IDLE) or inactive (INACTIVE) state, so as to achieve the purpose of receiving the MBS service data.
  • the adjustment parameter can carry the candidate boundary value of the receiving window, the COUNT value of the next PDCP SDU to be received, the HFN value, etc.
  • the network device sends the adjustment parameter to the terminal device through a broadcast message or an MBS control channel message.
  • the message carries adjustment parameters and other configuration information, such as initial access information in the System Information Block (SIB) 1.
  • SIB System Information Block
  • the terminal device needs to actively read the system information to obtain the changed HFN value, and the network device will not send the indication information for the change of the HFN value.
  • the variable of the receiving window of the current PDCP entity needs to be adjusted.
  • the network device needs to generate indication information based on the candidate adjustment parameters configured for the terminal device, and send it to the terminal device, instructing the terminal device to adjust the variables of the receiving window based on the indication information.
  • the indication information sent by the network device carries changes. after the HFN value.
  • the change indication information may be the paging short message corresponding to the SIB message, or the MCCH change notification corresponding to the MCCH message.
  • the method for configuring the receiving window of the PDCP entity proposed in the present application the execution subject is the network device, the network device configures adjustment parameters for the variables of the receiving window of the PDCP entity, and generates instruction information based on the configured adjustment parameters, and sends it to the terminal device for receiving
  • the variable of the window adjustment provides candidate configuration values, which realizes the timely update of the receiving window variable of the PDCP entity, so that new terminal equipment can join in the reception of MBS data at any time, ensuring the continuity and reliability of MBS data transmission.
  • FIG. 13 is a schematic flowchart of a method for configuring a receiving window of a PDCP entity according to another embodiment of the present application.
  • the method executing the method is a network device. As shown in FIG. 13 , the method includes:
  • S1301 Send an adjustment instruction for instructing the terminal device to adjust the variable of the receiving window to the terminal device.
  • the terminal device may determine that the variables of the receiving window need to be adjusted based on the adjustment instruction sent by the network device. variable to adjust.
  • the network device may send an adjustment instruction to the terminal device in response to determining that it is necessary to create a PDCP entity for the terminal device that carries the MRB over the MBS radio; optionally, in response to determining that the PDCP entity that needs to be rebuilt or reconfigured for the MRB for the terminal device , an adjustment instruction can be sent to the terminal device.
  • S1303 Send indication information to the terminal device, where the indication information is used to instruct the terminal device to configure the variable of the receiving window of the PDCP entity based on the adjustment parameter, and the indication information carries the adjustment parameter.
  • Steps S1302-S1303 can be involved in the above-mentioned related details, which will not be repeated here.
  • the network device sends adjustment instruction information to the terminal device, so that the terminal device can accurately adjust the variables of the receiving window of the PDCP entity, ensuring the continuity of MBS data transmission and reliability.
  • the methods for implementing the proposed application in this application are respectively introduced from the perspectives of network equipment and terminal equipment.
  • the network device and the terminal device may include hardware structures and software modules, and implement the above functions in the form of hardware structures, software modules, or hardware structures plus software modules.
  • a certain function among the above functions may be implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • FIG. 14 is a schematic structural diagram of an apparatus for configuring a receiving window of a PDCP entity according to an embodiment of the application.
  • the apparatus 1400 for configuring a receiving window of a PDCP entity may include: a transceiver module 141 and a processing module 142, wherein:
  • the transceiver module 141 may include a sending module and/or a receiving module, the sending module is used to implement the sending function, the receiving module is used to implement the receiving function, and the transceiver module 141 may implement the sending function and/or the receiving function.
  • the apparatus 1400 for configuring a receiving window of a PDCP entity which is a terminal device, includes:
  • the transceiver module 141 is used to determine the adjustment parameter corresponding to the variable of the receiving window of the PDCP entity;
  • the processing module 142 is configured to configure the variable of the receiving window of the PDCP entity based on the adjustment parameter.
  • the transceiver module 141 is further configured to: receive indication information sent by the network device, where the indication information carries adjustment parameters.
  • the processing module 142 is further configured to: in response to the adjustment parameters including the window length and/or the boundary value of the receiving window, configure the variable of the receiving window according to the window length and/or the boundary value.
  • the processing module 142 is further configured to: in response to the boundary value being a candidate lower boundary value of the receiving window, configure the lower boundary value of the receiving window as a candidate lower boundary value.
  • the processing module 142 is further configured to: in response to the boundary value being the upper boundary value of the receiving window, determining the candidate lower boundary value of the receiving window according to the window length and the target upper boundary value, and configuring the lower boundary value of the receiving window as the candidate lower boundary value. Boundary value.
  • the processing module 142 is further configured to: in response to the adjustment parameter including the candidate number value of the service data unit SDU of the next PDCP entity to be received, configure the number value of the SDU of the next PDCP entity to be received in the receiving window as the candidate number value.
  • the processing module 142 is further configured to: in response to the adjustment parameter including the HFN value, determine the SN value in the packet header of the first PDCP data packet received by the PDCP entity; and configure the variable of the receiving window according to the HFN value and the SN value.
  • the processing module 142 is further configured to: configure the HFN part of the variable of the receiving window according to the HFN value; and configure the SN part of the variable of the receiving window according to the SN value.
  • the processing module 142 is further configured to: configure the lower boundary value of the receiving window and/or the HFN part of the number value of the next PDCP SDU to be received as an HFN value.
  • the processing module 142 is further configured to: determine a first sum value of the SN value and the first target value; and configure the SN part of the variable of the receiving window according to the first sum value.
  • the processing module 142 is further configured to: determine the candidate configuration value corresponding to the target condition in response to the target condition satisfied by the first sum value; set the lower boundary value of the receiving window and/or the number value of the next PDCP SDU to be received.
  • the SN part is configured as a candidate configuration value.
  • the processing module 142 is further configured to: in response to the first sum value meeting the target condition of the maximum allowable value greater than the SN value, determine the candidate configuration value from the zero value; or, in response to the first sum value meeting the target condition smaller than the zero value, determining the maximum allowable value of the SN value, the second sum value of the first sum value and the second target value, and determining the second sum value as a candidate configuration value; or, in response to the first sum value meeting a target greater than half of the maximum allowable value condition, the first sum value determines the candidate configuration value.
  • the transceiver module 141 is further configured to determine the number value carried in the packet header of the first PDCP data packet received by the PDCP entity as an adjustment parameter;
  • the processing module 142 is further configured to configure the variable of the receiving window according to the serial number value carried in the packet header.
  • the processing module 142 is further configured to: configure the lower boundary value of the receiving window and/or the serial number value of the SDU of the next PDCP entity to be received as the serial number value carried in the packet header;
  • the third sum value of the three target values, the lower boundary value of the receiving window and/or the number value of the SDU of the next PDCP entity to be received is configured as the third sum value.
  • the transceiver module 141 is further configured to: receive a broadcast message or a broadcast multicast service MBS control channel message, wherein the broadcast message or the MBS control channel message is used to carry indication information.
  • the processing module 142 is further configured to: determine a trigger event that satisfies a variable for adjusting the receiving window; wherein, the trigger event is at least one of the following events: receiving an adjustment instruction sent by the network device, and the adjustment instruction is used to instruct the terminal device to adjust the receiving window. or, create a new PDCP entity for the MBS to wirelessly bear the MRB; or, rebuild or reconfigure the PDCP entity for the MRB.
  • the apparatus 1400 for configuring the receiving window of the PDCP entity which is a network device, includes:
  • a processing module 142 configured to configure adjustment parameters corresponding to variables of the receiving window of the PDCP entity
  • the transceiver module 141 is configured to send indication information to the terminal device, wherein the indication information is used to instruct the terminal device to configure the variable of the receiving window of the PDCP entity based on the adjustment parameter, and the indication information carries the adjustment parameter.
  • the processing module 142 is further configured to configure the adjustment parameters including the window length and/or the boundary value of the receiving window.
  • the processing module 142 is further configured to configure the adjustment parameter including the candidate number value of the service data unit SDU of the PDCP entity to be received next.
  • the processing module 142 is further configured to configure the adjustment parameters including the HFN value.
  • the processing module 142 is further configured to configure the adjustment parameters including the serial number value carried in the packet header of the first PDCP data packet received by the PDCP entity.
  • the transceiver module 141 is further configured to: send a broadcast message or a broadcast multicast service MBS control channel message to the terminal device, wherein the broadcast message or the MBS control channel message is used to carry indication information.
  • the transceiver module 141 is further configured to: send an adjustment instruction for instructing the terminal device to adjust the variable of the receiving window to the terminal device.
  • the network device In the device for configuring the receiving window of the PDCP entity proposed in this application, the network device generates an adjustment instruction based on the occurrence of the trigger event and sends it to the terminal device, configures the adjustment parameter of the variable of the receiving window of the PDCP entity for the terminal device and sends it to the terminal device, the terminal device After the device receives the adjustment instruction, it adjusts the variable of the receiving window based on the candidate configuration value carried in the obtained adjustment parameter.
  • the timely update of the receiving window variable of the PDCP entity is realized, and the receiving window of the PDCP entity is avoided. Due to the restriction on adding new terminal equipment caused by the inability to perform variable update, new terminal equipment can join at any time to receive MBS data, which ensures the continuity and reliability of MBS data transmission.
  • FIG. 15 is a schematic structural diagram of another communication apparatus 1500 proposed by an embodiment of the present application.
  • the communication apparatus 1500 may be a network device, a terminal device, a chip, a chip system, or a processor that supports the network device to implement the above method, or a chip, a chip system, or a chip that supports the terminal device to implement the above method. processor etc.
  • the apparatus can be used to implement the methods described in the foregoing method embodiments, and for details, reference may be made to the descriptions in the foregoing method embodiments.
  • the Communication apparatus 1500 may include one or more processors 1501 .
  • the processor 1501 may be a general-purpose processor or a special-purpose processor, or the like.
  • it may be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminal equipment, terminal equipment chips, DU or CU, etc.), execute computer programs, etc. , which processes data from computer programs.
  • the communication apparatus 1500 may further include one or more memories 1502, on which computer programs 1504 may be stored, and the processor 1501 executes the computer programs 1504, so that the communication apparatus 1500 executes the methods described in the above method embodiments.
  • data may also be stored in the memory 1502 .
  • the communication device 1500 and the memory 1502 can be provided separately or integrated together.
  • the communication apparatus 1500 may further include a transceiver 1505 and an antenna 1506 .
  • the transceiver 1505 may be called a transceiver unit, a transceiver, or a transceiver circuit, etc., and is used to implement a transceiver function.
  • the transceiver 1505 may include a receiver and a transmitter, the receiver may be called a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be called a transmitter or a transmitting circuit, etc., for implementing a transmitting function.
  • the communication apparatus 1500 may further include one or more interface circuits 1507 .
  • the interface circuit 1507 is used to receive code instructions and transmit them to the processor 1501 .
  • the processor 1501 executes the code instructions to cause the communication device 1500 to perform the methods described in the above method embodiments.
  • the communication apparatus 1500 is a terminal device: the transceiver 1505 is used to perform step S201 in FIG. 2 , step S401 in FIG. 4 , step S501 in FIG. 5 , etc.; Step S402 in FIG. 4 and step S502 in FIG. 5 and so on.
  • the communication apparatus 1500 is a network device: the transceiver 1505 is used to perform step S1002 in FIG. 10 , step S1102 in FIG. 11 , etc.; the processor 1501 is used to perform step S1001 in FIG. 10 , step S1101 in FIG. S1103 and so on.
  • the processor 1501 may include a transceiver for implementing receiving and transmitting functions.
  • the transceiver may be a transceiver circuit, or an interface, or an interface circuit.
  • Transceiver circuits, interfaces or interface circuits used to implement receiving and transmitting functions may be separate or integrated.
  • the above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface or interface circuit can be used for signal transmission or transmission.
  • the processor 1501 may store a computer program 1503, and the computer program 1503 runs on the processor 1501 to enable the communication device 1500 to execute the methods described in the above method embodiments.
  • the computer program 1503 may be embodied in the processor 1501, in which case the processor 1501 may be implemented by hardware.
  • the communication apparatus 1500 may include a circuit, and the circuit may implement the functions of sending or receiving or communicating in the foregoing method embodiments.
  • the processors and transceivers described in this application can be implemented in integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board, PCB), electronic equipment, etc.
  • the processor and transceiver can also be fabricated using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), nMetal-oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS nMetal-oxide-semiconductor
  • PMOS P-type Metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device described in the above embodiments may be a network device or a terminal device (such as the first terminal device in the foregoing method embodiments), but the scope of the communication device described in this application is not limited to this, and the structure of the communication device may be Not limited by FIG. 16 .
  • the communication apparatus may be a stand-alone device or may be part of a larger device.
  • the communication means may be:
  • the IC set can also include a storage component for storing data and computer programs;
  • ASIC such as modem (Modem);
  • the communication device may be a chip or a chip system
  • the chip shown in FIG. 16 includes a processor 1601 and an interface 1602 .
  • the number of processors 1601 may be one or more, and the number of interfaces 1602 may be multiple.
  • the interface 1602 is used to execute step S201 in FIG. 2 , step S401 in FIG. 4 , step S501 in FIG. 5 and so on.
  • the interface 1602 is used to execute step S1002 in FIG. 10 , step S1102 in FIG. 11 and so on.
  • the chip further includes a memory 1603 for storing necessary computer programs and data.
  • An embodiment of the present application further proposes a system for configuring a receiving window of a PDCP entity.
  • the system includes the communication device as a terminal device (such as the terminal device in the foregoing method embodiment) in the foregoing embodiment in FIG. 15 and a communication device as a network device Or, the system includes the communication device as the terminal device (such as the terminal device in the foregoing method embodiment) in the embodiment of FIG. 16 and the communication device as the network device.
  • the present application also provides a readable storage medium on which instructions are stored, and when the instructions are executed by a computer, implement the functions of any of the foregoing method embodiments.
  • the present application also provides a computer program product, which implements the functions of any of the foregoing method embodiments when the computer program product is executed by a computer.
  • a computer program product includes one or more computer programs.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer program can be stored on or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program can be transferred from a website site, computer, server, or data center over a wire (e.g.
  • coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless means to transmit to another website site, computer, server or data center.
  • a computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes an integration of one or more available media.
  • Useful media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, high-density digital video disc (DVD)), or semiconductor media (eg, solid state disk (SSD)) )Wait.
  • At least one in this application may also be described as one or more, and the multiple may be two, three, four or more, which is not limited in this application.
  • the technical feature is distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D”, etc.
  • the technical features described in the “first”, “second”, “third”, “A”, “B”, “C” and “D” described technical features in no order or order of magnitude.
  • the corresponding relationships shown in each table in this application may be configured or predefined.
  • the values of the information in each table are only examples, and can be configured with other values, which are not limited in this application.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, for example, splitting, merging, and so on.
  • the names of the parameters shown in the headings in the above tables may also adopt other names that can be understood by the communication device, and the values or representations of the parameters may also be other values or representations that the communication device can understand.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables. Wait.
  • Predefined in this application may be understood as defining, predefining, storing, pre-storing, pre-negotiating, pre-configuring, curing, or pre-firing.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提出的一种PDCP实体的接收窗口的配置方法及装置，其中，由终端设备执行的方法包括：确定PDCP实体的接收窗口的变量对应的调整参数；基于所述调整参数，配置所述PDCP实体的接收窗口的变量。本申请中，实现了PDCP实体的接收窗口变量的及时更新，使得新的终端设备可以随时加入进行MBS数据的接收，保证了MBS数据传输的持续性以及可靠性。

Description

一种PDCP实体的接收窗口的配置方法及其装置 技术领域
本申请涉及通信技术领域，尤其涉及一种PDCP实体的接收窗口的配置方法及其装置。
背景技术
当终端设备开始接收广播多播业务(Multicast Broadcast Service，MBS)的业务数据的时候，终端设备需要先建立接收MBS业务数据对应的无线承载(MBS Radio Bearer，MRB)的包数据汇聚协议(Packet Data Convergence Protocol，PDCP)实体。
相关技术中，PDCP的接收窗口的边界值无法基于PDCP的发送窗口的编号值实时更新，使得当新的一个UE加入接收MBS业务时无法实现对MBS的业务数据的接收。
发明内容
本申请实施例提出一种PDCP实体的接收窗口的配置方法及其装置，可以用于解决相关技术中MBS的业务数据发送的可靠性较低和持续性较差的问题。
第一方面，本申请实施例提出一种PDCP实体的接收窗口的配置方法，所述方法由终端设备执行，所述方法包括：确定PDCP实体的接收窗口的变量对应的调整参数；基于所述调整参数，配置所述PDCP实体的接收窗口的变量。
本申请提出的PDCP实体的接收窗口的配置方法，终端设备确定PDCP实体的接收窗口的变量对应的调整参数，并基于获取到的调整参数实现对于PDCP实体的接收窗口变量的调整配置。本申请中，基于接收到的调整参数对PDCP实体的接收窗口的变量进行调整，实现了PDCP实体的接收窗口变量的及时更新，使得新的终端设备可以随时加入进行MBS数据的接收，保证了MBS数据传输的持续性以及可靠性。
本申请第一方面提出的一种PDCP实体的接收窗口的配置方法，还可以具备如下技术特征：
在一种实现方式中，所述确定PDCP实体的接收窗口的变量调整参数，包括：接收网络设备发送的指示信息，所述指示信息携带所述调整参数。
在一种实现方式中，所述PDCP实体的接收窗口的配置方法，还包括：响应于所述调整参数包括所述接收窗口的窗口长度和/或边界值，根据所述窗口长度和/或边界值，配置所述接收窗口的变量。
在一种实现方式中，所述PDCP实体的接收窗口的配置方法，还包括：响应于所述边界值为所述接收窗口的候选下边界值，将所述接收窗口的下边界值配置为所述候选下边界值。
在一种实现方式中，所述PDCP实体的接收窗口的配置方法，还包括：响应于所述边界值为所述接收窗口的上边界值，根据所述窗口长度和所述目标上边界值，确定所述接收窗口的候选下边界值，并将所述接收窗口的下边界值配置为所述候选下边界值。
在一种实现方式中，所述PDCP实体的接收窗口的配置方法，还包括：响应于所述调整参数包括下一个待接收的PDCP实体的业务数据单元SDU的候选编号值，将所述接收窗口的下一个待接收的PDCP实体的SDU的编号值配置为所述候选编号值。
在一种实现方式中，所述PDCP实体的接收窗口的配置方法，还包括：响应于所述调整参数包括HFN值，确定所述PDCP实体接收到第一个PDCP数据包的包头中SN值；根据所述HFN值和所述SN 值，配置所述接收窗口的变量。
在一种实现方式中，所述根据所述HFN值和所述SN值，配置所述接收窗口的变量，包括：根据所述HFN值，配置所述接收窗口的变量的HFN部分；根据所述SN值，配置所述接收窗口的变量的SN部分。
在一种实现方式中，所述根据所述HFN值，配置所述接收窗口的变量的HFN部分，包括：将所述接收窗口的下边界值和/或下一个待接收的PDCP SDU的编号值的HFN部分，配置为所述HFN值。
在一种实现方式中，所述根据所述SN值，配置所述接收窗口的变量的SN部分，包括：确定所述SN值与第一目标数值的第一和值；根据所述第一和值配置所述接收窗口的变量的SN部分。
在一种实现方式中，所述根据所述第一和值配置所述接收窗口的变量的SN部分，包括：响应于所述第一和值所满足的目标条件，确定所述目标条件对应的候选配置值；将所述接收窗口的下边界值和/或下一个待接收的PDCP SDU的编号值的SN部分配置为所述候选配置值。
在一种实现方式中，所述响应于所述第一和值所满足的目标条件，确定所述目标条件对应的目标配置值，包括：响应于所述第一和值满足大于所述SN值的最大允许值的目标条件，将零值确定所述候选配置值；或者，响应于所述第一和值满足小于零值的目标条件，确定所述SN值的最大允许值、所述第一和值和第二目标数值的第二和值，将所述第二和值确定所述候选配置值；或者，响应于所述第一和值满足大于所述最大允许值的一半的目标条件，将所述第一和值确定所述候选配置值。
在一种实现方式中，所述PDCP实体的接收窗口的配置方法，还包括：确定所述PDCP实体接收到第一个PDCP数据包的包头中携带的编号值，作为所述调整参数；根据所述包头中携带的编号值，配置所述接收窗口的变量。
在一种实现方式中，所述根据所述包头中携带的编号值，配置所述接收窗口的变量，包括：将所述接收窗口的下边界值和/或下一个待接收的PDCP实体的SDU的编号值配置为所述包头中携带的编号值；或者，确定所述包头中携带的编号值与第三目标数值的第三和值，将所述接收窗口的下边界值和/或下一个待接收的PDCP实体的SDU的编号值配置为所述第三和值。
在一种实现方式中，所述接收网络设备发送的指示信息，包括：接收广播消息或者广播多播业务MBS控制信道消息，其中，所述广播消息或者MBS控制信道消息用于携带所述指示信息。
在一种实现方式中，所述确定PDCP实体的接收窗口的变量对应的调整参数之前，还包括：确定满足调整所述接收窗口的变量的触发事件；其中，所述触发事件为以下事件中的至少一种：接收网络设备发送的调整指示，所述调整指示用于指示所述终端设备对所述接收窗口的变量进行调整；或者，新建MBS无线承载MRB的PDCP实体；或者，重建或者重配置MRB的PDCP实体。
第二方面，本申请实施例还提出一种PDCP实体的接收窗口的配置方法，所述方法由网络设备执行，所述方法包括：配置PDCP实体的接收窗口的变量对应的调整参数；向终端设备发送指示信息，其中，所述指示信息用于指示所述终端设备基于调整参数，配置所述PDCP实体的接收窗口的变量，所述指示信息携带所述调整参数。
本申请第二方面提出的一种PDCP实体的接收窗口的配置方法，还可以具备如下技术特征：
在一种实现方式中，所述调整参数包括所述接收窗口的窗口长度和/或边界值。
在一种实现方式中，所述调整参数包括下一个待接收的PDCP实体的业务数据单元SDU的候选编号值。
在一种实现方式中，所述调整参数包括HFN值。
在一种实现方式中，所述调整参数包括所述PDCP实体接收到第一个PDCP数据包的包头中携带的编号值。
在一种实现方式中，所述向终端设备发送指示信息，包括：向终端设备发送广播消息或者广播多播业务MBS控制信道消息，其中，所述广播消息或者MBS控制信道消息用于携带所述指示信息。
在一种实现方式中，所述向终端设备发送指示信息之前，还包括：向所述终端设备发送用于指示所述终端设备对所述接收窗口的变量进行调整的调整指示。
第三方面，本申请实施例提出一种PDCP实体的接收窗口的配置装置，该装置具有实现上述第一方面所述的方法中终端设备的部分或全部功能，比如PDCP实体的接收窗口的配置装置的功能可具备本申请中的部分或全部实施例中的功能，也可以具备单独实施本申请的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，该处理模块被配置为支持通信装置执行上述方法中相应的功能。收发模块用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储模块，所述存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
作为示例，处理模块可以为处理器，收发模块可以为收发器或通信接口，存储模块可以为存储器。
第四方面，本申请实施例提出一种PDCP实体的接收窗口的配置装置，该装置具有实现上述第二方面所述的方法中网络设备的部分或全部功能，比如PDCP实体的接收窗口的配置装置的功能可具备本申请中的部分或全部实施例中的功能，也可以具备单独实施本申请的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，PDCP实体的接收窗口的配置装置的结构中可包括收发模块和处理模块，所述处理模块被配置为支持通信装置执行上述方法中相应的功能。所述收发模块用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储模块，所述存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
作为示例，处理模块可以为处理器，收发模块可以为收发器或通信接口，存储模块可以为存储器。
第五方面，本申请实施例提出一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第一方面所述的方法。
第六方面，本申请实施例提出一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第二方面所述的方法。
第七方面，本申请实施例提出一种通信装置，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行上述第一方面所述的方法。
第八方面，本申请实施例提出一种通信装置，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行上述第二方面所述的方法。
第九方面，本申请实施例提出一种通信装置，包括：处理器和接口电路；所述接口电路，用于接收代码指令并传输至所述处理器；所述处理器，用于运行所述代码指令以执行上述第一方面所述的方法。
第十方面，本申请提出一种通信装置，包括：处理器和接口电路；所述接口电路，用于接收代码指令并传输至所述处理器；所述处理器，用于运行所述代码指令以执行上述第二方面所述的方法。
第十一方面，本申请实施例提出一种通信系统，该系统包括第三方面所述的通信装置以及第四方面所述的通信装置，或者，该系统包括第五方面所述的通信装置以及第六方面所述的通信装置，或者，该系统包括第七方面所述的通信装置以及第八方面所述的通信装置，或者，该系统包括第九方面所述的通信装置以及第十方面所述的通信装置。
第十二方面，本申请实施例提出一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使上述第一方面所述的方法被实现。
第十三方面，本申请实施例提出一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使上述第二方面所述的方法被实现。
第十四方面，本申请还提出一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十五方面，本申请还提出一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
第十六方面，本申请提出一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持终端设备实现第一方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存终端设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十七方面，本申请提出一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持网络设备实现第二方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存网络设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十八方面，本申请提出一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十九方面，本申请提出一种计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
附图说明
为了更清楚地说明本申请实施例或背景技术中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1是本申请实施例提出的一种通信系统的架构示意图；
图2是本申请一实施例的PDCP实体的接收窗口的配置方法的流程示意图；
图3是本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图；
图4是本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图；
图5是本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图；
图6是本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图；
图7是本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图；
图8是本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图；
图9是本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图；
图10是本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图；
图11是本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图；
图12是本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图；
图13是本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图；
图14是本申请一实施例的PDCP实体的接收窗口的配置装置的结构示意图；
图15是本申请一实施例的通信装置的结构示意图；
图16是本申请一实施例的芯片的结构示意图；
具体实施方式
下面详细描述本申请的实施例，实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，旨在用于解释本申请，而不能理解为对本申请的限制。
为了便于理解，首先介绍本申请涉及的术语。
1、广播多播业务(Multicast Broadcast Service，MBS)
MBS可以通过物理下行控制信道(Physical Downlink Control Channel，PDCCH)调度的物理下行共享信道(Physical Downlink Shared Channel，PDSCH)发送，其该调度MBS业务的PDCCH可以通过MBS业务特定的调度标识进行指示信息的发送，比如，通过MBS无线网络临时标识(Group Radio Network Temporary Identity,G-RNTI)进行指示。
2、分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)
PDCP是对分组数据汇聚协议的一个简称。它是UMTS中的一个无线传输协议栈，它负责将IP头压缩和解压、传输用户数据并维护为无损的无线网络服务子系统(SRNS)设置的无线承载的序列号。分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层属于无线接口协议栈的第二层，处理控制平面上的无线资源管理(RRC)消息以及用户平面上的因特网协议(IP)包。在用户平面上，PDCP子层得到来自上层的IP数据分组后，可以对IP数据分组进行头压缩和加密，然后递交到RLC子层。PDCP子层还向上层提供按序提交和重复分组检测功能。在控制平面，PDCP子层为上层RRC提供信令传输服务，并实现RRC信令的加密和一致性保护，以及在反方向上实现RRC信令的解密和一致性检查。
为了更好的理解本申请实施例提出的一种PDCP实体的接收窗口的配置方法，下面首先对本申请实施例使用的通信系统进行描述。
如图1所示，图1为本申请实施例提出的一种通信系统的架构示意图。该通信系统可包括但不限于一个网络设备和一个终端设备，图1所示的设备数量和形态仅用于举例并不构成对本申请实施例的限定，实际应用中可以包括两个或两个以上的网络设备，两个或两个以上的终端设备。图1所示的通信系统以包括一个网络设备101和一个终端设备102为例。
需要说明的是，本申请实施例的技术方案可以应用于各种通信系统。例如：长期演进(long term evolution，LTE)系统、第五代(5th generation，5G)移动通信系统、5G新空口(new radio，NR)系统，或者其他未来的新型移动通信系统等。
本申请实施例中的网络设备101是网络侧的一种用于发射或接收信号的实体。例如，网络设备101可以为演进型基站(evolved NodeB，eNB)、传输点(transmission reception point，TRP)、NR系统中的下一代基站(next generation NodeB，gNB)、其他未来移动通信系统中的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。本申请实施例提出的网络设备可以是由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将网络设备，例如基站的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
本申请实施例中的终端设备102是用户侧的一种用于接收或发射信号的实体，如手机。终端设备也可以称为终端设备(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端设备(mobile terminal，MT)等。终端设备可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备等等。本申请的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
可以理解的是，本申请实施例描述的通信系统是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提出的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本申请实施例提出的技术方案对于类似的技术问题，同样适用。
可以理解的是，本申请实施例中的多个方案，既可以单独被实施，也可以组合在一起被实施，本申请并不对此作出限定。
下面结合附图对本申请所提出的一种PDCP实体的接收窗口的配置方法及装置进行详细的介绍。
图2为本申请一实施例的PDCP实体的接收窗口的配置方法的流程示意图，该方法由终端设备执行，如图2所示，该方法包括：
S201，确定PDCP实体的接收窗口的变量对应的调整参数。
PDCP分为用于数据接收的接收实体，以及用于数据发送的发送实体，PDCP的接收实体可以将接收到PDU的数据包，按照PDCP编号值(COUNT)的顺序进行重排序，经过重排序后的PDCP数据包可以按照COUNT依次递交到高层协议实体。PDCP实体可以实现数据的加解密、定时器丢弃、重建立时重传及重排序处理。
可选地，PDCP实体的接收窗口的变量可以包括以下至少一项：接收窗口的下边界，标记为“RX_NEXT”、下一个待接收的PDCP实体的服务数据单元(Server Data Unit，SDU)的COUNT值，标记为“RX_DELIV”、下一个待接收的PDCP实体的SDU数据包的超帧号(Hyper Frame Number，HFN)值、下一个待接收的PDCP实体的SDU数据包的序列号(Serial Number，SN)值。图3为PDCP实体的接收窗口的示意图，如图3所示，接收窗口的下边界的变量为“RX_DELIV”，该“RX_DELIV”标识了第1个没有被递交到高层协议实体的PDU数据包的数据包编号。PDCP实体根据递交到高层协议实体的PDU数据包的COUNT，更新接收窗口的下边界的变量“RX_DELIV”。对于等待接收PDU数据包，PDCP实体会启动重排序定时器，当该重排序定时器超时的时候，PDCP实体忽略该“等待接收的PDU数据包的COUNT”，并更新接收窗口的下边界。如果PDCP接收到接收窗口以外的数据包，PDCP实体将该数据包丢弃。“RX_REORD”变量标识了启动重排序定时器的数据包COUNT。其中，“RX_NEXT”标记了下一个待接收的PDU数据包的数据包COUNT。如图3所示，PDCP实体的“RX_DELIV”和“RX_NEXT”的初始值为“0”。当接收到编号为“1”的PDU数据包时，则表示编号为“0”的PDU数据包未接收到。PDCP实体更新“RX_NEXT”为“2”，响应于需要启动重排序定时器时，设置“RX_REORD”为“2”。当接收到编号为“2”的PDU数据包时，更新“RX_NEXT”为“3”。
可选地，PDCP实体的接收窗口的变量的调整参数可以包括以下至少一项：接收窗口的窗口长度、接收窗口的边界值、PDCP实体接收到的第一个数据包的包头中的HFN值、该第一个数据包的包头中的SN值、该第一个数据包的包头中的COUNT值。
在一些实现中，终端设备可以根据网络设备的指示，确定PDCP实体的接收窗口的变量对应的调整参数。在另一些实现中，终端设备可以根据协议约定，确定PDCP实体的接收窗口的变量对应的调整参数。
S202，基于调整参数，配置PDCP实体的接收窗口的变量。
本申请实施例中，终端设备在确定出用于对接收窗口的变量进行调整的调整参数后，可以根据该调整参数为PDCP实体的接收窗口配置变量。可选地，终端设备可以根据确定出的调整参数，直接配置PDCP实体的接收窗口的变量。可选地，终端设备与网络设备进行协议约定，约定对调整参数进行计算的计算公式，在确定出调整参数后，基于该协议约定的计算公式，可以计算出PDCP实体的接收窗口的变量的具体配置值，基于该计算出的配置值对PDCP实体的接收窗口的变量。
本申请提出的PDCP实体的接收窗口的配置方法，终端设备确定PDCP实体的接收窗口的变量对应的调整参数，并基于获取到的调整参数实现对于PDCP实体的接收窗口变量的调整配置。本申请中，基于接收到的调整参数对PDCP实体的接收窗口的变量进行调整，实现了PDCP实体的接收窗口变量的及时更新，使得新的终端设备可以随时加入进行MBS数据的接收，保证了MBS数据传输的持续性以及 可靠性。
图4为本申请一实施例的PDCP实体的接收窗口的配置方法的流程示意图，该方法由终端设备执行，如图4所示，该方法包括：
S401，确定PDCP实体的接收窗口的变量对应的调整参数。
作为一种可能的实现方式，终端设备可以接收网络设备发送的指示信息，指示信息携带调整参数。
本申请实施例中，网络设备可以向终端设备发送指示信息，其中，指示信息中携带有调整参数，该调整参数可以用于实现PDCP实体的接收窗口变量的调整，相应地终端设备可以接收到网络设备发送的携带调整参数的指示信息。关于调整参数的具体介绍可参见本申请各实施例中相关内容的记载，此次不再赘述。
可选地，终端设备可以接收网络设备发送的广播消息，其中，该广播消息中携带指示信息。比如，网络设备可以通过无线资源控制(Radio Resource Control，RRC)信令，为终端设备配置MRB-1的PDCP实体，可以理解为，在RRC信令中携带有该PDCP实体的接收窗口的变量对应的调整参数，终端设备接收网络设备发送的RRC信令，可以确定PDCP实体的接收窗口的变量对应的调整参数。
可选地，终端设备可以接收广播多播业务MBS控制信道消息，其中，MBS控制信道消息用于携带指示信息。比如，网络设备可以通过多播控制信道(Multimedia Control Channel，MCCH)，MCCH为空口的一个逻辑信道，可以实现MBS控制信令的发送。网络设备通过MCCH发送控制信令，为终端设备配置MRB-1的PDCP实体。可以理解为，在控制信令中携带有接收窗口的变量的对应的调整参数，终端设备接收网络设备发送的控制信令，可以确定PDCP实体的接收窗口的变量对应的调整参数。
在一些实现中，网络设备所发送的调整参数可以包括接收窗口的长度，也可以包括接收传窗口的边界值，也可以同时包括上述两个调整参数。其中，接收窗口的边界值可以为接收窗口的候选下边界值，也可以为接收窗口的候选上边界值，还可以同时包括接收窗口的候选上边界值和接收窗口的候选下边界值。
S402，响应于调整参数包括接收窗口的窗口长度和/或边界值，根据窗口长度和/或边界值，配置接收窗口的变量。
可选地，响应于边界值为接收窗口的候选下边界值，终端设备可以基于该候选下边界值，对接收窗口的变量进行调整。实现中终端设备可以直接将接收窗口的下边界值配置为该候选下边界值，即终端设备将RX_DELIV配置为该候选下边界值。
比如，设定网络设备发送的指示信息所需携带的接收窗口的候选下边界值RX_DELIV＝4，则对于多播发送，网络设备可以通过RRC信令为终端设备配置MRB-1的PDCP实体，其中，RRC信令携带PDCP实体的接收窗口的候选下边界值，进而终端设备可以将该PDCP实体的接收窗口的下边界值配置为4，即配置RX_DELIV＝4，其中，MRB-1可以为MBS业务的承载标识，RRC信令可以为RRC连接重新配置(RRC Connection Reconfiguration)信令。
再比如，设定网络设备发送的指示信息所需携带的接收窗口的候选下边界值RX_DELIV＝4，则对于广播发送，网络设备可以通过MCCH发送控制信令，为终端设备配置MRB-1的PDCP实体，其中，控制信令携带PDCP实体的接收窗口的候选下边界值，进而终端设备可以该PDCP实体的接收窗口的下边界值配置为4，即配置RX_DELIV＝4。
可选地，响应于边界值为接收窗口的候选上边界值，根据窗口长度和候选上边界值，对接收窗口的变量进行调整。实现中终端设备基于窗口长度和候选上边界值，确定接收窗口的候选下边界值，并将接收窗口的下边界值配置为候选下边界值。也就是说，当终端设备接收网络设备发送的接收窗口变量对应的调整参数为接收窗口的候选上边界值时，为了实现对于接收窗口下边界值的调整配置，终端设备还需根据接收窗口的窗口长度，候选下边界值，并将接收窗口的下边界这一变量的值直接配置为该候选下边界值，即终端设备将RX_DELIV配置为该候选下边界值。
比如，设定网络设备发送的指示信息所需携带的接收窗口的候选上边界值为7，PDCP的实体的接收窗口长度为4，则对于多播发送，网络设备可以通过RRC信令，为终端设备配置MRB-1的PDCP实体，RRC信令携带有接收窗口的候选上边界值为7，基于获取到的接收窗口的候选上边界值以及PDCP实体的接收窗口的窗口长度，终端设备可以确定该PDCP实体的接收窗口的候选下边界值RX_DELIV＝(7-window_size+1)＝(7-4+1)＝4。进一步地，终端设备将接收窗口的RX_DELIV配置为该候选下 边界值。再比如，设定网络设备发送的指示信息所需携带的接收窗口的候选上边界值为7，PDCP实体的接收窗口长度为4，则对于广播发送，网络设备可以通过MCCH发送控制信令，为终端设备配置MRB-1的PDCP实体，其中，控制信令携带有接收窗口的候选上边界值为7，基于获取到的接收窗口的候选上边界值以及PDCP实体的接收窗口的窗口长度，终端设备可以确定该PDCP实体的接收窗口的候选下边界值RX_DELIV＝(7-window_size+1)＝(7-4+1)＝4。进一步地，终端设备将接收窗口的RX_DELIV配置为该候选下边界值。
本申请提出的PDCP实体的接收窗口的配置方法，接收网络设备发送的携带有调整参数的指示信息，并基于获取到的调整参数实现对于PDCP实体的接收窗口的下边界值的调整。本申请中，通过获取到的网络设备发送的候选下边界值或者候选上边界值以及窗口长度，可以实现对于接收窗口下边界值的调整，使得PDCP实体的接收窗口变量的及时更新，进而实现了新的终端设备可以随时加入进行MBS数据的接收，保证了MBS数据传输的持续性以及可靠性。
上述实施例中，对于PDCP实体的接收窗口的变量调整方法，还可以包括图5，图5为本申请一实施例的PDCP实体的接收窗口的配置方法的流程示意图，该方法由终端设备执行，如图5所示，该方法包括：
S501，确定PDCP实体的接收窗口的变量对应的调整参数。
步骤S501可参见本申请任一实施例中相关内容的记载，此处不再赘述。
可选地，调整参数包括下一个待接收的PDCP实体的SDU的候选编号值。
S502，响应于调整参数包括下一个待接收的PDCP实体的SDU的候选编号值，将接收窗口的下一个待接收的PDCP实体的SDU的编号值配置为候选编号值。
本申请实施例中，响应于获取到的调整参数为下一个待接收的PDCP实体的服务数据单元(service data unit，SUD)的候选编号值，终端设备可以基于该SDU的候选编号值，对PDCP实体的接收窗口的变量进行调整。实现中终端设备可以将PDCP实体的接收窗口对应的下一个待接收的PDCP实体的SDU的编号直接配置SDU的候选编号值，即终端设备将接收窗口的RX_NEXT配置为该候选编号值。
比如，设定下一个待接收的PDCP实体的SDUCOUNT的候选配置值为RX_NEXT＝4，则对于多播发送，网络设备可以通过RRC信令，为终端设备配置MRB-1的PDCP实体，RRC信令携带有接收窗口的下一个待接收的PDCP实体的SDUCOUNT的候选配置值，终端设备可以确定该PDCP实体的接收窗口的下一个待接收的PDCP实体的SDU的COUNT为4。进一步地，终端设备将接收窗口的下一个待接收的PCDP实体的SDU的COUNT配置4，即配置RX_NEXT＝4。
再比如，设定下一个待接收的PDCP实体的SDUCOUNT的候选配置值为RX_NEXT＝4，则对于广播发送，网络设备可以通过MCCH发送控制信令，为终端设备配置MRB-1的PDCP实体，控制信令携带有下一个待接收的PDCP实体的SDUCOUNT的候选配置值，终端设备可以确定该PDCP实体的接收窗口的下一个待接收的PDCP实体的SDUCOUNT为4。进一步地，终端设备将下一个待接收的PCDP实体的SDUCOUNT配置为4，即配置RX_NEXT＝4。
本申请提出的PDCP实体的接收窗口的配置方法，将下一个待接收的PCDP实体的SDU编号值配置为候选编号值，可以实现PCDP实体的SDU编号值的调整，使得PDCP实体的接收窗口变量的及时更新，进而实现了新的终端设备可以随时加入进行MBS数据的接收，保证了MBS数据传输的持续性以及可靠性。
图6为本申请一实施例的PDCP实体的接收窗口的配置方法的流程示意图，该方法由终端设备执行，如图6所示，该方法包括：
S601，确定PDCP实体的接收窗口的变量对应的调整参数。
步骤S601可参加上述相关详细内容，此处不再赘述。
可选地，调整参数包括下一个待接收的PDCP实体的SDU的HFN值。
S602，响应于调整参数包括HFN值，确定PDCP实体接收到第一个PDCP数据包的包头中SN值。
下一个待接收的PDCP实体的SDU的编号值(COUNT)由HFN值和PDCPSN值两个部分共同组成，如图7所示，其中，PDCP SN值可以由第一个PDCP数据包的包头中携带的SN值确定，HFN值可以由网络设备通过RRC信令或者MCCH发送的控制信令向终端设备指示。本申请实施例中，为了确定下一个待接收的PDCP实体的SDU的COUNT，可以理解为，调整参数还需要包括SN值，终端设备侧的PDCP实体可以接收网络设备发送的PDCP数据包，在接收到第一个PDCP数据包时，终端设备可以基于该第一个PDCP数据包的包头中携带的SN值确定调整参数中的SN值。
需要说明的是，PDCP SN值在达到最大值后会进行翻转，在该场景下，HFN值加一，比如，设定PDCP SN值取值范围为[0，7]，PDCP SN＝7之前的HFN值为0，则当PDCP SN＝7之后HFN值为1。
S603，根据HFN值和SN值，配置接收窗口的变量。
本申请实施例中，终端设备基于调整参数SN值和HFN值，可以对PDCP实体的接收窗口的变量进行调整，其中，接收窗口调整的变量，可以是接收窗口的下边界值，也可以是下一个待接收的PDCP SDU的编号值。
进一步地，根据HFN值，配置接收窗口的变量的HFN部分。
可选地，将接收窗口的下边界值和/或下一个待接收的PDCP SDU的编号值的HFN部分，配置为HFN值。
终端设备获取到网络设备配置的HFN值后，基于获取到的HFN值，针对接收窗口的下边界值和/或下一个待接收的PDCP SDU的编号值中所包括的HFN部分，进行调整配置。在一些实现方式中，还可以根据接收窗口的下边界值以及其他参数，进行调整配置。在另一些实现方式中，还可以根据下一个待接收的PDCP SDU的编号值中所包括的HFN部分以及其他参数，进行调整配置。
比如，设定当前状态下接收窗口的下边界值中的HFN部分的数值为1，网络设备通过RRC信令配置HFN＝2，则基于获取到的HFN＝2，将接收窗口的下边界值中的HFN部分的数值调整为2。
再比如，设定当前状态下PDCP实体的下一个待接收的PDCP SDU的编号值中的HFN部分的数值为2，网络设备通过RRC信令配置HFN＝3，则基于获取到的HFN＝3，将PDCP实体的下一个待接收的PDCP SDU的编号值中的HFN部分的数值调整为3。
进一步地，根据SN值，配置接收窗口的变量的SN部分。
作为一种可能的实现方式，确定SN值与第一目标数值的第一和值。其中，该第一目标值为网络设备指示或者协议约定的一个整数值。
终端设备接收到的第一个PDCP数据包，可以从该第一个PDCP数据包的包头中解析出SN值，进一步地，将包头中的SN值与第一目标数值相加，获取到结果数值即为第一和值。进一步地，根据第一和值配置接收窗口的变量的SN部分。
比如，设定第一目标数值为a，终端设备接收到的第一个PDCP数据包的包头中的SN值为3，第一目标数值a为1，则第一和值为3+1＝4。
可选地，可以根据SN值的最大允许值预先设置有不同的条件，在满足不同的条件时可以SN部分可以对应有不同的候选配置值。终端设备可以先确定第一和值所满足的目标条件，并将目标条件对应的配置值，确定为用于对接收窗口的变量进行配置的候选配置值。进一步地，终端将接收窗口的下边界值和/或下一个待接收的PDCP SDU的编号值的SN部分配置为候选配置值。
在一些实现中，响应于第一和值满足大于SN值的最大允许值的目标条件，将零值确定候选配置值。进一步地，终端设备将接收窗口的变量中的SN部分的取值配置为0。也就是说，终端设备可以将接收窗口的下边界值RX_DELIV中的SN部分的配置为0，或者将下一个待接收的PDCP SDU的编号值RX_NEXT中的SN部分的配置为0。
比如，设定PDCP中的SN值的取值范围为[0，7]，终端设备接收的MRB的第一个PDCP数据包的包头中指示SN＝7，a＝1，则第一和值为7+1＝8，此时，第一和值的数值大于PDCP中的SN值可取值的最大数值。进一步地，将0作为接收窗口的变量中的SN部分的候选配置值，比如，接收窗口的下边界值RX_DELIV中的SN部分的候选配置值可以为0，或者下一个待接收的PDCP SDU的编号值RX_NEXT中的SN部分的候选配置值可以为0。
在另一些实现中，响应于第一和值满足小于零值的目标条件，确定SN值的最大允许值、第一和值和第二目标数值的第二和值，将第二和值确定候选配置值。进一步地，终端设备将接收窗口的变量中的SN部分的取值配置为第二和值。也就是说，终端设备可以将接收窗口的下边界值RX_DELIV中的SN部分的配置为第二和值，或者将下一个待接收的PDCP SDU的编号值RX_NEXT中的SN部分的配置为第二和值。
本申请实施例中，网络设备会为PDCP实体接收到的第一个PDCP数据包的包头配置另一个整数值，该整数值也可以是由预先签订的协议约定，为第二目标数值。可以将PDCP的SN值可取的最大值、第一和值以及第二目标数值相加，进而获取到第二和值。
当第一和值小于零时，可以将第二和值确定为接收窗口的变量中的SN部分调整的候选配置值。
比如，设定PDCP中的SN值的取值范围为[0，7]，第二目标数值为b，终端设备接收的MRB的第一个PDCP数据包的包头中SN＝1，a＝-2，b＝1，且PDCP实体SN值的最大允许值为7，此时，第一和值为-2+1＝-1小于0，终端设备可以该SN值的最大允许值、第一和值以及第二目标数值，获取到第二和值为7+1-2+1＝7，进一步地，将第二和值7作为接收窗口的变量中的SN部分调整的候选配置值。比如，接收窗口的下边界值RX_DELIV中的SN部分候选配置值可以为7，或者下一个待接收的PDCP SDU的编号值RX_NEXT中的SN部分候选配置值可以为7。
在又一些实现中，响应于第一和值满足大于最大允许值的一半的目标条件，将第一和值确定候选配 置值。进一步地，终端设备将接收窗口的变量中的SN部分的取值配置为第一和值。也就是说，终端设备可以将接收窗口的下边界值RX_DELIV中的SN部分的配置为第一和值，或者可以将下一个待接收的PDCP SDU的编号值RX_NEXT中的SN部分的配置为第一和值。
本申请实施例中，当第一和值大于PDCP中的SN值的取值范围中可取值的前一半中的最大值时，则可以将第一和值确定为接收窗口的变量中的SN部分的调整候选配置值。
比如，设定PDCP中的SN值的取值范围为[0，7]，终端设备接收的MRB的第一个PDCP数据包的包头中SN＝4，a＝1，则SN值的取值范围中可取值的前一半为[0，3]，其中，最大允许值的一半为3。基于第一个PDCP数据包的包头中SN＝4，a＝1获取第一和值为4+1＝5，此时，第一和值大于SN值的最大允许值的一半。进一步地，终端设备将第一和值确定为接收窗口的变量中的SN部分的调整候选配置值，比如，接收窗口的下边界值RX_DELIV中的SN部分候选配置值可以为5，或者下一个待接收的PDCP SDU的编号值RX_NEXT中的SN部分候选配置值可以为5。
进一步地，确定接收窗口的变量中的SN部分的候选配置值后，可以基于获取到的候选配置值，为接收窗口的某一个变量中的SN部分的数值进行调整。
可选地，当候选配置值为0时，可以将接收窗口的下边界值RX_DELIV中的SN部分的配置为0，或者可以将下一个待接收的PDCP SDU的编号值RX_NEXT中的SN部分的配置为0。
可选地，当候选配置值为第二和值时，若第二和值为7，则可以将接收窗口的下边界值RX_DELIV中的SN部分配置为7，或者将下一个待接收的PDCP SDU的编号值RX_NEXT中的SN部分配置为7。
可选地，当候选配置值为第一和值时，若第一和值为7，则可以将接收窗口的下边界值RX_DELIV中的SN部分配置为7，或者将下一个待接收的PDCP SDU的编号值RX_NEXT中的SN部分配置为7。
需要特别说明的是，通过第一目标数值、第二目标数值的合理配置，可以使得PDCP实体的接收窗口在接收新的终端设备加入后的下边界值保持在一个合理范围内，进而有效减少数据包的丢失。
本申请提出的PDCP实体的接收窗口的配置方法，基于获取到的SN值以及HFN值，对PDCP实体的接收窗口的变量进行调整，实现了PDCP实体的接收窗口变量的及时更新，使得新的终端设备可以随时加入进行MBS数据的接收，保证了MBS数据传输的持续性以及可靠性。
图8为本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图，该方法执行主体为终端设备，如图8所示，该方法包括：
S801，确定PDCP实体接收到第一个PDCP数据包的包头中携带的编号值，作为调整参数。
本申请实施例中，可以通过变更PDCP实体接收到的第一个PDCP数据包的包头的内容，直接向终端设备指示编号值，并将该编号值作为接收窗口的变量的调整参数。
S802，根据包头中携带的编号值，配置接收窗口的变量。
本申请实施例中，可以根据获取到的调整参数，为接收窗口的变量进行调整配置。
可选地，将接收窗口的下边界值和/或下一个待接收的PDCP实体的SDU的编号值配置为包头中携带的编号值。
比如，设定第一个PDCP数据包的包头指示的编号值为4，则可以将接收窗口的下边界值RX_DELIV中的SN部分配置为4，或者将下一个待接收的PDCP SDU的编号值RX_NEXT中的SN部分配置为4。
可选地，确定包头中携带的编号值与第三目标数值的第三和值，将接收窗口的下边界值和/或下一个待接收的PDCP实体的SDU的编号值配置为第三和值。
本申请实施例中，网络设备会为PDCP实体接收到的第一个PDCP数据包的包头配置另一个整数值，该整数值也可以是由预先签订的协议约定，为第三目标数值。可以将第一个PDCP数据包的包头指示的编号值与第三目标值相加，进而获取到第三和值。
比如，设定第一个PDCP数据包的包头指示的编号值为4，第三目标值c为1，则第三和值为4+1＝5。进一步地，可以将接收窗口的下边界值RX_DELIV中的SN部分配置为5，或者将下一个待接收的PDCP SDU的编号值RX_NEXT中的SN部分配置为5。
需要特别说明的是，通过第三目标数值的合理配置，可以使得PDCP实体的接收窗口在接收新的终端设备加入后的下边界值保持在一个合理范围内，进而有效减少数据包的丢失。
本申请提出的PDCP实体的接收窗口的调整方法，通过第一个PDCP数据包的包头指示的编号值作为候选配置值，对接收窗口的变量进行调整配置，实现了PDCP实体的接收窗口变量的及时更新，使得新的终端设备可以随时加入进行MBS数据的接收，保证了MBS数据传输的持续性以及可靠性。
图9为本申请一实施例的PDCP实体的接收窗口的配置方法的流程示意图，该方法由终端设备执行，如图9所示，该方法包括：
S901，接收网络设备发送的指示信息，指示信息携带调整参数。
步骤S901可参加上述相关详细内容，此处不再赘述。
S902，确定满足调整接收窗口的变量的触发事件。
本申请实施例中，PDCP实体的接收窗口的变量调整可以基于触发事件开始进行，其中，触发事件可以由网络设备进行配置，也可以由预先设定的协议约定。
作为一种可能的实现方式，触发事件为接收网络设备发送的调整指示，调整指示用于指示终端设备对接收窗口的变量进行调整。
本申请实施例中，网络设备可以将触发事件配置指示至终端设备，终端设备基于获取到的调整指示，开始对接收窗口的变量进行调整。
作为另一种可能的实现方式，触发事件为新建MBS无线承载MRB的PDCP实体。
本申请实施例中，可以将新建MBS无线承载MRB的PDCP实体作为触发事件，当开始新建立一个MBS无线承载MRB的PDCP实体时，可以触发一个开始调整的指示至终端设备，终端设备基于获取到的指示开始调整接收窗口的变量。
作为另一种可能的实现方式，触发事件为重建或者重配置MRB的PDCP实体。
本申请实施例中，可以将MRB的PDCP实体的重建或者重配置作为触发事件，实现中重建与重配置具备相同的功能。
MBS业务可以通过特定的无线承载(MBS Radio Bearer，MRB)进行发送，其中，承载MBS业务的无线承载的协议栈结构可以是普通MBS承载，也可以是分离MBS承载。
其中，普通MBS承载，包括1个PDCP关联1个无线链路控制(Radio Link Control，RLC)实体，该RLC实体的数据通过G-RNTI PDCCH调度发送。分离MBS承载，包括1个PDCP关联2个RLC实体，其中一个RLC实体的数据通过G-RNTI PDCCH调度发送，可以理解为多播承载，另一个RLC实体的数据通过无线网络临时标识(Cell-Radio Network Temporary Identifier，C-RNTI)PDCCH调度发送，可以理解为单播承载。当然，上述实施例并不排除1个PDCP关联两个以上RLC实体的实施方式，而其原理与1个PDCP关联2个RLC实体的分离MBS承载的原理相同，在此不再赘述。
可选地，针对MRB的PDCP实体的重配置，可以从“单播承载”重配置为“多播承载”。
比如，设定当前的MBS业务-1通过DRB-1进行发送，网络设备将MBS业务-1的发送方式进行重配置，通过RRC信令将该MBS业务-1的发送方式重配置为通过MRB-1发送。
此时，可以将该重配置的行为作为触发事件，进而开始对接收窗口的变量的调整。
可选地，针对MRB的PDCP实体的重配置，可以从“分离MBS承载”重配置为“普通MBS承载”。
比如，设定当前的MBS业务-1通过MRB-1发送，MRB-1的承载类型为“分离MBS承载”，网络设备通过RRC信令将该MRB-1的承载类型重配置为“普通MBS承载”。
此时，可以将该重配置的行为作为触发事件，进而开始对接收窗口的变量的调整。
可选地，针对MRB的PDCP实体的重配置，可以将“分离MBS承载”的数据接收从单播路径转换到多播路径。
比如，设定当前的MBS业务-1通过MRB-1发送，MRB-1的承载类型为“分离MBS承载”，包括单播路径和多播路径，终端设备通过MRB-1的单播路径接收MBS业务-1。网络设备通过发送指示信令，将MRB-1的MBS业务-1的接收路径从单播路径变更为多播路径。
此时，可以将该重配置的行为作为触发事件，进而开始对接收窗口的变量的调整。
需要特别说明的是，上述的触发事件可以包括上述步骤S802～S804中描述的至少一种。
S903，基于调整参数，配置PDCP实体的接收窗口的变量。
本申请实施例中，触发事件发生后，终端设备可以基于触发事件的发生开始进行PDCP实体的接收窗口的变量的调整，详细的调整方法可以参加上述相关详细内容，此处不再赘述。
本申请提出的PDCP实体的接收窗口的调整方法，通过触发事件使得PDCP实体的接收窗口的变量调整可以开始进行，保证了接收窗口的变量更新的稳定实施，进而保证了MBS数据传输的持续性以及可靠性。
图10为本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图，如图10所示，该方法包括：
S1001，接收网络设备发送的用于配置MBS业务的多播承载配置信息。
本申请实施例中，终端设备里接收网络设备发送的配置信息，该配置欣喜用于配置MBS业务的多播承载配置信息。
其中，该多播承载配置信息包括：MBS业务信息。其中，该MBS业务信息包括以下至少一项。
可选地，MBS业务信息可以为MBS业务标识。
实现中，MBS业务可以通过PDCCH调度的PDSCH发送，该调度MBS业务的PDCCH可以通过MBS业务特定的调度标识进行指示，其中，MBS业务标识可以为临时移动组标识(Temporary Mobile  Group Identity，TMGI)，也可以为MBS会话标识(MBS Session ID)，又可以为MBS业务流标识(MBS QoS flow ID)。
可选地，MBS业务信息可以为MBS承载标识，比如，MRB-1。
可选地，MBS业务信息可以为MBS承载的协议实体配置，比如，PDCP配置。
S1002，根据多播承载配置信息，建立对应的MRB，以及MRB对应的PDCP实体。
MBS业务可以通过特定的MRB进行发送，可以承载MBS业务的MRB可以包括普通MBS承载，也可以包括分离MBS承载。如图11所示，普通MBS承载，包括一个PDCP关联一个RLC实体，该RLC实体的数据通过G-RNTI PDCCH调度发送。分离MBS承载，包括一个PDCP关联两个RLC实体，一个RLC实体的数据通过G-RNTI PDCCH调度发送，即多播，一个RLC实体的数据通过C-RNTI PDCCH调度发送，即单播。
本申请实施例中，终端设备需要建立起PDCP实体才能实现对于MBS业务发送信息的接收。根据多播承载配置信息，建立对应的MRB，进而，基于MRB建立对应的PDCP实体。
可选地，针对多播的发送方式，MRB可以采用普通MBS承载，进一步地，基于普通MBS承载的结构，建立对应的PDCP实体。网络设备通过终端设备对应的信令将MBS业务的配置信息发送给终端设备。
可选地，针对广播的发送方式，MBS可以采用普通MBS承载或者分离MBS承载，进而建立对应的PDCP实体。该场景下，网络设备通过系统信息和MBS控制信道信息将MBS业务的配置信息发送给终端设备。
S1003，确定PDCP实体的接收窗口的变量对应的调整参数。
S1004，基于调整参数，配置PDCP实体的接收窗口的变量。
步骤S1003～步骤S1004可参加上述相关详细内容，此处不再赘述。
本申请提出的PDCP实体的接收窗口的配置方法，基于不同的MRB建立对应的PDCP实体，为终端设备接收MBS业务信息提供了承载，保证了接收窗口的变量更新的稳定实施，进而保证了MBS数据传输的持续性以及可靠性。
为了实现上述实施例提出的PDCP实体的接收窗口的调整方法，本申请还提出一种PDCP实体的接收窗口的调整方法，该方法执行主体为网络设备，如图12所示，图12为本申请另一实施例的PDCP实体的接收窗口的调整方法的流程示意图，该方法包括：
S1201，配置PDCP实体的接收窗口的变量对应的调整参数。
本申请实施例中，为了新的终端设备可以实现随时加入并进行MBS数据的接收，PDCP实体的接收窗口需要根据终端设备加入的情况随时调整，进一步地，网络设备基于终端设备的动态调整，为终端设备配置特定承载的PDCP实体的接收窗口的变量的调整参数。
可选地，接收窗口的变量可以包括一项至少一项：接收窗口的窗口长度、接收窗口的边界值、PDCP实体接收到的第一个数据包的包头中的HFN值、该第一个数据包的包头中的SN值、该第一个数据包的包头中的COUNT值。
可选地，接收窗口的变量的调整参数可以包括一项至少一项：接收窗口的窗口长度的候选配置值、接收窗口的边界值的候选配置值、PDCP实体接收到的第一个数据包的包头中的HFN值的候选配置值、该第一个数据包的包头中的SN值的候选配置值、该第一个数据包的包头中的COUNT值的候选配置值。
可选地，调整参数包括接收窗口的窗口长度和/或边界值。
本申请实施例中，接收窗口下边界值的变化可以影响其内可容纳的终端设备的数量，网络设备可以基于接收窗口中终端设备容量的需求为终端设备配置调整参数，为了实现对于接受窗口下边界值的调整，网络设备所配置并发送给终端设备的调整参数中，可以包括下边界值的候选配置值，也可以包括上边界值的候选配置值以及窗口长度，终端设备可以基于获取到的上边界值候选配置值以及窗口长度获取下边界值的候选配置值，进而达到调整接收窗口的下边界值的目的。
可选地，调整参数包括下一个待接收的PDCP实体的业务数据单元SDU的候选编号值。
本申请实施例中，下一个待接收的PDCP实体的SDU编号值是由SN值以及HFN值组成，终端设备可以基于下一个待接收的PCDP实体的SDU编号值中携带的SN值实现接收窗口变量中SN部分的调整，可以基于下一个待接收的PCDP实体的SDU编号值中携带的HFN值实现接收窗口变量中HFN部分的调整，进而实现接收窗口变量的调整。
进一步地，调整参数可以包括HFN值。
为了调整接收窗口的变量中的HFN部分，网络设备可以通过RRC信令为终端设备配置HFN值。
进一步地，调整参数可以包括PDCP实体接收到第一个PDCP数据包的包头中携带的编号值。
接收窗口的变量中的SN部分的候选配置值，可以基于下一个待接收的PDCP实体的SDU的编号 值中携带的SN值确定，进一步地，下一个待接收的PDCP实体的SDU的编号值中的SN值需要由PDCP实体接收到的第一个PDCP数据包的包头中携带的SN值确定。为了实现接收窗口的变量中的SN部分的调整，网络设备需要为终端设备所接收到的第一个PDCP数据包的包头中配置SN值。
S1202，向终端设备发送指示信息，其中，指示信息用于指示终端设备基于调整参数，配置PDCP实体的接收窗口的变量，指示信息携带调整参数。
本申请实施例中，网络设备基于为PDCP实体待接收窗口的变量配置的调整参数，生成指示信息，并将指示信息发送至终端设备，使得终端设备可以基于指示信息中携带的调整参数，实现接收窗口的变量的调整。
进一步地，向终端设备发送广播消息或者广播多播业务MBS控制信道消息，其中，广播消息或者MBS控制信道消息用于携带指示信息。
网络设备可以发送广播消息或者广播多播业务MBS控制信道消息至终端设备，可以在广播消息或者MBS控制信道消息中携带指示信息，终端设备基于获取到的广播消息或者MBS控制信道消息获取携带有调整参数的指示信息，进而完成接收窗口的变量的调整。
可选地，可以采用普通MBS承载，选择广播多播业务的发送模式，实现网络设备将配置信息发送至终端设备，终端设备进入连接态，并接收MBS业务发送的配置信息，以达到接收MBS业务数据的目的。
可选地，可以采用普通MBS承载或分离MBS承载，选择广播发送模式，网络设备可以通过系统信息和MBS控制信道信息，将MBS业务的接收配置信息发送给终端设备。其中，系统消息可以是系统信息块(System Information Block，SIB)，MBS控制信道信息可以是MCCH。
终端设备可以在空闲(IDLE)或非激活(INACTIVE)状态接收MBS业务的发送配置信息，以达到接收MBS业务数据的目的。
需要特别说明的是，调整参数可以携带有接收窗口的候选边界值、下一个待接收的PDCP SDU的COUNT值、HFN值等等，网络设备通过广播消息或MBS控制信道消息发送调整参数至终端设备时，消息中携带有调整参数以及其它配置信，比如系统信息块(System Information Block，SIB)1中的初始接入信息。
针对调整参数中的HFN值的变更，终端设备需要主动读取系统信息以获取变更后的HFN值，网络设备不会发送针对HFN值变更的指示信息。
进一步地，在HFN值变更的场景下，当其它配置信息发生变更时，比如SIB1中的初始接入信息发生变更，可以理解为，当前的PDCP实体的接收窗口的变量需要进行调整。网络设备需要基于为终端设备配置的候选调整参数生成指示信息，并发送至终端设备，指示终端设备基于该指示信息进行接收窗口的变量的调整，该场景下网络设备发送的指示信息中携带有变更后的HFN值。
其中，变更指示信息可以是SIB消息对应的paging short message，也可以是MCCH消息对应的MCCH change notification。
本申请提出的PDCP实体的接收窗口的配置方法，执行主体为网络设备，网络设备为PDCP实体的接收窗口的变量配置调整参数，并基于配置的调整参数生成指示信息，发送至终端设备，为接收窗口调整其变量提供了候选配置值，实现了PDCP实体的接收窗口变量的及时更新，使得新的终端设备可以随时加入进行MBS数据的接收，保证了MBS数据传输的持续性以及可靠性。
图13为本申请另一实施例的PDCP实体的接收窗口的配置方法的流程示意图，该方法执行主体为网络设备，如图13所示，该方法包括：
S1301，向终端设备发送用于指示终端设备对接收窗口的变量进行调整的调整指示。
本申请实施例中，终端设备可以基于网络设备发送的调整指示，确定需要对接收窗口的变量进行调整，可以理解为，该网络设备发送的调整指示可以作为一个触发事件，触发终端设备对接收窗口的变量进行调整。
可选地，响应于确定需要为终端设备新建MBS无线承载MRB的PDCP实体时，网络设备可以向终端设备发送调整指示；可选地，响应于确定需要为终端设备重建或者重配置MRB的PDCP实体，可以向终端设备发送调整指示。
S1302，配置PDCP实体的接收窗口的变量对应的调整参数。
S1303，向终端设备发送指示信息，其中，指示信息用于指示终端设备基于调整参数，配置PDCP实体的接收窗口的变量，指示信息携带调整参数。
步骤S1302～S1303可参加上述相关详细内容，此处不再赘述。
本申请提出的PDCP实体的接收窗口的配置方法，网络设备发送调整指示信息至终端设备，使得终端设备可以准确的实现对于PDCP实体的接收窗口的变量的调整，保证了MBS数据传输的持续性以及 可靠性。
上述本申请提出的实施例中，分别从网络设备、终端设备的角度对本申请实施提出的方法进行了介绍。为了实现上述本申请实施例提出的方法中的各功能，网络设备和终端设备可以包括硬件结构、软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能可以以硬件结构、软件模块、或者硬件结构加软件模块的方式来执行。
如图14所示，图14为本申请一实施例的PDCP实体的接收窗口的配置装置的结构示意图，该PDCP实体的接收窗口的配置装置1400可以包括：收发模块141和处理模块142，其中：
收发模块141可包括发送模块和/或接收模块，发送模块用于实现发送功能，接收模块用于实现接收功能，收发模块141可以实现发送功能和/或接收功能。
PDCP实体的接收窗口的配置装置1400，为终端设备，包括：
收发模块141，用于确定PDCP实体的接收窗口的变量对应的调整参数；
处理模块142，用于基于调整参数，配置PDCP实体的接收窗口的变量。
收发模块141，还用于：接收网络设备发送的指示信息，指示信息携带调整参数。
处理模块142，还用于：响应于调整参数包括接收窗口的窗口长度和/或边界值，根据窗口长度和/或边界值，配置接收窗口的变量。
处理模块142，还用于：响应于边界值为接收窗口的候选下边界值，将接收窗口的下边界值配置为候选下边界值。
处理模块142，还用于：响应于边界值为接收窗口的上边界值，根据窗口长度和目标上边界值，确定接收窗口的候选下边界值，并将接收窗口的下边界值配置为候选下边界值。
处理模块142，还用于：响应于调整参数包括下一个待接收的PDCP实体的业务数据单元SDU的候选编号值，将接收窗口的下一个待接收的PDCP实体的SDU的编号值配置为候选编号值。
处理模块142，还用于：响应于调整参数包括HFN值，确定PDCP实体接收到第一个PDCP数据包的包头中SN值；根据HFN值和SN值，配置接收窗口的变量。
处理模块142，还用于：根据HFN值，配置接收窗口的变量的HFN部分；根据SN值，配置接收窗口的变量的SN部分。
处理模块142，还用于：将接收窗口的下边界值和/或下一个待接收的PDCP SDU的编号值的HFN部分，配置为HFN值。
处理模块142，还用于：确定SN值与第一目标数值的第一和值；根据第一和值配置接收窗口的变量的SN部分。
处理模块142，还用于：响应于第一和值所满足的目标条件，确定目标条件对应的候选配置值；将接收窗口的下边界值和/或下一个待接收的PDCP SDU的编号值的SN部分配置为候选配置值。
处理模块142，还用于：响应于第一和值满足大于SN值的最大允许值的目标条件，将零值确定候选配置值；或者，响应于第一和值满足小于零值的目标条件，确定SN值的最大允许值、第一和值和第二目标数值的第二和值，将第二和值确定候选配置值；或者，响应于第一和值满足大于最大允许值的一半的目标条件，将第一和值确定候选配置值。
收发模块141，还用于确定PDCP实体接收到第一个PDCP数据包的包头中携带的编号值，作为调整参数；
处理模块142，还用于根据包头中携带的编号值，配置接收窗口的变量。
处理模块142，还用于：将接收窗口的下边界值和/或下一个待接收的PDCP实体的SDU的编号值配置为包头中携带的编号值；或者，确定包头中携带的编号值与第三目标数值的第三和值，将接收窗口的下边界值和/或下一个待接收的PDCP实体的SDU的编号值配置为第三和值。
收发模块141，还用于：接收广播消息或者广播多播业务MBS控制信道消息，其中，广播消息或者MBS控制信道消息用于携带指示信息。
处理模块142，还用于：确定满足调整接收窗口的变量的触发事件；其中，触发事件为以下事件中的至少一种：接收网络设备发送的调整指示，调整指示用于指示终端设备对接收窗口的变量进行调整；或者，新建MBS无线承载MRB的PDCP实体；或者，重建或者重配置MRB的PDCP实体。
PDCP实体的接收窗口的配置装置1400，为网络设备，包括：
处理模块142，用于配置PDCP实体的接收窗口的变量对应的调整参数；
收发模块141，用于向终端设备发送指示信息，其中，指示信息用于指示终端设备基于调整参数，配置PDCP实体的接收窗口的变量，指示信息携带调整参数。
处理模块142，还用于配置调整参数包括接收窗口的窗口长度和/或边界值。
处理模块142，还用于配置调整参数包括下一个待接收的PDCP实体的业务数据单元SDU的候选编号值。
处理模块142，还用于配置调整参数包括HFN值。
处理模块142，还用于配置调整参数包括PDCP实体接收到第一个PDCP数据包的包头中携带的编号值。
收发模块141，还用于：向终端设备发送广播消息或者广播多播业务MBS控制信道消息，其中，广播消息或者MBS控制信道消息用于携带指示信息。
收发模块141，还用于：向终端设备发送用于指示终端设备对接收窗口的变量进行调整的调整指示。
本申请提出的PDCP实体的接收窗口的配置装置，网络设备基于触发事件的发生生成调整指示并发送至终端设备，为终端设备配置PDCP实体的接收窗口的变量的调整参数并发送至终端设备，终端设备接收到调整指示后，基于获取到的调整参数中携带的候选配置值为接收窗口的变量进行调整，本申请中，实现了PDCP实体的接收窗口变量的及时更新，避免了PDCP实体的接收窗口由于无法进行变量更新所导致的对于新的终端设备加入的限制，使得新的终端设备可以随时加入进行MBS数据的接收，保证了MBS数据传输的持续性以及可靠性。
图15是本申请实施例提出的另一种通信装置1500的结构示意图。通信装置1500可以是网络设备，也可以是终端设备，也可以是支持网络设备实现上述方法的芯片、芯片系统、或处理器等，还可以是支持终端设备实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1500可以包括一个或多个处理器1501。处理器1501可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置1500中还可以包括一个或多个存储器1502，其上可以存有计算机程序1504，处 理器1501执行计算机程序1504，以使得通信装置1500执行上述方法实施例中描述的方法。可选的，存储器1502中还可以存储有数据。通信装置1500和存储器1502可以单独设置，也可以集成在一起。
可选的，通信装置1500还可以包括收发器1505、天线1506。收发器1505可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1505可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置1500中还可以包括一个或多个接口电路1507。接口电路1507用于接收代码指令并传输至处理器1501。处理器1501运行代码指令以使通信装置1500执行上述方法实施例中描述的方法。
通信装置1500为终端设备：收发器1505用于执行图2中的步骤S201、图4中的步骤S401、图5中的步骤S501等等；处理器1501用于执行图2中的步骤S202、图4中的步骤S402以及图5中的步骤S502等等。
通信装置1500为网络设备：收发器1505用于执行图10中的步骤S1002、图11中的步骤S1102等等；处理器1501用于执行图10中的步骤S1001、图11中的步骤S1101以及步骤S1103等等。
在一种实现方式中，处理器1501中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1501可以存有计算机程序1503，计算机程序1503在处理器1501上运行，可使得通信装置1500执行上述方法实施例中描述的方法。计算机程序1503可能固化在处理器1501中，该种情况下，处理器1501可能由硬件实现。
在一种实现方式中，通信装置1500可以包括电路，电路可以实现前述方法实施例中发送或接收或者通信的功能。本申请中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是网络设备或者终端设备(如前述方法实施例中的第一终端设备)，但本申请中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图16的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、 网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，可参见图16所示的芯片的结构示意图。图16所示的芯片包括处理器1601和接口1602。其中，处理器1601的数量可以是一个或多个，接口1602的数量可以是多个。
对于芯片用于实现本申请实施例中终端设备的功能的情况：
接口1602，用于执行图2中的步骤S201、图4中的步骤S401、图5中的步骤S501等等。
对于芯片用于实现本申请实施例中网络设备的功能的情况：
接口1602，用于执行图10中的步骤S1002、图11中的步骤S1102等等。
可选的，芯片还包括存储器1603，存储器1603用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本申请实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现的功能，但这种实现不应被理解为超出本申请实施例保护的范围。
本申请实施例还提出一种PDCP实体的接收窗口的配置系统，该系统包括前述图15实施例中作为终端设备(如前述方法实施例中的终端设备)的通信装置和作为网络设备的通信装置，或者，该系统包括前述图16实施例中作为终端设备(如前述方法实施例中的终端设备)的通信装置和作为网络设备的通信装置。
本申请还提出一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本申请还提出一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行计算机程序时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本申请中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围，也表示先后顺序。
本申请中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本申请不做限制。在本申请实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D” 等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本申请中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本申请并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本申请中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本申请中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (28)

  1. 一种PDCP实体的接收窗口的配置方法，其特征在于，所述方法由终端设备执行，所述方法包括：
    确定PDCP实体的接收窗口的变量对应的调整参数；
    基于所述调整参数，配置所述PDCP实体的接收窗口的变量。
  2. 根据权利要求1所述的方法，其特征在于，所述确定PDCP实体的接收窗口的变量调整参数，包括：
    接收网络设备发送的指示信息，所述指示信息携带所述调整参数。
  3. 根据权利要求1或2所述的方法，其特征在于，还包括：
    响应于所述调整参数包括所述接收窗口的窗口长度和/或边界值，根据所述窗口长度和/或边界值，配置所述接收窗口的变量。
  4. 根据权利要求3所述的方法，其特征在于，还包括：
    响应于所述边界值为所述接收窗口的候选下边界值，将所述接收窗口的下边界值配置为所述候选下边界值。
  5. 根据权利要求3所述的方法，其特征在于，还包括：
    响应于所述边界值为所述接收窗口的候选上边界值，根据所述窗口长度和所述候选上边界值，确定所述接收窗口的候选下边界值，并将所述接收窗口的下边界值配置为所述候选下边界值。
  6. 根据权利要求1或2所述的方法，其特征在于，还包括：
    响应于所述调整参数包括下一个待接收的PDCP实体的业务数据单元SDU的候选编号值，将所述接收窗口的下一个待接收的PDCP实体的SDU的编号值配置为所述候选编号值。
  7. 根据权利要求1或2所述的方法，其特征在于，还包括：
    响应于所述调整参数包括HFN值，确定所述PDCP实体接收到第一个PDCP数据包的包头中SN值；
    根据所述HFN值和所述SN值，配置所述接收窗口的变量。
  8. 根据权利要求7所述的方法，其特征在于，所述根据所述HFN值和所述SN值，配置所述接收窗口的变量，包括：
    根据所述HFN值，配置所述接收窗口的变量的HFN部分；
    根据所述SN值，配置所述接收窗口的变量的SN部分。
  9. 根据权利要求8所述的方法，其特征在于，所述根据所述HFN值，配置所述接收窗口的变量的HFN部分，包括：
    将所述接收窗口的下边界值和/或下一个待接收的PDCP SDU的编号值的HFN部分，配置为所述HFN值。
  10. 根据权利要求8所述的方法，其特征在于，所述根据所述SN值，配置所述接收窗口的变量的SN部分，包括：
    确定所述SN值与第一目标数值的第一和值；
    根据所述第一和值配置所述接收窗口的变量的SN部分。
  11. 根据权利要求8所述的方法，其特征在于，所述根据所述第一和值配置所述接收窗口的变量的 SN部分，包括：
    响应于所述第一和值所满足的目标条件，确定所述目标条件对应的候选配置值；
    将所述接收窗口的下边界值和/或下一个待接收的PDCP SDU的编号值的SN部分配置为所述候选配置值。
  12. 根据权利要求11所述的方法，其特征在于，所述响应于所述第一和值所满足的目标条件，确定所述目标条件对应的目标配置值，包括：
    响应于所述第一和值满足大于所述SN值的最大允许值的目标条件，将零值确定所述候选配置值；或者，
    响应于所述第一和值满足小于零值的目标条件，确定所述SN值的最大允许值、所述第一和值和第二目标数值的第二和值，将所述第二和值确定所述候选配置值；或者，
    响应于所述第一和值满足大于所述最大允许值的一半的目标条件，将所述第一和值确定所述候选配置值。
  13. 根据权利要求1或2所述的方法，其特征在于，还包括：
    确定所述PDCP实体接收到第一个PDCP数据包的包头中携带的编号值，作为所述调整参数；
    根据所述包头中携带的编号值，配置所述接收窗口的变量。
  14. 根据权利要求13所述的方法，其特征在于，所述根据所述包头中携带的编号值，配置所述接收窗口的变量，包括：
    将所述接收窗口的下边界值和/或下一个待接收的PDCP实体的SDU的编号值配置为所述包头中携带的编号值；或者，
    确定所述包头中携带的编号值与第三目标数值的第三和值，将所述接收窗口的下边界值和/或下一个待接收的PDCP实体的SDU的编号值配置为所述第三和值。
  15. 根据权利要求2所述的方法，其特征在于，所述接收网络设备发送的指示信息，包括：
    接收广播消息或者广播多播业务MBS控制信道消息，其中，所述广播消息或者MBS控制信道消息用于携带所述指示信息。
  16. 根据权利要求1所述的方法，其特征在于，所述确定PDCP实体的接收窗口的变量对应的调整参数之前，还包括：
    确定满足调整所述接收窗口的变量的触发事件；
    其中，所述触发事件为以下事件中的至少一种：
    接收网络设备发送的调整指示，所述调整指示用于指示所述终端设备对所述接收窗口的变量进行调整；或者，
    新建MBS无线承载MRB的PDCP实体；或者，
    重建或者重配置MRB的PDCP实体。
  17. 一种PDCP实体的接收窗口的配置方法，其特征在于，所述方法由网络设备执行，所述方法包括：
    配置PDCP实体的接收窗口的变量对应的调整参数；
    向终端设备发送指示信息，其中，所述指示信息用于指示所述终端设备基于调整参数，配置所述PDCP实体的接收窗口的变量，所述指示信息携带所述调整参数。
  18. 根据权利要求17所述的方法，其特征在于，所述调整参数包括所述接收窗口的窗口长度和/或边界值。
  19. 根据权利要求17所述的方法，其特征在于，所述调整参数包括下一个待接收的PDCP实体的业务数据单元SDU的候选编号值。
  20. 根据权利要求17所述的方法，其特征在于，所述调整参数包括HFN值。
  21. 根据权利要求17所述的方法，其特征在于，所述调整参数包括所述PDCP实体接收到第一个PDCP数据包的包头中携带的编号值。
  22. 根据权利要求17所述的方法，其特征在于，所述向终端设备发送指示信息，包括：
    向终端设备发送广播消息或者广播多播业务MBS控制信道消息，其中，所述广播消息或者MBS控制信道消息用于携带所述指示信息。
  23. 根据权利要求17所述的方法，其特征在于，所述向终端设备发送指示信息之前，还包括：
    向所述终端设备发送用于指示所述终端设备对所述接收窗口的变量进行调整的调整指示。
  24. 一种PDCP实体的接收窗口的配置装置，其特征在于，所述装置由终端设备执行，所述装置包括：
    收发模块，用于确定PDCP实体的接收窗口的变量对应的调整参数；
    处理模块，用于基于所述调整参数，配置所述PDCP实体的接收窗口的变量。
  25. 一种PDCP实体的接收窗口的配置装置，其特征在于，所述装置由网络设备执行，所述装置包括：
    处理模块，用于配置PDCP实体的接收窗口的变量对应的调整参数；
    收发模块，用于向终端设备发送指示信息，其中，所述指示信息用于指示所述终端设备基于调整参数，配置所述PDCP实体的接收窗口的变量，所述指示信息携带所述调整参数。
  26. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至16中任一项所述的方法；或，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求17至23所述的方法。
  27. 一种通信装置，其特征在于，包括：处理器和接口电路；
    所述接口电路，用于接收代码指令并传输至所述处理器；
    所述处理器，用于运行所述代码指令以执行如权利要求1至16中任一项所述的方法；或，所述处理器，用于运行所述代码指令以执行如权利要求17至23所述的方法。
  28. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求1至16中任一项所述的方法被实现；或，用于存储有指令，当所述指令被执行时，使如权利要求17至23所述的方法被实现。
PCT/CN2021/084700 2021-03-31 2021-03-31 一种pdcp实体的接收窗口的配置方法及其装置 WO2022205191A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN202180000755.XA CN115552930B (zh) 2021-03-31 2021-03-31 一种pdcp实体的接收窗口的配置方法及其装置
PCT/CN2021/084700 WO2022205191A1 (zh) 2021-03-31 2021-03-31 一种pdcp实体的接收窗口的配置方法及其装置
US18/552,569 US20240179729A1 (en) 2021-03-31 2021-03-31 Method and device for configuring receive window of pdcp entity
EP21933855.5A EP4319211A4 (en) 2021-03-31 2021-03-31 METHOD FOR CONFIGURING THE RECEIVE WINDOW OF A PDCP UNIT AND DEVICE THEREFOR

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/084700 WO2022205191A1 (zh) 2021-03-31 2021-03-31 一种pdcp实体的接收窗口的配置方法及其装置

Publications (1)

Publication Number Publication Date
WO2022205191A1 true WO2022205191A1 (zh) 2022-10-06

Family

ID=83455446

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/084700 WO2022205191A1 (zh) 2021-03-31 2021-03-31 一种pdcp实体的接收窗口的配置方法及其装置

Country Status (4)

Country Link
US (1) US20240179729A1 (zh)
EP (1) EP4319211A4 (zh)
CN (1) CN115552930B (zh)
WO (1) WO2022205191A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140105096A1 (en) * 2011-06-09 2014-04-17 Haifeng Wang Method and Apparatus for Facilitating Multicast Service
CN108347308A (zh) * 2017-01-22 2018-07-31 成都鼎桥通信技术有限公司 点对多点业务的接收方法和装置
CN111818630A (zh) * 2019-07-12 2020-10-23 维沃移动通信有限公司 状态变量维护方法、装置及用户设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TW200803371A (en) * 2006-05-05 2008-01-01 Interdigital Tech Corp Ciphering control and synchronization in a wireless communication system
JP6516402B2 (ja) * 2013-10-31 2019-05-22 株式会社Ｎｔｔドコモ ユーザ装置、及びレイヤ２状態制御方法
CN112399468B (zh) * 2019-08-14 2022-02-15 大唐移动通信设备有限公司 一种数据传输方法及接收设备
CN111510278B (zh) * 2020-04-26 2023-01-13 Oppo广东移动通信有限公司 一种超帧号hfn同步方法及终端、存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140105096A1 (en) * 2011-06-09 2014-04-17 Haifeng Wang Method and Apparatus for Facilitating Multicast Service
CN108347308A (zh) * 2017-01-22 2018-07-31 成都鼎桥通信技术有限公司 点对多点业务的接收方法和装置
CN111818630A (zh) * 2019-07-12 2020-10-23 维沃移动通信有限公司 状态变量维护方法、装置及用户设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INC; FIRSTNET; UIC; BT PLC; KYOCERA; BBC; AT&T: "NR Multicast PTM bearer RLC AM mode operation", 3GPP DRAFT; R2-2100319, vol. RAN WG2, 15 January 2021 (2021-01-15), pages 1 - 9, XP051973511 *
See also references of EP4319211A4 *

Also Published As

Publication number Publication date
EP4319211A4 (en) 2024-04-24
US20240179729A1 (en) 2024-05-30
CN115552930B (zh) 2024-09-10
CN115552930A (zh) 2022-12-30
EP4319211A1 (en) 2024-02-07

Similar Documents

Publication Publication Date Title
WO2021143868A1 (en) Methods and apparatus of lossless handover for nr multicast services
US11259362B2 (en) Method for repeatedly transmitting data and device
KR20220042176A (ko) 통신 방식, slrb 구축 방식 및 통신 장치
WO2021056152A1 (zh) 一种信息配置方法及装置、终端设备、网络设备
JP7549077B2 (ja) 通信制御方法、ユーザ装置及びプロセッサ
WO2021062809A1 (zh) 一种时刻信息的通知方法和装置
WO2022205191A1 (zh) 一种pdcp实体的接收窗口的配置方法及其装置
US20230319942A1 (en) Communication method and apparatus
US20220338288A1 (en) Communication method and apparatus
WO2024092523A1 (zh) 侧行链路定位消息的发送方法、接收方法及其装置
WO2022217448A1 (zh) 一种上行控制信息的复用方法及其装置
WO2022205005A1 (zh) 一种数据接收的处理方法及其装置
WO2022120541A1 (zh) 数据传输的方法和装置
WO2022205230A1 (zh) 一种分组数据汇聚协议实体的超帧号确定方法及其装置
WO2023130321A1 (zh) 一种数据压缩方法和装置
WO2023060402A1 (en) Method and apparatus for multicast and broadcast services
TWI846088B (zh) 為多播設置初始ｐｄｃｐ狀態變數的方法和使用者設備
WO2023220941A1 (zh) 一种数据前转信息的传输方法及其装置
WO2023023958A1 (zh) 一种寻呼消息的传输方法及装置、设备
WO2024027560A1 (zh) 无线承载的处理方法及装置
WO2024159543A1 (zh) 一种传输实体的控制方法及其装置
WO2024065550A1 (zh) 一种丢包处理方法及装置
WO2023246404A1 (zh) 一种通信方法及装置
WO2024016244A1 (zh) 支持非激活态组播业务接收的配置方法及装置
WO2023122988A1 (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: 21933855

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18552569

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 202347072678

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2021933855

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021933855

Country of ref document: EP

Effective date: 20231031

NENP Non-entry into the national phase

Ref country code: DE