CN113950042A

CN113950042A - Identification method, sending method and related equipment

Info

Publication number: CN113950042A
Application number: CN202010694240.1A
Authority: CN
Inventors: 吴昱民
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-07-17
Filing date: 2020-07-17
Publication date: 2022-01-18

Abstract

The application discloses an identification method, a sending method and related equipment, and belongs to the technical field of communication. The identification method comprises the following steps: receiving first target configuration information, wherein the first target configuration information is used for determining a first association relation between multicast service and unicast load; and identifying the first multicast service transmitted by the first unicast bearer according to the first association relation. When the terminal receives the multicast service through the first unicast bearer, the terminal can accurately identify that the first unicast bearer transmits the first multicast service, thereby avoiding the failure of receiving the service data caused by the incapability of identifying the multicast service transmitted by the unicast bearer, and further achieving the effect of reducing the failure rate of receiving the service data.

Description

Identification method, sending method and related equipment

Technical Field

The present application belongs to the field of communication technologies, and in particular, to an identification method, a transmission method, and a related device.

Background

In the prior art, when receiving a downlink Service through a unicast bearer, a terminal identifies, through a Quality of Service flow ID (QFI) corresponding to data, whether a type of a Service corresponding to the data received in the unicast bearer is a unicast Service or a multicast Service.

However, when the base station sends the multicast service through the unicast bearer, since the base station may not know which UEs are to receive the multicast service when the multicast service is sent to the base station, the terminal cannot simply identify which multicast service the data belongs to through the data corresponding to the QFI, which results in a high failure rate of receiving the service data.

Disclosure of Invention

The embodiment of the application provides an identification method, a sending method and related equipment, which can solve the problem of high receiving failure rate of service data caused by the fact that a terminal cannot identify multicast service sent by unicast bearer.

In a first aspect, an identification method is provided, which is applied to a terminal, and the method includes:

receiving first target configuration information, wherein the first target configuration information is used for determining a first association relation between multicast service and unicast load;

and identifying the first multicast service transmitted by the first unicast bearer according to the first association relation.

In a second aspect, a sending method is provided, which is applied to a network side device, and the method includes:

and sending first target configuration information, wherein the first target configuration information is used for determining a first association relation between multicast service and unicast load.

In a third aspect, an identification apparatus is provided, which is applied to a terminal, and includes:

an obtaining module, configured to receive first target configuration information, where the first target configuration information is used to determine a first association relationship between a multicast service and a unicast bearer;

and the identification module is used for identifying the first multicast service transmitted by the first unicast bearer according to the first association relation.

In a fourth aspect, a sending apparatus is provided, where the sending apparatus is applied to a network side device, and the sending apparatus includes:

a second sending module, configured to send first target configuration information, where the first target configuration information is used to determine a first association relationship between a multicast service and a unicast bearer.

In a fifth aspect, there is provided a terminal comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, which when executed by the processor, performs the steps of the method according to the first aspect.

In a sixth aspect, a network-side device is provided, which comprises a processor, a memory, and a program or instructions stored on the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method according to the second aspect.

In a seventh aspect, there is provided a readable storage medium on which a program or instructions are stored, which program or instructions, when executed by a processor, implement the steps of the method according to the first aspect or implement the steps of the method according to the second aspect.

In an eighth aspect, a chip is provided, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a network-side device program or instruction, implement the method according to the first aspect, or implement the method according to the second aspect.

In this embodiment of the present application, a terminal may obtain, according to first target configuration information sent by a network side device, a first association relationship between a multicast service and a unicast bearer, where in the first association relationship, the first unicast bearer associates a first multicast service. Therefore, when the terminal receives the multicast service through the first unicast bearer, the terminal can accurately identify that the first unicast bearer transmits the first multicast service, thereby avoiding the failure of receiving the service data caused by the incapability of identifying the multicast service transmitted by the unicast bearer, and further achieving the effect of reducing the failure rate of receiving the service data.

Drawings

FIG. 1 is a block diagram of a wireless communication system to which embodiments of the present application are applicable;

FIG. 2 is a flow chart of an identification method provided by an embodiment of the present application;

fig. 3 is a flowchart of a transmission method provided in an embodiment of the present application;

fig. 4 is a block diagram of an identification device provided in an embodiment of the present application;

fig. 5 is a structural diagram of a transmitting apparatus according to an embodiment of the present application;

fig. 6 is a block diagram of a communication device provided in an embodiment of the present application;

fig. 7 is a structural diagram of a terminal provided in an embodiment of the present application;

fig. 8 is a structural diagram of a network-side device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. 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.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

It is noted that the technology described in the embodiments of the present application is not limited to Long Term Evolution (LTE)/LTE-Advanced (LTE-a) systems, but may also be used in other wireless communication systems, such as Code Division Multiple Access (CD)MA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, although the techniques may also be applied to applications other than NR system applications, such as 6 th generation (6 th generation)^thGeneration, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be called as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a multicast Service distribution entity, wherein the Base Station may be referred to as a node B, an evolved node B, an access Point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a home evolved node B, a WLAN access Point, a WiFi node, a Transmission Receiving Point (TRP), or some other suitable terminology in the field, and the Base Station is not limited to a specific technical vocabulary as long as the same technical effect is achieved. The multicast service issuing entity may be: a Multicast Broadcast Service center (BMSC), an AF (Application Function), a NEF (Network Element Function), an MBSF (Multicast Broadcast message Function), or an MBSU (Multicast Broadcast Service Function).

