CN115669067A

CN115669067A - Wireless communication method and apparatus

Info

Publication number: CN115669067A
Application number: CN202080101266.9A
Authority: CN
Inventors: 卢前溪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-08-07
Filing date: 2020-08-07
Publication date: 2023-01-31
Also published as: WO2022027682A1

Abstract

A wireless communication method and apparatus are provided, the method comprising: and receiving indication information, wherein the indication information is used for indicating the terminal equipment to switch the multicast bearer. The indication information indicates the terminal equipment to switch the multicast bearer, which is equivalent to switching unicast and multicast on an access layer, thereby not only reducing the switching time delay, but also realizing lossless switching.

Description

Wireless communication method and apparatus

Technical Field

The embodiments of the present application relate to the field of communications, and more particularly, to a wireless communication method and apparatus.

Background

Currently, switching between unicast and multicast in Long Term Evolution (LTE) is implemented by an application layer server/core network element above an access layer.

However, the switching delay is large due to more network elements of the core network; in addition, the unicast or multicast switching is realized through the application layer server/core network element, which means that the unicast and multicast switching needs to be realized at a high layer, and the lossless switching is difficult to realize.

Disclosure of Invention

A wireless communication method and device are provided, which can not only reduce the switching delay but also realize lossless switching by switching between unicast and multicast on an access layer.

In a first aspect, a wireless communication method is provided, including:

and receiving indication information, wherein the indication information is used for indicating the terminal equipment to switch the multicast bearer.

In a second aspect, a wireless communication method is provided, including:

and sending indication information, wherein the indication information is used for indicating the terminal equipment to switch the multicast bearer.

In a third aspect, a terminal device is provided, configured to perform the method in the first aspect or each implementation manner thereof. Specifically, the terminal device includes a functional module configured to execute the method in the first aspect or each implementation manner thereof.

In a fourth aspect, a network device is provided for performing the method of the second aspect or its implementations. In particular, the network device comprises functional modules for performing the methods of the second aspect or its implementations.

In a fifth aspect, a terminal device is provided that includes a processor and a memory. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory to perform the method in the first aspect or each implementation manner thereof.

In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the method of the second aspect or each implementation manner thereof.

In a seventh aspect, a chip is provided, which is configured to implement the method in any one of the first aspect to the second aspect or each implementation manner thereof. Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that a device in which the chip is installed performs the method in any one of the first aspect to the second aspect or the implementation manners thereof.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, the computer program causing a computer to perform the method of any one of the first to second aspects or implementations thereof.

In a ninth aspect, there is provided a computer program product comprising computer program instructions to cause a computer to perform the method of any one of the first to second aspects or implementations thereof.

A tenth aspect provides a computer program which, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.

Based on the technical scheme, the indication information indicates the terminal equipment to switch the multicast bearer, which is equivalent to switching unicast and multicast on an access layer, so that not only can the switching time delay be reduced, but also lossless switching can be realized.

Drawings

Fig. 1 is an example of an application scenario of the present application.

Fig. 2 is a schematic diagram of a mapping relationship between a logical channel and a transport channel according to an embodiment of the present application.

Fig. 3 is a schematic diagram of a configuration transmission mechanism provided in an embodiment of the present application.

Fig. 4 to 6 are schematic block diagrams of BWP of the terminal device according to the embodiment of the present application.

Fig. 7 is a schematic flow chart of a wireless communication method provided by an embodiment of the present application.

Fig. 8 is another schematic flowchart of a wireless communication method provided in an embodiment of the present application.

Fig. 9 is a schematic block diagram of a terminal device provided in an embodiment of the present application.

Fig. 10 is a schematic block diagram of a network device according to an embodiment of the present application.

Fig. 11 is a schematic block diagram of a communication device provided in an embodiment of the present application.

Fig. 12 is a schematic block diagram of a chip provided in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present application.

As shown in fig. 1, the SC-PTM architecture 100 may include: a terminal device, an access network device, a Multi-cell/Multicast Coordination Entity (MCE), a Mobility Management network element (MME), a Home Subscriber Server (HSS), a Policy and Charging Rules Function (PCRF), a Serving/public data Gateway (Serving/PDN Gateway, S/P-GW), a Group Communication Application Server (GCS AS), a Broadcast Multicast Service Center (Broadcast Multicast Service Center, BM-SC), a Multimedia Broadcast Multicast Service Gateway (MBMS-GW).

Wherein, each node or network element in the SC-PTM architecture 100 may communicate with each other. For example, various nodes or network elements in the SC-PTM100 may communicate via various types of interfaces.

For example, the terminal device may communicate with an access network device over a Uu interface; the access network equipment can communicate with MCE through an M2 interface, can also communicate with the MME through an S1-MME interface, can also communicate with the MBMS-GW through an M1 interface, and can also communicate with the S/P-GW through an S1-U interface; the MCE may communicate with an MME over an M3 interface; the MME can communicate with the HSS through an S6a interface, can also communicate with the S/P-GW through an S-11 interface, and can also communicate with the MBMS-GW through an Sm interface; the S/P-GW can also communicate with GCS AS through an SGi interface and can also communicate with PCRF through a Gx interface; the PCRF can communicate with the GCS AS through an Rx interface; the GCS AS can also communicate with the BM-SC through an MB2-C interface and an MB2-U interface; and the BM-SC communicates with the MBMS-GW through an SGimb interface and an SGmb.

It will be appreciated that the interfaces referred to above may be interfaces defined or specified in a communications standard for enabling the transmission of data or signalling between the various nodes or network elements.

It should be noted that, the present application does not limit the specific implementation form of each node or network element.

For example, the Access Network device may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (Long Term Evolution, LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a Radio controller in a Cloud Radio Access Network (CRAN), or the Network device 120 may be a relay station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a Network device in a future evolved Public Land Mobile Network (PLMN), or the like.

As another example, the terminal device may be any terminal device including, but not limited to, a terminal device that is in wired or wireless connection with the network device 120 or other terminal devices. For example, the terminal device may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolution network, etc. As another example, the terminal Device may be used for Device-to-Device (D2D) communication.

As an example, the frame 100 may be a Single Cell Point To multipoint (SC-PTM).

For example, SC-PTM may be based on MBMS network architecture. Multimedia Broadcast Multicast Service (MBMS) is a Service introduced in 3gpp Release 6. The multimedia broadcast multicast service is a technology for transmitting data from one data source to a plurality of user equipments by sharing network resources, and can provide multimedia services while efficiently utilizing the network resources to implement broadcasting and multicasting of the multimedia services at a higher rate (256 kbps). Because the MBMS spectrum efficiency in the 3GPP R6 is low, it is not enough to effectively carry and support the operation of the mobile tv type service. Therefore, in the Long Term Evolution (LTE) project of the radio access network, the 3GPP proposes to enhance the support capability of the downlink high-speed multimedia broadcast multicast service, and determines the design requirements for the physical layer and the air interface. eMBMS is introduced to LTE networks by R9. E-MBMS proposes a Single Frequency Network (SFN) concept, that is, a uniform Frequency is used to transmit data in all cells simultaneously, but synchronization between cells is guaranteed. The method can greatly improve the distribution of the integral signal-to-noise ratio of the cell, and the frequency spectrum efficiency can be correspondingly and greatly improved. And realizes broadcasting and multicasting of services based on an IP (Internet Protocol) multicast Protocol. Optionally, the MCE determines whether to adopt an SC-PTM transmission mode or a Multimedia Broadcast multicast service Single Frequency Network (MBSFN) transmission mode

Fig. 2 is a schematic diagram of logical channels and physical channels provided in an embodiment of the present application.

As shown in fig. 2, the downlink logical Channel may include a Single Cell Multicast Control Channel (SC-MCCH) and a Single Cell Multicast traffic Channel (SC-MTCH). For example, a Logical Channel Identity (LCID) of the SC-MCCH may be 11001), an LCID of the SC-MTCH may be 11001, and both the SC-MCCH and the SC-MTCH may be mapped onto a Downlink Shared Channel (DL-SCH), e.g., a Physical Downlink Shared Channel (PDSCH). Optionally, the SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat Request (HARQ) operation, and use Radio Link Control (RLC) in Unacknowledged Mode (UM).

In addition, as shown in fig. 2, the downlink logical channel may further include: at least one of a Multicast Control Channel (MCCH), a Multicast Traffic Channel (MTCH), a Paging Control Channel (PCCH), a Common Control Channel (CCCH), a Dedicated Control Channel (DCCH), a Broadcast Control Channel (BCCH), and a Dedicated Traffic Channel (DTCH). In addition, the downlink transmission channel may further include: at least one of a Broadcast Channel (BCH), a Paging Channel (PCH), and a Multicast Channel (MCH).

In addition, configuration Information of the SC-MCCH may be carried in a System Information Block (SIB). For example, SIB20 may include configuration information for SC-MCCH. Optionally, there is only one SC-MCCH for a cell. The configuration information may include: the modification period and the repetition period of the SC-MCCH, and the configuration information of a radio frame and a subframe. Optionally, the modification period of the SC-MCCH may indicate a change notification through one bit of 8 bits in DCI 1C. Optionally, the boundary of the modification period may be defined as SFN mod m =0, where m is a modification period (sc-mcch-ModificationPeriod) configured in SIB 20.

Fig. 3 is a schematic diagram of a configuration transmission mechanism (configuration transmission mechanism) according to an embodiment of the present application.

As shown in fig. 3, SIB20 may configure (Config) the SC-MCCH PDCCH, and may also configure the notification PDCCH. Optionally, the SC-MCCH PDCCH may be scrambled by a Single Cell radio network temporary identifier (Single Cell RNTI, SC-RNTI), and/or the Notification PDCCH may be scrambled by a Single Cell Notification radio network temporary identifier (Single Cell Notification RNTI, SC-N-RNTI). Downlink Control Information (DCI) in the SC-MCCH PDCCH may be used to schedule the SC-MCCH PDSCH. The SC-MCCH PDSCH may be configured (Config) with SC-MTCH 1-SC-MTCH M, wherein the SC-MTCH 1-SC-MTCH M may include SC-MTCH 1 PDCCH-SC-MTCH M PDCCH, and DCI in the SC-MTCH 1 PDCCH-SC-MTCH M PDCCH may be used to schedule SC-MTCH 1 PDSCH-SC-MTCH M PDSCH. Optionally, the PDCCH to SC-MTCH M PDCCH may be scrambled by Group radio network temporary identifiers (Group RNTI, G-RNTI) G-RNTI 1 to-RNTI M, respectively. Optionally, the SC-MTCH 1PDSCH to SC-MTCH M PDSCH may respectively carry Temporary Mobile Group Identities (TMGIs) 1 to TMGI M.