For convenience of understanding, some contents related to the embodiments of the present invention are explained below:

first, Multimedia Broadcast Multicast Service (MBMS), and Broadcast Multicast Service (MBS).

In a Long Term Evolution (LTE) system, MBMS/MBS can be transmitted in two ways:

MBMS/MBS transmission mode 1: the MBMS service Single Frequency Network (MBSFN) subframe is transmitted through a Physical Multicast Channel (PMCH) Physical Channel. The Control Information is transmitted through System Information (e.g., System Information Block (SIB) 13) and a broadcast Control Channel (MCCH), and the data is transmitted through an MTCH (broadcast Traffic Channel).

MBMS/MBS transmission mode 2: and a Physical Downlink Shared Channel (PDSCH) scheduled by a Physical Downlink Control Channel (PDCCH). The Control information is transmitted through system information (e.g., SIB20) and a Single Cell Multicast Control Channel (SC-MCCH), and the data is transmitted through a Single Cell Multicast Traffic Channel (SC-MTCH). The SC-MCCH is transmitted through a PDSCH scheduled by a PDCCH (Single Cell Radio Network Temporary Identity, SC-RNTI), and the SC-MTCH is transmitted through a PDSCH scheduled by a PDCCH (Group Radio Network Temporary Identity, G-RNTI).

The MBS service is transmitted through a specific MBMS Radio Bearer (MRB) Radio Bearer. MBS services can be marked by the following identities:

temporary Mobile Group Identity (TMGI);

quality of Service flow identification (Quality of Service flow ID, QFI);

protocol Data Unit (PDU) Session (Session) ID.

And II, unicasting.

The unicast reception of the UE is received through a specific unicast Data Radio Bearer (DRB). Service data received by the UE from the unicast bearer needs to be delivered to a protocol entity (or application service entity) corresponding to the service. The unicast service may be data transmission scheduled by a Cell Radio Network Temporary Identity (C-RNTI) PDCCH channel.

In the embodiment of the present application, the multicast service may be the MBMS or MBS, but is not limited thereto.

Referring to fig. 2, fig. 2 is a flowchart of an identification method provided in an embodiment of the present application. The identification method of the embodiment of the application can be applied to the terminal.

As shown in fig. 2, the identification method may include the steps of:

step 201, receiving first target configuration information, where the first target configuration information is used to determine a first association relationship between a multicast service and a unicast bearer.

In implementation, the terminal may obtain the first association relationship directly by receiving the first target configuration information, or may obtain the first association relationship by processing the received first target configuration information, which may be determined according to actual situations, and this is not limited in this embodiment of the present application.

Step 202, according to the first association relationship, identifying a first multicast service transmitted by a first unicast bearer.

It should be appreciated that in the first association, the first unicast bearer is associated with the first multicast traffic. In this way, the terminal may identify the multicast service transmitted by the first unicast bearer as the first multicast service by searching the first association relationship.

In a specific implementation, in a first implementation manner, multicast services associated with each unicast bearer in the first association relationship may be different from each other. In a second implementation manner, the multicast services associated with the plurality of unicast bearers in the first association relationship may be the same, but the unicast bearers associated with different multicast services are different. Therefore, when the terminal receives the multicast service through a certain unicast bearer, the terminal can accurately identify the multicast service associated with the unicast bearer, thereby avoiding the failure of receiving the service data caused by the failure of identifying the multicast service transmitted by the unicast bearer, and further achieving the effect of reducing the failure rate of receiving the service data.

For ease of understanding, examples are illustrated below:

assuming that the first association includes: a first unicast bearer, a second unicast bearer, and a third unicast bearer. In the first implementation manner, the first unicast bearer may be associated with the multicast service 1; the second unicast bearer may be associated with multicast service 2; the third unicast bearer may be associated with multicast traffic 3. In the second implementation manner, the first unicast bearer and the second unicast bearer may be associated with the multicast service 1; the third unicast bearer may be associated with multicast traffic 2.

In addition, assuming that the terminal is to receive the multicast service through the third unicast bearer, for the first implementation manner, the terminal may identify the multicast service 3 when the multicast service is transmitted through the third unicast bearer by searching the first association relationship; for the first implementation manner, the terminal may identify the multicast service 2 when the multicast service is transmitted by the third unicast bearer by searching the first association relationship.

According to the identification method provided by the embodiment of the application, the terminal can acquire the first association relationship between the multicast service and the unicast bearer according to the first target configuration information sent by the network side device, wherein in the first association relationship, the first unicast bearer associates the first multicast service. Therefore, when the terminal receives the multicast service through the first unicast bearer, the terminal can accurately identify that the first unicast bearer transmits the first multicast service, thereby avoiding the failure of receiving the service data caused by the incapability of identifying the multicast service transmitted by the unicast bearer, and further achieving the effect of reducing the failure rate of receiving the service data.

The following describes the acquisition of the first association relationship in the embodiment of the present application:

the first embodiment: the terminal may obtain the first association relationship by processing the received first target configuration information.