In addition, downlink Discontinuous Reception (DRX) for SC-PTM may be controlled by a plurality of parameters. For example, the plurality of parameters include, but are not limited to: an active period timer (ondurationtimerscmp) of the SC-PTM, a deactivation DRX timer (DRX-inactivitytimerscmp) of the SC-PTM, a deactivation DRX timer of the SC-MTCH, an SC-MTCH scheduling cycle (SC-MTCH-scheduling cycle), and an SC-MTCH scheduling offset (SC-MTCH-scheduling offset).

For example, DRX for SC-PTM may be controlled as follows:

a) Starts a timer onDurationTimerSCPTM when [ (SFN x 10) + subframe number ] mod (SC-MTCH-scheduling cycle) = SC-MTCH-scheduling offset is satisfied.

b) When receiving downlink PDCCH dispatching, starting a timer drx-InactivityTimerSCPTM;

c) Receive the downstream SC-PTM service only when the timer ondurationTimerSCPTM or drx-InactivetyTimeSCPTM is operated.

In addition, the scheme provided by the application can also carry out communication based on Bandwidth Part (BWP). For example, a terminal device in an idle (idle) state or an inactive (inactive) state may reside on an initial (inactive) BWP, which may be visible to the terminal device in the idle state or the inactive state, and may acquire information such as MIB, RMSI, OSI, and paging on the initial BWP.

The BWP is briefly explained as follows:

in 5G, the maximum channel bandwidth may be 400MHZ (wideband carrier), which is large compared to LTE maximum 20M bandwidth. If the UE remains operating on the wideband carrier, power consumption of the UE is increased. The power consumption of the UE may be optimized by a BandWidth component (BWP). I.e. the RF bandwidth of the UE can be adjusted according to the actual throughput of the UE. Another purpose of BWP is to trigger coexistence of multiple sets of air interface parameters (Numerology) in a cell.

For example, as shown in fig. 4, if the rate of the UE is low, the UE may be configured with a partial bandwidth of the carrier bandwidth, for example, BWP1. As another example, as shown in fig. 5, if the UE has a high requirement for the rate, the UE may be configured with a slightly larger BWP. E.g., BWP2, which is larger than BWP1. As another example, as shown in fig. 6, if the UE supports high rate or operates in CA mode, a plurality of BWPs, e.g., BWP1 and BWP2, may be configured. Optionally, BWP1 and BWP2 may respectively correspond to an air interface parameter set 1 and an air interface parameter set 2.

Up to 4 UL BWPs and up to 4 DL BWPs can be configured for one UE through RRC dedicated signaling, but only one DL BWP and UL BWP can be activated at the same time. In RRC dedicated signaling, the first active BWP of the configured BWPs may be indicated. Meanwhile, in the process that the UE is in a connected state, the UE can also switch between different BWPs through DCI. When the carrier in the inactive state enters the active state, the first active BWP is the first active BWP configured in the RRC. The configuration parameters of each BWP include at least one of:

subcarrier spacing (subarrierspating);

cyclic prefix (cyclic prefix);

the first PRB and the number of consecutive PRBs (locationAndBandwidth) of BWP.

BWP identification (BWP-Id); and

BWP Common configuration parameters (BWP Common) and Dedicated configuration parameters (BWP Dedicated).

Illustratively, the BWP id may take values from 0 to 4 in RRC signaling, with 0 defaulting to the initial BWP.

In the DCI, the BWP indicator is 2bit. If the number of the configured BWPs is less than or equal to 3, the BWP indicator can be 1,2 or 3, and

BWP indicators

1,2 and 3 respectively correspond to

BWP ids

1,2 and 3. If the number of BWPs is 4, the BWP indicators may be 0,1,2 and 3, and optionally,

BWP indicators

0,1,2 and 3 correspond to BWPs configured according to the sequential index, respectively. Alternatively, a continuous BWP id is used when configuring BWP.

Fig. 7 shows a schematic flow diagram of a wireless communication method 200 according to an embodiment of the application, which method 200 may be performed interactively by a terminal device and a network device. The terminal device shown in fig. 2 may be a terminal device as shown in fig. 1, and the network device shown in fig. 2 may be an access network device as shown in fig. 1.

As shown in fig. 7, the method 200 may include:

s210, the terminal device receives indication information sent by the network device, wherein the indication information is used for indicating the terminal device to switch multicast bearing.

For example, the network device sends the indication information to the terminal device, and the terminal device triggers the terminal device to switch the multicast bearer after receiving the indication information. For example, the indication information sent by the source access network device is received. For another example, the indication information sent by the target access network device is received by the source access network device.

The indication information indicates the terminal equipment to switch the multicast bearer, which is equivalent to switching unicast and multicast on an access layer, thereby not only reducing the switching time delay, but also realizing lossless switching.

In some embodiments of the present application, the method 200 may further comprise:

determining a processing action of a Packet Data Convergence Protocol (PDCP) layer for the terminal device based on the indication information.

In other words, the indication information may also be used to determine a processing action of the terminal device for the PDCP layer. Or, the indication information is used to trigger the terminal device to perform a processing action for a packet data convergence protocol PDCP layer of the terminal device.

It should be understood that the processing action for the PDCP layer in this application can be understood as processing of the related functions of the PDCP layer.

Illustratively, the functions of the PDCP layer or PDCP entity include, but are not limited to:

header compression and decompression functions, such as ROHC; a user data transmission function for realizing the transmission of user data; an in-order delivery function for in-order delivery of upper layer PDUs; a sequence reordering function for reordering the received PDCP PDUs; a duplicate detection function for duplicate detecting lower layer SDUs; a retransmission function, namely retransmission PDCP SDU; encryption and decryption functions; timer-based SDU deletion function, i.e. timer-based SDU discard in uplink.

For example, the reordering function of the NR PDCP entity refers to a function of sequentially reordering PDCP PDUs received from a lower layer based on a PDCP Sequence Number (SN), may include a function of delivering data to a higher layer in a reordered sequence, may include a function of recording lost PDCP PDUs by reordering the sequence, may include a function of making a status report on the lost PDCP PDUs to a transmitting side, and may include a function of requesting retransmission of the lost PDCP PDUs.

In some embodiments of the application, the processing action for the PDCP layer of the terminal device comprises at least one of:

triggering a PDCP release and/or establishment procedure;

triggering a PDCP rebuilding process;

resetting/reinitializing PDCP variables;

maintaining a PDCP variable;

submitting the data in the cache to an upper layer; and

triggering PDCP release and/or establishment procedures.

Illustratively, the PDCP re-establishment may refer to an operation performed in a PDCP of the terminal device. The PDCP re-establishment may also be referred to as PDCP entity re-establishment. The PDCP re-establishment may include a re-establishment of a receiving entity and/or a re-establishment of a transmitting entity. The re-establishment of the receiving entity may also be referred to as a re-establishment of the downlink and the transmitting entity may also be referred to as a re-establishment of the uplink. The re-establishing of the sending entity may comprise re-establishing a function associated with the sending entity. For example, the re-establishment of the sending entity may include resetting header compression and decompression functions and/or re-acquiring encryption algorithms and keys, etc. The re-establishing of the receiving entity may comprise re-establishing a function associated with the receiving entity. For example, the re-establishment of the receiving entity may include resetting header compression and/or stopping and resetting sequence reordering functions, etc.

Illustratively, the PDCP variable may include a transmit (Tx) PDCP status variable and a receive (Rx) PDCP status variable.

For example, the Tx PDCP status variable may include at least one of NEXT PDCP Tx SN, tx HFN, and Tx NEXT. The NEXT PDCP TX SN, which may be used to indicate a PDCP Sequence Number (SN) of a PDCP SDU to be subsequently transmitted at the PDCP entity, may be set to 0 at the PDCP entity setup. The TX HFN may be used to indicate a Hyper Frame Number (HFN) value generated from a COUNT (COUNT) value for PDCP PDUs in the PDCP entity, and may be set to 0 at PDCP entity setup. The TX NEXT may be used to indicate a COUNT value of a PDCP SDU to be subsequently transmitted in the PDCP entity, and may be set to 0 at PDCP entity setup.

As another example, the rxptdcp status variable may include at least one of Next PDCP RX SN, RX HFN, last terminated PDCP RX SN, RX Next, and RX DELIV. The Next PDCP RX SN may be used to indicate a PDCP SN of a PDCP SDU expected to be subsequently received in the PDCP entity, which may be set to 0 at PDCP entity setup. The RX HFN may be used to indicate an HFN value generated from a COUNT value for PDCP PDUs received in the PDCP entity, and may be set to 0 at the PDCP entity setup. The Last subordinated PDCP RX SN, which is applied only to the PDCP entities mapped to the DRB, may be used to indicate a sequence number indicating the Last PDCP SDU delivered to a higher layer, and may be set to a maximum PDCP SN value at the PDCP setup time. The RX NEXT may refer to a COUNT value of PDCP SDUs expected to be received subsequently, and the initial value may be set to 0. The RX DELIV may be used to indicate a COUNT value of the last PDCP SDU delivered to a higher layer.

In some embodiments of the present application, the resetting/reinitializing the PDCP variable includes resetting/reinitializing the PDCP variable based on a sequence number of a first data packet transmitted by the target access network device.

In some embodiments of the present application, the data in the buffer is a PDCP service data unit SDU.

In some embodiments of the present application, the indication information is further used to indicate the first processing action or the second processing action; the S210 may include: determining the first processing action indicated by the indication information or the second processing action indicated by the indication information as a processing action aiming at a Packet Data Convergence Protocol (PDCP) layer of the terminal equipment.

For example, after receiving the indication information, the terminal device determines the first processing action or the second processing action indicated by the indication information as a processing action of the terminal device for a PDCP layer.