For the first embodiment, optionally, the first target configuration information includes first configuration information and second configuration information, where the first configuration information is used to configure a second association relationship between a multicast service and a first bearer of the multicast service, and the second configuration information is used to configure a third association relationship between a unicast bearer and the first bearer;

after the receiving the first target configuration information and before the identifying the first multicast traffic transmitted by the first unicast bearer, the method further includes:

and determining the first association relation according to the second association relation and the third association relation.

Optionally, the first configuration information may include: description information of multicast service; an identity of the first bearer. Optionally, the second configuration information may include: an identity of said first bearer; identification of unicast bearer.

In this embodiment of the present application, optionally, the description information of the multicast service may include at least one of the following:

a multicast service identity (e.g., TMGI);

multicast service name (e.g., central television station);

multicast service interpretation (e.g., multicast service distribution channel (e.g., central television station program sent over broadcast television network); multicast service features (e.g., voice, or video));

a Transmission address of the multicast service (e.g., a Transmission Control Protocol (TCP) and/or an Internet Protocol (IP) address, and a port number of a Transmission end corresponding to the Transmission address);

a transmission Protocol of a multicast service (e.g., Hypertext Transfer Protocol (HTTP), or Simple Message Transfer Protocol (SMTP));

session identification of multicast service (e.g., MBS session-1).

Optionally, the identifier of the first bearer may include at least one of:

a data flow identification (e.g., QFI-1);

a data Session identification (e.g., PDU Session-1);

a radio bearer identification (e.g., DRB-1);

a Logical Channel identification (e.g., Logical Channel Identification (LCID) -1);

a multicast scheduling identifier (e.g., a PDCCH scheduling multicast traffic identified by MBS RNTI).

Optionally, the identifier of the unicast bearer may include at least one of:

a radio bearer identification (e.g., DRB-1);

logical channel identification (e.g., LCID-1);

cell Group identity (e.g., Master Cell Group (MCG) or Secondary Cell Group (SCG));

radio Link Control (RLC) entity identification (e.g., Primary RLC);

unicast scheduling identity (e.g., PDCCH scheduling multicast traffic identified by C-RNTI).

It should be noted that, in practical applications, the first configuration information and the second configuration information may be carried in the same message, or may be carried in different messages respectively.

Optionally, the first configuration information is carried by a service description file, and the second configuration information is carried by a Radio Resource Control (RRC) message, but is not limited thereto. Such as: the multicast Service issuing entity configures the second association relationship in a Service Description file (e.g., User Service Description (USD)). And the base station configures the third association relationship through an RRC message.

In the first embodiment, the terminal may determine the first bearer associated with the multicast service through the second association relationship, and in addition, may determine the unicast bearer associated with the first bearer through the third association relationship. Therefore, the terminal may determine the unicast bearer associated with the multicast service according to the second association relationship and the third association relationship, that is, determine the first association relationship. And further determining the multicast service associated with the unicast bearer according to the first association relation.

For ease of understanding, examples are illustrated below:

the RRC message carries the third association, in which DRB-1 associates Q with the second association, and in which TMGI-1 associates QoS flow-1. Thus, the UE can recognize that data of TMGI-1 is carried in DRB-1.

Second embodiment: the terminal may obtain the first association relationship directly by receiving the first target configuration information.

For the second embodiment, optionally, the first target configuration information is used to configure the first association relationship.

Optionally, the first target configuration information includes: description information of multicast service; identification of unicast bearer. For the description of the "description information of multicast service" and the "identifier of unicast bearer", reference may be made to the foregoing contents, which are not described herein again.

Optionally, the first target configuration information is carried by an RRC message, but is not limited thereto.

In the second embodiment, the first target configuration information is directly used to configure the first association relationship, so that the terminal can directly identify the multicast service associated with the unicast bearer according to the first target configuration information.

For ease of understanding, examples are illustrated below:

the RRC message carries the first association relationship, and in the first association relationship, the TMGI-1 associates with the DRB-1, so that the UE can recognize that the DRB-1 carries the data of the TMGI-1.

The establishment of the unicast bearer associated with the multicast service in the embodiment of the present application is described as follows:

in this embodiment of the present application, optionally, before identifying the first multicast service transmitted by the first unicast bearer, the method further includes:

receiving indication information, where the indication information is used to indicate that a second multicast service of the first cell is sent through a unicast bearer, and the second multicast service includes the first multicast service.

In a specific implementation, the second multicast service may include one or more specified multicast services, and in this case, the indication information is used to indicate that the specific multicast service of the first cell is sent through a unicast bearer. The second multicast service may also be a multicast service that is referred to in general, and in this case, the indication information is used to indicate that the multicast services of the first cell are all sent through unicast bearer. The first cell may include one or more target cells. The indication Information may be carried in a System Information Block (SIB), but is not limited thereto.

Such as: the network side equipment indicates the sending mode of the multicast service TMGI-1 of the cell-1 in the SIB message to be sending through the DRB.

In this way, if the terminal needs to receive the second multicast service, the data of the second unicast service of the first cell can be received through unicast bearer according to the indication of the indication information, so that the success rate of service data reception can be improved.

It should be understood that, in the case that the terminal receives the indication information, the network side device needs to establish a unicast bearer of the first multicast service, that is, the first unicast bearer, before sending the first multicast service.