In some embodiments of the present application, the first processing action is at least one of: triggering PDCP release and/or establishment procedures, resetting/reinitializing PDCP variables, and delivering buffered data to upper layers. For example, the first handling action is to trigger a PDCP release and/or establishment procedure; or, the first handling action is to reset/reinitialize PDCP variables; or, the first processing action is to submit the data in the cache to the upper layer.

In some embodiments of the present application, the second processing action is at least one of: and triggering a PDCP rebuilding process, keeping a PDCP variable and not submitting data in the buffer to an upper layer. For example, the second handling action is to trigger a PDCP re-establishment procedure; or, the second handling action is used as a keep PDCP variable; or the second processing action is not to submit the data in the cache to the upper layer. For example, the second processing action is not to submit data in the cache to the upper layer, and the data in the cache is used for performing combined sorting with the data received after the multicast bearer is switched.

In some embodiments of the present application, the first processing action is different from the second processing action.

In some embodiments of the present application, a scenario corresponding to the first processing action is a scenario that does not need to avoid packet loss or lossy switching. In some embodiments of the present application, a scenario corresponding to the second processing action is a scenario in which packet loss needs to be avoided or a scenario of lossless handover needs to be avoided.

For example, if the first processing action is to trigger a PDCP release and/or establishment procedure, the procedure is simple, but packet loss may be caused; if the first processing action is to reset/reinitialize the PDCP variable, it means that after the terminal device switches the multicast bearer, the variable is reset/initialized only according to the sending condition of the target network device, which is equivalent to mutually independent packet sending processes of the source network device and the target network device, and therefore packet loss may be caused; if the first processing action is to submit the data in the cache to the upper layer, it indicates that the terminal device may submit all the data received before switching the multicast bearer to the upper layer, which is equivalent to that packet sending processes of the source network device and the target network device are independent of each other, and thus packet loss may be caused.

For another example, if the second processing action is used for triggering the PDCP reestablishment process, packet loss can be avoided; if the second processing action is used for keeping the PDCP variable, it means that the terminal device needs to keep the relevant variables of the PDCP after switching the multicast bearer, which is equivalent to mutually synchronizing the packet sending processes of the source network device and the target network device, so that packet loss can be avoided; if the second processing action is not to submit the data in the cache to the upper layer, it indicates that the terminal device may use the data received before the multicast bearer is switched for performing the combined ordering with the data received after the multicast bearer is switched, which is equivalent to that the packet sending processes of the source network device and the target network device are mutually synchronized, so that the packet loss can be avoided.

Fig. 8 is a schematic flow chart of a wireless communication method 300 provided by an embodiment of the present application.

As shown in fig. 8, the method 300 may include:

and S310, triggering switching.

For example, the source network device triggers the terminal device to start the process of switching the multicast bearer.

And S320, the source network equipment sends indication information to the terminal equipment, and the indication information is used for indicating the terminal equipment to switch the multicast bearer. Of course, the target network device may also send the indication information through the source network device.

S330, the terminal equipment executes a processing action aiming at the PDCP layer of the terminal equipment.

For example, the terminal device determines and executes a processing action for a PDCP layer of the terminal device based on the indication information.

And S340, finishing the switching.

For example, the terminal device sends a handover complete message to the network device.

It should be understood that the steps in the method 300 can refer to the related steps in the method 200, and are not repeated here to avoid repetition.

The preferred embodiments of the present application have been described in detail with reference to the accompanying drawings, however, the present application is not limited to the details of the above embodiments, and various simple modifications may be made to the technical solution of the present application within the technical idea of the present application, and these simple modifications all belong to the protection scope of the present application. For example, the various features described in the foregoing detailed description may be combined in any suitable manner without contradiction, and in order to avoid unnecessary repetition, various combinations that may be made are not described separately in this application. For example, various embodiments of the present application may be arbitrarily combined with each other, and the same should be considered as the disclosure of the present application as long as the concept of the present application is not violated.

It should also be understood that, in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply an execution sequence, and the execution sequence of the processes should be determined by their functions and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. In addition, in the embodiment of the present application, the terms "downlink" and "uplink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate that the transmission direction of signals or data is a first direction transmitted from a station to a user equipment of a cell, and "uplink" is used to indicate that the transmission direction of signals or data is a second direction transmitted from the user equipment of the cell to the station, for example, "downlink signal" indicates that the transmission direction of signals is the first direction. In addition, in the embodiment of the present application, the term "and/or" is only one kind of association relation describing an associated object, and means that three kinds of relations may exist. Specifically, a and/or B may represent: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

Method embodiments of the present application are described in detail above in conjunction with fig. 1-8, and apparatus embodiments of the present application are described in detail below in conjunction with fig. 9-12.

Fig. 9 is a schematic block diagram of a terminal device 400 according to an embodiment of the present application.

As shown in fig. 9, the terminal device 400 may include:

a communication unit 410, configured to receive indication information, where the indication information is used to instruct a terminal device to switch a multicast bearer.

In some embodiments of the present application, the communication unit 410 is further configured to:

triggering a PDCP release and/or establishment process;

triggering a PDCP rebuilding process;

resetting/reinitializing PDCP variables;

keeping a PDCP variable;

submitting the data in the cache to an upper layer; and

triggering PDCP release and/or establishment procedures.

In some embodiments of the present application, the data in the buffer is PDCP service data unit SDU.

In some embodiments of the present application, the indication information is further used to indicate the first processing action or the second processing action; the communication unit 410 is specifically configured to:

determining the first processing action indicated by the indication information or the second processing action indicated by the indication information as a processing action aiming at a Packet Data Convergence Protocol (PDCP) layer of the terminal equipment.

In some embodiments of the present application, the first processing action is at least one of: triggering PDCP release and/or establishment procedures, resetting/reinitializing PDCP variables, and delivering buffered data to upper layers.

In some embodiments of the present application, the second processing action is at least one of: and triggering a PDCP reconstruction process, keeping a PDCP variable, and not submitting the data in the buffer to an upper layer.

In some embodiments of the present application, the second processing action is to not submit data in a cache to an upper layer, where the data in the cache is used for performing combined ordering with data received after the multicast bearer is switched.

In some embodiments of the present application, a scenario corresponding to the first processing action is a scenario that does not need to avoid packet loss or a scenario of lossy handover.

In some embodiments of the present application, a scenario corresponding to the second processing action is a scenario in which packet loss needs to be avoided or a scenario of lossless handover needs to be avoided.

In some embodiments of the present application, the communication unit 410 is specifically configured to:

receiving the indication information sent by the source access network equipment, or

And receiving the indication information sent by the target access network equipment through the source access network equipment.

It is to be understood that apparatus embodiments and method embodiments may correspond to one another and that similar descriptions may refer to method embodiments. Specifically, the terminal device 400 shown in fig. 9 may correspond to a corresponding main body in executing the

method

200 or 300 according to the embodiment of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 400 are respectively for implementing corresponding flows in each method, and are not described herein again for brevity.

Fig. 10 is a schematic block diagram of a network device 500 of an embodiment of the present application.

As shown in fig. 10, the network device 500 may include:

a communication unit 510, configured to send indication information, where the indication information is used to instruct a terminal device to switch a multicast bearer.

In some embodiments of the present application, the indication information is used to trigger the terminal device to perform a processing action for a packet data convergence protocol, PDCP, layer of the terminal device.

In some embodiments of the present application, the processing action for the PDCP layer of the terminal device comprises at least one of:

triggering a PDCP release and/or establishment procedure;

triggering a PDCP rebuilding process;

resetting/reinitializing PDCP variables;

keeping a PDCP variable;

submitting the data in the cache to an upper layer; and

triggering PDCP release and/or establishment procedures.

In some embodiments of the present application, the indication information is further used to indicate a first processing action or a second processing action, and the first processing action indicated by the indication information or the second processing action indicated by the indication information is a processing action for a packet data convergence protocol, PDCP, layer of the terminal device.

In some embodiments of the present application, the first processing action is at least one of: triggering PDCP release and/or setup procedures, resetting/re-initializing PDCP variables, and delivering data in the buffer to the upper layer.

In some embodiments of the present application, the second processing action is not to submit data in a buffer to an upper layer, where the data in the buffer is used for performing combined ordering with data received after the multicast bearer is switched.

In some embodiments of the present application, a scenario corresponding to the first processing action is a scenario that does not need to avoid packet loss or lossy switching.

In some embodiments of the present application, the network device is a target network device, and the communication unit 510 is specifically configured to:

and receiving the indication information sent by the source network equipment through the source network equipment.

In some embodiments of the present application, the network device is a source network device, and the communication unit 510 is specifically configured to:

and receiving the indication information sent by the source network equipment.

It is to be understood that apparatus embodiments and method embodiments may correspond to one another and that similar descriptions may refer to method embodiments. Specifically, the network device 500 shown in fig. 9 may correspond to a corresponding main body that executes the

method

200 or 300 in the embodiment of the present application, and the foregoing and other operations and/or functions of each unit in the network device 500 are not described herein again for brevity in order to implement a corresponding flow in each method.

The communication device of the embodiments of the present application is described above from the perspective of functional modules in conjunction with the drawings. It should be understood that the functional modules may be implemented by hardware, by instructions in software, or by a combination of hardware and software modules.

Specifically, the steps of the method embodiments in the present application may be implemented by integrated logic circuits of hardware in a processor and/or instructions in the form of software, and the steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor.

Alternatively, the software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, registers, or other storage medium known in the art. The storage medium is located in a memory, and a processor reads information in the memory and combines hardware thereof to complete steps of the above method embodiments.

For example, the processing unit and the communication unit referred to above may be implemented by a processor and a transceiver, respectively.

Fig. 11 is a schematic configuration diagram of a communication device 600 according to an embodiment of the present application.

As shown in fig. 11, the communication device 600 may include a processor 610.

From which processor 610 may invoke and execute a computer program to implement the methods of the embodiments of the present application.

With continued reference to fig. 11, the communication device 600 may also include a memory 620.

The memory 620 may be used for storing indication information, and may also be used for storing codes, instructions, etc. executed by the processor 610. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present application. The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

With continued reference to fig. 11, the communication device 600 may also include a transceiver 630.

The processor 610 may control the transceiver 630 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices. The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

It should be understood that the various components in the communication device 600 are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