In this embodiment of the present application, the first unicast bearer may be established by a terminal or a network side device, and the specific description is as follows:

scene one, the first unicast bearer is established by a terminal.

In a scenario one, optionally, after receiving the indication information and before receiving the first target configuration information, the method further includes:

and sending a request message under the condition that the terminal needs to receive the first multicast service, wherein the request message is used for requesting to establish a unicast bearer.

For ease of understanding, examples are illustrated below:

the IDLE (IDLE)/INACTIVE (INACTIVE) UE finds that the sending mode of the multicast service TMGI-1 of the cell-1 is sending through the DRB through the SIB message, and then the UE may initiate a connection establishment procedure in the cell-1 and request to establish a unicast bearer of the multicast service TMGI-1.

Further, after the sending the request message, the method further includes:

receiving a request response message, wherein the request response message indicates the terminal to establish a first unicast bearer;

establishing the first unicast bearer.

In specific implementation, after receiving the request message, the network side device may determine whether to allow the terminal to establish a unicast bearer. Under the condition that the network side device allows the terminal to establish the unicast bearer, the network side device may send a request response message to the terminal, where the request response message indicates that the terminal establishes the first unicast bearer.

And in a second scenario, the first unicast bearer is established by network side equipment.

In scenario two, after the network side device sends the indication information, the first unicast bearer may be directly established. In this way, signaling overhead may be saved compared to scenario one.

In this embodiment of the present application, after establishing the first unicast bearer, the network side device may establish at least one of the following association relationships: the first association relationship in which the first unicast bearer associates with a first multicast service; a third association in which the first unicast bearer is associated with a bearer of a first multicast service. In this way, the network side device may send the first target configuration information to the terminal, so that the terminal identifies the first multicast service when the multicast service associated with the first unicast bearer is identified.

The following describes the behavior of a terminal that identifies a multicast service transmitted by a unicast bearer in the embodiment of the present application:

optionally, after identifying the first multicast service transmitted by the first unicast bearer, the method may further include:

and receiving the data of the first multicast service through the first unicast bearer.

Further, after receiving the data of the first multicast service, the terminal may transmit the received data of the first multicast service to a protocol entity (or, an application entity) corresponding to the first multicast service, so as to improve reliability of data utilization.

Referring to fig. 3, fig. 3 is a flowchart of a sending method provided in an embodiment of the present application. The sending method of the embodiment of the application is applied to network side equipment.

As shown in fig. 3, the transmission method may include the steps of:

step 301, sending first target configuration information, where the first target configuration information is used to determine a first association relationship between a multicast service and a unicast bearer.

According to the sending method of the embodiment of the application, the network side device can send the first target configuration information to the terminal, and the first target configuration information is used for determining the first association relationship between the multicast service and the unicast bearer. In this way, the terminal may obtain the first association relationship between the multicast service and the unicast bearer according to the first target configuration information sent by the network side device. Therefore, when the terminal receives the multicast service through the first unicast bearer, the terminal can accurately identify that the first unicast bearer transmits the first multicast service, and can avoid the failure of receiving the service data caused by the incapability of identifying the multicast service transmitted by the unicast bearer, thereby achieving the effect of reducing the failure rate of receiving the service data.

Optionally, the first target configuration information includes first configuration information and second configuration information, where the first configuration information is used to configure a second association relationship between a multicast service and a first bearer of the multicast service, and the second configuration information is used to configure a third association relationship between a unicast bearer and the first bearer.

Optionally, the first configuration information includes: description information of multicast service; an identity of the first bearer.

Optionally, the second configuration information includes: an identity of the first bearer; identification of unicast bearer.

Optionally, the first configuration information is carried by a service description file, and the second configuration information is carried by a radio resource control RRC message.

Optionally, the first target configuration information is used to configure the first association relationship.

Optionally, the first target configuration information includes: description information of multicast service; identification of unicast bearer.

Optionally, the first target configuration information is carried through an RRC message.

Optionally, before sending the first target configuration information, the method further includes:

receiving second target configuration information, wherein the second target configuration information is used for configuring a second association relation between the multicast service and a first bearer of the multicast service;

and determining the first association relation according to the second association relation and a third association relation between the pre-established unicast bearer and the first bearer.

In this optional embodiment, the second target configuration information may be sent to the network side device by a core network node. The network side device may process the second association relationship and the third association relationship to obtain the first association relationship.

Optionally, the second target configuration information includes: description information of multicast service; an identity of the first bearer.

Optionally, the description information of the multicast service includes at least one of: multicast service identification; a multicast service name; multicast service interpretation; a transmission address of the multicast service; a transmission protocol of the multicast service; and the session identification of the multicast service.

Optionally, the identifier of the first bearer includes at least one of: a data stream identification; a data session identification; a radio bearer identity; a logical channel identification; and multicast scheduling identification.

Optionally, the identifier of the unicast bearer includes at least one of: a radio bearer identity; a logical channel identification; cell group identification; a radio link control, RLC, entity identity; and unicast scheduling identification.

and sending indication information, wherein the indication information is used for indicating that the second multicast service of the first cell is sent through a unicast bearer.

Optionally, after the sending the indication information and before the sending the first target configuration information, the method further includes:

receiving a request message sent by a terminal under the condition that a first multicast service needs to be received, wherein the request message is used for requesting to establish a unicast bearer;

wherein the first multicast service belongs to the second multicast service.

Optionally, after receiving the request message sent by the terminal and before sending the first target configuration information, the method further includes:

and sending a request response message, wherein the request response message indicates the terminal to establish the first unicast bearer.

a first unicast bearer is established.

establishing at least one of the following association relations: the first association relationship in which the first unicast bearer associates with a first multicast service; a third association in which the first unicast bearer is associated with a bearer of a first multicast service.

It should be noted that, the present embodiment is taken as an embodiment of a network side device corresponding to the embodiment of the method in fig. 2, and therefore, reference may be made to relevant descriptions in the embodiment of the method in fig. 2, and the same beneficial effects may be achieved. To avoid repetition of the description, the description is omitted.

It should be noted that, various optional implementations described in the embodiments of the present application may be implemented in combination with each other or separately, and the embodiments of the present application are not limited thereto.

For ease of understanding, examples are illustrated below:

embodiment one, service description file + RRC configuration co-association.

The method comprises the following steps: and the network side sends the configuration information of the association relationship between the multicast service and the multicast service bearer to the UE. (e.g., the multicast service publishing entity provides the association configuration information of the multicast service and the multicast service bearer in the USD.

The "association relationship configuration information carried by multicast service and multicast service" may include:

multicast service description information;

the multicast traffic carries information.

Wherein, the multicast service description information includes at least one of the following:

a multicast service identity (e.g., TMGI);

multicast service name (e.g., central television station);

the sending address of the multicast service (e.g., TCP and/or IP address, and the sending port number corresponding to the address);

a transmission Protocol of the multicast service (e.g., HTTP (Hypertext Transfer Protocol), or SMTP (Simple Message Transfer Protocol));

a session identity (e.g., MBS session-1).

Wherein the multicast service bearer information comprises at least one of:

data flow identification (e.g., QoS flow ID-1);

a data Session identification (e.g., PDU Session-1);

a radio bearer identification (e.g., DRB-1);

logical channel identification (e.g., LCID-1).

Step two: the network side configures a unicast bearer (such as DRB-1) for the UE, and associates the unicast bearer with a multicast service bearer.

For example, the data carried in DRB-1 is from QoS flow-1 (and/or PDU Session-1).

Wherein the unicast carried information comprises at least one of the following:

a radio bearer identification (e.g., DRB-1);

logical channel identification (e.g., LCID-1);

cell Group identity (e.g., MCG (Master Cell Group) or SCG (Secondary Cell Group));

an RLC (Radio Link Control) entity identity (e.g., primary RLC).

Wherein the information carried by the multicast service includes at least one of the following:

data flow identification (e.g., QoS flow ID-1);

a data Session identification (e.g., PDU Session-1).

Additionally, the network side may notify the UE that the specific multicast service transmission mode of the specific cell is "multicast service transmission through unicast bearer".

For example, the network side indicates the sending mode of the multicast service TMGI-1 of the cell-1 in the SIB message to be sending through the DRB.

Step three: and the UE configures information according to the association relation between the unicast bearer and the multicast bearer in the step two and the association relation between the multicast service and the multicast service bearer in the step one, so that the specific multicast service transmitted in the unicast bearer can be identified.

For example, the RRC message carries "association relationship between unicast bearer and multicast bearer" (e.g., DRB-1 corresponds to QoS flow-1), and the USD carries "association relationship configuration information between multicast service and multicast service bearer" (e.g., TMGI-1 corresponds to QoS flow-1), so that the UE can recognize that the DRB-1 carries multicast service-1.

And the UE transmits the received specific multicast service to a protocol entity (or an application entity) corresponding to the specific multicast service according to the specific multicast service transmitted in the unicast bearer.

Additionally, if the network side indicates that the specific multicast service transmission mode of the specific cell is "multicast service transmission through unicast bearer", the UE requests to establish unicast bearer of the multicast service when the specific multicast service needs to be accepted.

If IDLE/INACTIVE UE finds that the sending mode of the multicast service TMGI-1 of the cell-1 is sending through the DRB through the SIB message, the UE initiates a connection establishment process in the cell-1 and requests to establish a unicast bearer of the multicast service TMGI-1.

Example two: RRC configuration co-association.

The method comprises the following steps: the network side configures a unicast bearer (such as DRB-1) for the UE, and associates the unicast bearer with the multicast service.

For example, the data carried in DRB-1 is from TMGI-1.

Wherein the information of the multicast service comprises at least one of the following items:

multicast service description information (same as embodiment 1);

the multicast traffic carries information.

Wherein the multicast service bearer information comprises at least one of:

data flow identification (e.g., QoS flow ID-1);

a data Session identification (e.g., PDU Session-1).

Additionally, before configuring the unicast bearer and the association relationship between the unicast bearer and the multicast service for the UE, the network side receives the configuration of the correspondence relationship between the multicast bearer and the multicast service sent by the core. Wherein, the corresponding relation configuration of the multicast bearer and the multicast service comprises:

multicast service bearer information (same as embodiment 1);

multicast service description information (as described in embodiment 2 above).

Additionally, the network side may notify the UE that the specific multicast service transmission mode of the specific cell is "multicast service transmission through unicast bearer". For example, the network side indicates the sending mode of the multicast service TMGI-1 of the cell-1 in the SIB message to be sending through the DRB. The same as in example 1.

Step two: and the UE can identify the specific multicast service transmitted in the unicast bearer according to the association relation between the unicast bearer and the multicast service in the step one.

If the RRC message carries "association of unicast bearer and multicast service" (e.g., DRB-1 corresponding to TMGI-1), the UE may recognize that the DRB-1 carries multicast service-1.

The information of the unicast bearer is the same as that of embodiment 1.

Wherein, the information of the multicast service is the same as the step 1.

Additionally, if the network side indicates that the specific multicast service transmission mode of the specific cell is "multicast service transmission through unicast bearer", the UE requests to establish unicast bearer of the multicast service when the specific multicast service needs to be accepted. The same as in example 1.

In the first embodiment, the association relationship between the specific multicast service and the multicast service bearer is provided by the service description file. In the second embodiment, when the unicast bearer is established, the multicast service type of the unicast bearer is specified.

By applying the embodiment, the terminal can accurately identify the type of the multicast service when receiving the multicast service through unicast bearer, so that the UE can be ensured to send the received data to the corresponding service receiving entity, and the data receiving failure caused by the fact that the type of the data service cannot be identified is avoided.

In the identification method provided in the embodiment of the present application, the execution subject may be an identification device, or a control module in the identification device for executing the identification method. In the embodiment of the present application, an example in which an identification device executes an identification method is taken as an example, and the identification device provided in the embodiment of the present application is described.

Referring to fig. 4, fig. 4 is a structural diagram of an identification device provided in an embodiment of the present application.

As shown in fig. 4, the recognition apparatus 400 includes:

an obtaining module 401, configured to receive first target configuration information, where the first target configuration information is used to determine a first association relationship between a multicast service and a unicast bearer;

an identifying module 402, configured to identify, according to the first association relationship, a first multicast service that is transmitted by a first unicast bearer.

Optionally, the first target configuration information includes first configuration information and second configuration information, where the first configuration information is used to configure a second association relationship between a multicast service and a first bearer of the multicast service, and the second configuration information is used to configure a third association relationship between a unicast bearer and the first bearer;

the identification apparatus 400 further includes:

and the determining module is used for determining the first association relation according to the second association relation and the third association relation.

Optionally, the second configuration information includes: an identity of said first bearer; identification of unicast bearer.

Optionally, the identification apparatus 400 further includes:

a first receiving module, configured to receive indication information, where the indication information is used to indicate that a second multicast service of a first cell is sent through a unicast bearer, and the second multicast service includes the first multicast service.

Optionally, the identification apparatus 400 further includes:

a first sending module, configured to send a request message when the terminal needs to receive the first multicast service, where the request message is used to request to establish a unicast bearer.

Optionally, the identification apparatus 500 further includes:

a second receiving module, configured to receive a request response message, where the request response message indicates the terminal to establish a first unicast bearer;

a first establishing module, configured to establish the first unicast bearer.

Optionally, the identification apparatus 400 further includes:

a third receiving module, configured to receive the data of the first multicast service through the first unicast bearer.

The identification device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. By way of example, the mobile terminal may include, but is not limited to, the above-listed type of terminal 4, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a kiosk, or the like, and the embodiments of the present application are not limited in particular.

The identification device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

The identification apparatus 400 provided in the embodiment of the present application can implement each process implemented in the embodiment of the method in fig. 2, and achieve the same technical effect, and for avoiding repetition, the details are not repeated here.

In the transmission method provided in the embodiment of the present application, the execution main body may be a transmission apparatus, or a control module in the transmission apparatus for executing the transmission method. In the embodiment of the present application, a transmitting apparatus that executes a transmitting method is taken as an example, and the transmitting apparatus provided in the embodiment of the present application is described.

Referring to fig. 5, fig. 5 is a structural diagram of a transmitting apparatus according to an embodiment of the present application.

As shown in fig. 5, the transmission apparatus 500 includes:

a second sending module 501, configured to send first target configuration information, where the first target configuration information is used to determine a first association relationship between a multicast service and a unicast bearer.

Optionally, the sending apparatus 500 further includes:

a fourth receiving module, configured to receive second target configuration information, where the second target configuration information is used to configure a second association relationship between a multicast service and a first bearer of the multicast service;

Optionally, the sending apparatus 500 further includes:

and a third sending module, configured to send indication information, where the indication information is used to indicate that the second multicast service of the first cell is sent through a unicast bearer.

Optionally, the sending apparatus 500 further includes:

a fifth receiving module, configured to receive a request message sent by a terminal when the terminal needs to receive a first multicast service, where the request message is used to request establishment of a unicast bearer;

wherein the first multicast service belongs to the second multicast service.

Optionally, the sending apparatus 500 further includes:

a fourth sending module, configured to send a request response message, where the request response message indicates the terminal to establish the first unicast bearer.

Optionally, the sending apparatus 500 further includes:

and the second establishing module is used for establishing the first unicast bearer.

Optionally, the sending apparatus 500 further includes:

a third establishing module, configured to establish at least one of the following association relationships: the first association relationship in which the first unicast bearer associates with a first multicast service; a third association in which the first unicast bearer is associated with a bearer of a first multicast service.

The transmitting apparatus in the embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a network side device. The network-side device may include, but is not limited to, the types of the network-side device 5 listed above, and the embodiment of the present application is not particularly limited.

The sending apparatus 500 provided in this embodiment of the present application can implement each process implemented in the method embodiment of fig. 3, and achieve the same technical effect, and for avoiding repetition, details are not described here again.

Optionally, as shown in fig. 6, an embodiment of the present application further provides a communication device 600, which includes a processor 601, a memory 602, and a program or an instruction stored on the memory 602 and executable on the processor 601, for example, when the communication device 600 is a terminal, the program or the instruction is executed by the processor 601 to implement the processes of the method embodiment of fig. 2, and the same technical effect can be achieved. When the communication device 600 is a network-side device, the program or the instructions are executed by the processor 601 to implement the processes of the method embodiment shown in fig. 3, and the same technical effect can be achieved.

Fig. 7 is a schematic diagram of a hardware structure of a terminal for implementing the embodiment of the present application.

The terminal 700 includes, but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, and a processor 710.

Those skilled in the art will appreciate that the terminal 700 may further include a power supply (e.g., a battery) for supplying power to various components, which may be logically connected to the processor 710 via a power management system, so as to manage charging, discharging, and power consumption management functions via the power management system. The terminal structure shown in fig. 7 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or combine some components, or have a different arrangement of components, and will not be described again here.

It should be understood that in the embodiment of the present application, the input Unit 704 may include a Graphics Processing Unit (GPU) 7041 and a microphone 7042, and the Graphics Processing Unit 7041 processes image data of still pictures or videos obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 707 includes a touch panel 7071 and other input devices 7072. The touch panel 7071 is also referred to as a touch screen. The touch panel 7071 may include two parts of a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

In the embodiment of the present application, the radio frequency unit 701 receives downlink data from a network side device and then processes the downlink data in the processor 710; in addition, the uplink data is sent to the network side equipment. In general, radio frequency unit 701 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 709 may be used to store software programs or instructions as well as various data. The memory 709 may mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. In addition, the Memory 709 may include a high-speed random access Memory and a nonvolatile Memory, where the nonvolatile 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. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.

Processor 710 may include one or more processing units; alternatively, processor 710 may be integrated into an application processor that handles primarily the operating system, user interface, and application programs or instructions, and a modem processor that handles primarily wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 710.

The radio frequency unit 701 is configured to: receiving first target configuration information, wherein the first target configuration information is used for determining a first association relation between multicast service and unicast load;

a processor 710 configured to: and identifying the first multicast service transmitted by the first unicast bearer according to the first association relation.

a processor 710 configured to:

Optionally, the radio frequency unit 701 is further configured to:

Optionally, the radio frequency unit 701 is further configured to: receiving a request response message, wherein the request response message indicates the terminal to establish a first unicast bearer;

processor 710, further configured to: establishing the first unicast bearer.

Optionally, the radio frequency unit 701 is further configured to:

It should be noted that, in this embodiment, the terminal 700 may implement each process in the method embodiment of fig. 2 in the embodiment of the present invention, and achieve the same beneficial effects, and for avoiding repetition, details are not described here again.

Specifically, the embodiment of the application further provides a network side device. As shown in fig. 8, the network device 800 includes: antenna 81, radio frequency device 82, baseband device 83. The antenna 81 is connected to a radio frequency device 82. In the uplink direction, the rf device 82 receives information via the antenna 81 and sends the received information to the baseband device 83 for processing. In the downlink direction, the baseband device 83 processes information to be transmitted and transmits the information to the rf device 82, and the rf device 82 processes the received information and transmits the processed information through the antenna 81.

The above band processing means may be located in the baseband device 83, and the method performed by the network side device in the above embodiment may be implemented in the baseband device 83, where the baseband device 83 includes a processor 84 and a memory 85.

The baseband device 83 may include, for example, at least one baseband board, on which a plurality of chips are disposed, as shown in fig. 8, wherein one chip, for example, the processor 84, is connected to the memory 85 to call up the program in the memory 85 to perform the network device operation shown in the above method embodiment.

The baseband device 83 may further include a network interface 86 for exchanging information with the radio frequency device 82, such as a Common Public Radio Interface (CPRI).

Specifically, the network side device of the embodiment of the present invention further includes: the instructions or programs stored in the memory 85 and executable on the processor 84, and the processor 84 calls the instructions or programs in the memory 85 to execute the processes in the embodiment of the method in fig. 3, and achieve the same technical effects, which are not described herein for avoiding repetition.

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the above-mentioned identification method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the method embodiment in fig. 2 or fig. 3, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or an instruction, to implement each process in the method embodiment shown in fig. 2 or fig. 3, and can achieve the same technical effect, and details are not repeated here to avoid repetition.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present application has been described with reference to the embodiments shown in the drawings, the present application is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that many more modifications and variations can be made without departing from the spirit of the application and the scope of the appended claims.

Claims

1. An identification method applied to a terminal, the method comprising:

2. The method of claim 1, wherein the first target configuration information comprises first configuration information and second configuration information, the first configuration information is used for configuring a second association relationship between multicast traffic and a first bearer of multicast traffic, and the second configuration information is used for configuring a third association relationship between unicast bearer and the first bearer;

3. The method of claim 2, wherein the first configuration information comprises: description information of multicast service; an identity of the first bearer.

4. The method of claim 2, wherein the second configuration information comprises: an identity of said first bearer; identification of unicast bearer.

5. The method of claim 2, wherein the first configuration information is carried by a service description file and the second configuration information is carried by a Radio Resource Control (RRC) message.

6. The method of claim 1, wherein the first target configuration information is used to configure the first association relationship.

7. The method of claim 6, wherein the first target configuration information comprises: description information of multicast service; identification of unicast bearer.

8. The method of claim 6, wherein the first target configuration information is carried via an RRC message.

9. The method of claim 1, wherein prior to identifying the first multicast traffic for the first unicast bearer transmission, the method further comprises:

10. The method of claim 9, wherein after the receiving the indication information and before the receiving the first target configuration information, the method further comprises:

under the condition that the terminal needs to receive the first multicast service, sending a request message, wherein the request message is used for requesting to establish a unicast bearer;

establishing the first unicast bearer.

11. The method of claim 1, wherein after identifying the first multicast traffic for the first unicast bearer transmission, the method further comprises:

12. A sending method is applied to a network side device, and is characterized in that the method comprises the following steps:

13. The method of claim 12, wherein the first target configuration information comprises first configuration information and second configuration information, the first configuration information is used for configuring a second association relationship between multicast traffic and a first bearer of multicast traffic, and the second configuration information is used for configuring a third association relationship between unicast bearer and the first bearer.

14. The method of claim 13, wherein the first configuration information comprises: description information of multicast service; an identity of the first bearer.

15. The method of claim 13, wherein the second configuration information comprises: an identity of the first bearer; identification of unicast bearer.

16. The method of claim 13, wherein the first configuration information is carried by a service description file and the second configuration information is carried by a Radio Resource Control (RRC) message.

17. The method of claim 12, wherein the first target configuration information is used to configure the first association relationship.

18. The method of claim 17, wherein the first target configuration information comprises: description information of multicast service; identification of unicast bearer.

19. The method of claim 17, wherein the first target configuration information is carried via an RRC message.

20. The method of claim 17, wherein prior to sending the first target configuration information, the method further comprises:

21. The method of claim 20, wherein the second target configuration information comprises: description information of multicast service; an identity of the first bearer.

22. The method of claim 12, wherein prior to sending the first target configuration information, the method further comprises:

23. The method of claim 22, wherein after the sending the indication information and before the sending the first target configuration information, the method further comprises:

receiving a request message sent by a terminal under the condition that a first multicast service is required to be received, wherein the request message is used for requesting to establish a unicast bearer, and the first multicast service belongs to the second multicast service;

24. The method of claim 22, wherein after the sending the indication information and before the sending the first target configuration information, the method further comprises:

a first unicast bearer is established.

25. The method according to claim 23 or 24, wherein before sending the first target configuration information, the method further comprises:

26. An identification device applied to a terminal, the identification device comprising:

27. The apparatus according to claim 26, wherein the first target configuration information includes first configuration information and second configuration information, the first configuration information is used to configure a second association relationship between multicast traffic and a first bearer of multicast traffic, and the second configuration information is used to configure a third association relationship between unicast bearer and the first bearer;

the identification device further comprises:

28. The apparatus according to claim 26, wherein the first target configuration information is used to configure the first association relationship.

29. The identification device of claim 26, further comprising:

30. The identification device of claim 29, further comprising:

a first sending module, configured to send a request message when the terminal needs to receive the first multicast service, where the request message is used to request to establish a unicast bearer;

a first establishing module, configured to establish the first unicast bearer.

31. The identification device of claim 26, further comprising:

32. A transmitting device applied to a network side device is characterized in that the transmitting device comprises:

33. The apparatus of claim 32, wherein the first target configuration information comprises first configuration information and second configuration information, the first configuration information is used for configuring a second association relationship between multicast traffic and a first bearer of multicast traffic, and the second configuration information is used for configuring a third association relationship between unicast bearer and the first bearer.

34. The apparatus as claimed in claim 32, wherein the first target configuration information is used to configure the first association relationship.

35. The transmitting apparatus of claim 34, wherein the transmitting apparatus further comprises:

36. The transmitting apparatus of claim 32, wherein the transmitting apparatus further comprises:

37. The transmitting apparatus of claim 36, wherein the transmitting apparatus further comprises:

a fifth receiving module, configured to receive a request message sent by a terminal when a first multicast service needs to be received, where the request message is used to request establishment of a unicast bearer, and the first multicast service belongs to the second multicast service;

38. The transmitting apparatus of claim 36, wherein the transmitting apparatus further comprises:

39. The transmission apparatus according to claim 37 or 38, characterized in that the transmission apparatus further comprises:

40. A terminal comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the identification method according to any one of claims 1 to 11.

41. A network-side device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the transmission method according to any one of claims 12 to 25.

42. A readable storage medium, characterized in that it stores thereon a program or instructions which, when executed by a processor, implement the steps of the identification method according to any one of claims 1 to 11, or implement the steps of the transmission method according to any one of claims 12 to 25.