It should also be understood that the communication device 600 may be a terminal device in the embodiment of the present application, and the communication device 600 may implement a corresponding process implemented by the terminal device in each method in the embodiment of the present application, that is, the communication device 600 in the embodiment of the present application may correspond to the terminal device 400 in the embodiment of the present application, and may correspond to a corresponding main body in executing the method 200 in the embodiment of the present application, and for brevity, no further description is provided here. Similarly, the communication device 600 may be a network device according to the embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in the methods according to the embodiments of the present application. That is to say, the communication device 600 in the embodiment of the present application may correspond to the network device 500 in the embodiment of the present application, and may correspond to a corresponding main body in executing the method 200 according to the embodiment of the present application, and for brevity, no detailed description is given here.

In addition, the embodiment of the application also provides a chip.

For example, the chip may be an integrated circuit chip having signal processing capabilities and capable of implementing or performing the methods, steps, and logic blocks disclosed in the embodiments of the present application. The chip may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc. Alternatively, the chip may be applied to various communication devices, so that the communication device mounted with the chip can execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.

Fig. 12 is a schematic block diagram of a chip 700 according to an embodiment of the present application.

As shown in fig. 12, the chip 700 includes a processor 710.

From which processor 710 may retrieve and execute a computer program to implement the methods of the embodiments of the present application.

With continued reference to fig. 12, the chip 700 may further include a memory 720.

From the memory 720, the processor 710 can call and run a computer program to implement the method in the embodiment of the present application. The memory 720 may be used to store instructions and codes, instructions, etc. that may be executed by the processor 710. The memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

With continued reference to fig. 12, the chip 700 may also include an input interface 730.

The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.

With continued reference to fig. 12, the chip 700 may further include an output interface 740.

The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

It should be understood that the chip 700 may be applied to a network device in this embodiment, and the chip may implement a corresponding process implemented by the network device in each method in this embodiment, and may also implement a corresponding process implemented by a terminal device in each method in this embodiment, which is not described herein again for brevity.

It will also be appreciated that the various components in the chip 700 are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

The processors referred to above may comprise, but are not limited to:

general purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like.

The processor may be configured to implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. The steps of the method disclosed in connection with the embodiments of this application may be embodied directly in a hardware decoding processor, or in a combination of hardware and software modules in a decoding processor. The software module may be located in ram, flash memory, rom, prom, eprom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and combines hardware thereof to complete the steps of the method.

The memories referred to above include, but are not limited to:

volatile memory and/or non-volatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. The volatile Memory may be a Random Access Memory (RAM) which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), enhanced Synchronous SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

It should be noted that the memory described herein is intended to comprise these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing a computer program. The computer readable storage medium stores one or more programs, the one or more programs comprising instructions, which when executed by a portable electronic device comprising a plurality of application programs, enable the portable electronic device to perform the methods of the method embodiments.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables a computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.

Optionally, the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

The embodiment of the application also provides a computer program product which comprises a computer program.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

The embodiment of the application also provides a computer program. The computer program, when executed by a computer, enables the computer to perform the methods of the method embodiments.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

In addition, an embodiment of the present application further provides a communication system, where the communication system may include the terminal device and the network device mentioned above to form the communication system 100 shown in fig. 1, and details are not described herein for brevity. It should be noted that the term "system" or the like in this document may also be referred to as "network management architecture" or "network system" or the like.

It is also to be understood that the terminology used in the embodiments of the present application and the appended claims is for the purpose of describing particular embodiments only, and is not intended to be limiting of the embodiments of the present application.

For example, as used in the examples of this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

Those of skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the embodiments of the present application.

If implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented or make a contribution to the prior art, or may be implemented in the form of a software product stored in a storage medium and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: u disk, removable hard disk, read only memory, random access memory, magnetic or optical disk, etc. for storing program codes.

It can be clearly understood by those skilled in the art that, for convenience and simplicity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways.

For example, the division of a unit or a module or a component in the above-described device embodiments is only one logical function division, and there may be other divisions in actual implementation, for example, a plurality of units or modules or components may be combined or may be integrated into another system, or some units or modules or components may be omitted, or not executed.

Also for example, the units/modules/components described above as separate/display components may or may not be physically separate, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the units/modules/components can be selected according to actual needs to achieve the purposes of the embodiments of the present application.

Finally, it should be noted that the above shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The above description is only a specific implementation of the embodiments of the present application, but the scope of the embodiments of the present application is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the embodiments of the present application, and all the changes or substitutions should be covered by the scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims

A method of wireless communication, comprising:

and receiving indication information, wherein the indication information is used for indicating the terminal equipment to switch the multicast bearer.
The method of claim 1, further comprising:

determining a processing action of a Packet Data Convergence Protocol (PDCP) layer for the terminal device based on the indication information.
The method of claim 2, wherein the processing action for the PDCP layer of the terminal device comprises at least one of:

triggering a PDCP release and/or establishment procedure;

triggering a PDCP rebuilding process;

resetting/reinitializing PDCP variables;

keeping a PDCP variable;

submitting the data in the cache to an upper layer; and

triggering PDCP release and/or establishment procedures.
The method of claim 3, wherein resetting/reinitializing the PDCP variable comprises resetting/reinitializing the PDCP variable based on a sequence number of a first packet transmitted by the target access network device.
The method of claim 3, wherein the data in the buffer is a PDCP Service Data Unit (SDU).
The method according to any of claims 1 to 5, wherein the indication information is further used to indicate a first processing action or a second processing action; the processing action of determining the Packet Data Convergence Protocol (PDCP) layer aiming at the terminal equipment based on the indication information comprises the following steps:

determining the first processing action indicated by the indication information or the second processing action indicated by the indication information as a processing action aiming at a Packet Data Convergence Protocol (PDCP) layer of the terminal equipment.
The method of claim 6, wherein the first processing action is at least one of: triggering PDCP release and/or establishment procedures, resetting/reinitializing PDCP variables, and delivering buffered data to upper layers.
The method according to claim 6 or 7, characterized in that the second handling action is at least one of the following: and triggering a PDCP rebuilding process, keeping a PDCP variable and not submitting data in the buffer to an upper layer.
The method of claim 8, wherein the second handling action is not to submit the data in the buffer to an upper layer, and wherein the data in the buffer is used for performing combined ordering with the data received after switching the multicast bearer.
The method according to any one of claims 6 to 9, wherein the scenario corresponding to the first processing action is a scenario in which packet loss does not need to be avoided or a scenario in which lossy handover does not need to be avoided.
The method according to any one of claims 6 to 10, wherein the scenario corresponding to the second processing action is a scenario in which packet loss needs to be avoided or a scenario of lossless handover.
The method according to any one of claims 1 to 11, wherein the receiving indication information comprises:

receiving the indication information sent by the source access network equipment, or

And receiving the indication information sent by the target access network equipment through the source access network equipment.
A method of wireless communication, comprising:

and sending indication information, wherein the indication information is used for indicating the terminal equipment to switch the multicast bearer.
The method of claim 13, wherein the indication information is configured to trigger the terminal device to perform a processing action for a Packet Data Convergence Protocol (PDCP) layer of the terminal device.
The method of claim 14, wherein the processing action for the PDCP layer of the terminal device comprises at least one of:

triggering a PDCP release and/or establishment procedure;

triggering a PDCP rebuilding process;

resetting/reinitializing PDCP variables;

maintaining a PDCP variable;

submitting the data in the cache to an upper layer; and

triggering PDCP release and/or establishment procedures.
The method of claim 15, wherein resetting/reinitializing the PDCP variable comprises resetting/reinitializing the PDCP variable based on a sequence number of a first packet transmitted by a target access network device.
The method of claim 15, wherein the data in the buffer is a PDCP service data unit, SDU.
The method according to any of claims 13 to 17, wherein the indication information is further configured to indicate a first processing action or a second processing action, and the first processing action indicated by the indication information or the second processing action indicated by the indication information is a processing action for a packet data convergence protocol, PDCP, layer of the terminal device.
The method of claim 18, wherein the first processing action is at least one of: triggering PDCP release and/or establishment procedures, resetting/reinitializing PDCP variables, and delivering buffered data to upper layers.
The method according to claim 18 or 19, wherein the second handling action is at least one of: and triggering a PDCP reconstruction process, keeping a PDCP variable, and not submitting the data in the buffer to an upper layer.
The method of claim 20, wherein the second handling action is not to submit the data in the buffer to an upper layer, and wherein the data in the buffer is used for performing combined ordering with the data received after switching the multicast bearer.
The method according to any one of claims 18 to 21, wherein the scenario corresponding to the first processing action is a scenario in which packet loss does not need to be avoided or a scenario in which lossy switching does not need to be avoided.
The method according to any one of claims 18 to 22, wherein the scenario corresponding to the second processing action is a scenario in which packet loss needs to be avoided or a scenario of lossless handover needs to be avoided.
The method according to any one of claims 13 to 23, wherein the method is applied to a target network device, and the sending the indication information comprises:

and receiving the indication information sent by the source network equipment through the source network equipment.
The method according to any one of claims 14 to 24, wherein the method is applied to a source network device, and the sending the indication information comprises:

and receiving the indication information sent by the source network equipment.
A terminal device, comprising:

and the communication unit is used for receiving indication information, and the indication information is used for indicating the terminal equipment to switch the multicast bearer.
A network device, comprising:

and the communication unit is used for sending indication information, and the indication information is used for indicating the terminal equipment to switch the multicast bearer.
A terminal device, comprising:

a processor, a memory for storing a computer program, and a transceiver, the processor for invoking and executing the computer program stored in the memory to perform the method of any one of claims 1 to 12.
A network device, comprising:

a processor, a memory for storing a computer program, and a transceiver, the processor for invoking and executing the computer program stored in the memory to perform the method of any of claims 13-25.
A chip, comprising:

a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any of claims 1 to 12 or the method of any of claims 13 to 25.
A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 12 or the method of any one of claims 13 to 25.
A computer program product comprising computer program instructions to cause a computer to perform the method of any of claims 1 to 12 or the method of any of claims 13 to 25.
A computer program, c h a r a c t e r i z e d in that the computer program causes a computer to perform the method of any of claims 1-12 or the method of any of claims 13-25.