CN115669207A

CN115669207A - Method and device for establishing MBS (multicast broadcast multicast service), terminal equipment and network equipment

Info

Publication number: CN115669207A
Application number: CN202080101099.8A
Authority: CN
Inventors: 王淑坤
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-07-10
Filing date: 2020-07-10
Publication date: 2023-01-31
Also published as: WO2022006875A1

Abstract

The embodiment of the application provides a method and a device for establishing MBS service, terminal equipment and network equipment, wherein the method comprises the following steps: a terminal device sends a first RRC message to a network device, wherein the first RRC message is an RRC connection establishment request message or an RRC connection recovery request message, the first RRC message carries a first reason value, and the first reason value is used for indicating that the reason initiated by the first RRC message is MBS service establishment; and the terminal equipment receives a second RRC message sent by the network equipment, wherein the second RRC message is an RRC connection establishment message or an RRC connection recovery message.

Description

Method and device for establishing MBS (multicast broadcast multicast service), terminal equipment and network equipment

Technical Field

The embodiment of the present application relates to the field of mobile communication technologies, and in particular, to a method and an apparatus for establishing a Multimedia multicast Service (MBS) Service, a terminal device, and a network device.

Background

After entering a Radio Resource Control (RRC) connection state, the terminal device can receive the MBS service, and therefore, there is a need to quickly establish the MBS service. However, when the MBS service is established according to the current service establishment procedure, there may be a case of failed establishment, and how to effectively establish the MBS service is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a method and a device for establishing MBS service, terminal equipment and network equipment.

The method for establishing the MBS service provided by the embodiment of the application comprises the following steps:

a terminal device sends a first RRC message to a network device, wherein the first RRC message is an RRC connection establishment request message or an RRC connection recovery request message, the first RRC message carries a first reason value, and the first reason value is used for indicating that the reason initiated by the first RRC message is MBS service establishment;

and the terminal equipment receives a second RRC message sent by the network equipment, wherein the second RRC message is an RRC connection establishment message or an RRC connection recovery message.

network equipment receives a first RRC message sent by terminal equipment, wherein the first RRC message is an RRC connection establishment request message or an RRC connection recovery request message, the first RRC message carries a first reason value, and the first reason value is used for indicating that the reason initiated by the first RRC message is MBS service establishment;

and the network equipment sends a second RRC message to the terminal equipment, wherein the second RRC message is an RRC connection establishment message or an RRC connection recovery message.

The device for establishing the MBS service provided by the embodiment of the application comprises the following steps:

a sending unit, configured to send a first RRC message to a network device, where the first RRC message is an RRC connection establishment request message or an RRC connection recovery request message, where the first RRC message carries a first cause value, and the first cause value is used to indicate that a cause initiated by the first RRC message is MBS service establishment;

a receiving unit, configured to receive a second RRC message sent by the network device, where the second RRC message is an RRC connection setup message or an RRC connection recovery message.

a receiving unit, configured to receive a first RRC message sent by a terminal device, where the first RRC message is an RRC connection establishment request message or an RRC connection recovery request message, where the first RRC message carries a first cause value, and the first cause value is used to indicate that a cause initiated by the first RRC message is MBS service establishment;

a sending unit, configured to send a second RRC message to the terminal device, where the second RRC message is an RRC connection setup message or an RRC connection recovery message.

The terminal device provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing computer programs, and the processor is used for calling and running the computer programs stored in the memory and executing the method for establishing the MBS service.

The network device provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing computer programs, and the processor is used for calling and running the computer programs stored in the memory and executing the method for establishing the MBS service.

The chip provided by the embodiment of the application is used for realizing the method for establishing the MBS service.

Specifically, the chip includes: and the processor is used for calling and running the computer program from the memory so that the equipment provided with the chip executes the method for establishing the MBS service.

The computer-readable storage medium provided in the embodiments of the present application is used for storing a computer program, where the computer program enables a computer to execute the above-mentioned method for establishing an MBS service.

The computer program product provided by the embodiment of the present application includes computer program instructions, and the computer program instructions enable a computer to execute the method for establishing the MBS service.

The computer program provided in the embodiment of the present application, when running on a computer, enables the computer to execute the above-mentioned method for establishing an MBS service.

Through the technical scheme, the terminal equipment carries the first cause value for establishing the MBS service in the RRC connection establishment request message or the RRC connection recovery request message, so that the network equipment can determine that the service to be established is the MBS service, the terminal equipment receives the MBS service in a multicast mode, so that the resource waste is avoided, and on the basis, the network equipment cannot refuse the request of the terminal equipment, thereby realizing the quick establishment of the MBS service.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

fig. 2 is a first flowchart illustrating a method for establishing an MBS service according to an embodiment of the present application;

fig. 3 is a flowchart illustrating a second method for establishing an MBS service according to an embodiment of the present application;

fig. 4 is a third flowchart illustrating a method for establishing an MBS service according to an embodiment of the present application;

fig. 5 is a first schematic structural diagram of a device for establishing an MBS service according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a device for establishing an MBS service according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a chip of an embodiment of the present application;

fig. 9 is a schematic block diagram of a communication system according to 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.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a system, a 5G communication system, a future communication system, or the like.

For example, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Alternatively, the Network device 110 may be an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the Network device may be a mobile switching center, a relay station, an Access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a future communication system, and the like.

The communication system 100 further comprises at least one terminal 120 located within the coverage area of the network device 110. As used herein, "terminal" includes, but is not limited to, a connection via a wireline, such as via a Public Switched Telephone Network (PSTN), a Digital Subscriber Line (DSL), a Digital cable, a direct cable connection; and/or another data connection/network; and/or via a Wireless interface, such as for a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal that is arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal may refer to an access terminal, user Equipment (UE), a subscriber unit, a subscriber station, mobile, remote 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 in a 5G network, or a terminal in a future evolved PLMN, etc.

Optionally, the terminals 120 may perform direct-to-Device (D2D) communication therebetween.

Alternatively, the 5G communication system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.

Fig. 1 exemplarily shows one network device and two terminals, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminals within the coverage of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that a device having a communication function in a network/system in the embodiments of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal 120 having a communication function, and the network device 110 and the terminal 120 may be the specific devices described above and are not described again here; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association relationship describing an associated object, and means that there may be three relationships, for example, a and/or B, which may mean: 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.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application are described below.

With the pursuit of speed, delay, high-speed mobility, energy efficiency and the diversity and complexity of the services in future life, the third generation partnership project (3) ^rd Generation Partnership Project,3 GPP) the international organization for standardization began developing 5G. The main application scenarios of 5G are: enhanced Mobile Ultra wide band (eMBB), low-Latency high-reliability communication (URLLC), and large-scale machine type communication (LSC)(massive Machine-Type Communications，mMTC)。

On the one hand, the eMBB still targets users to obtain multimedia content, services and data, and its demand is growing very rapidly. On the other hand, since the eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., and the difference between the capabilities and the requirements is large, it cannot be said in a general way, and it must be analyzed in detail in connection with a specific deployment scenario. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety, and the like. Typical characteristics of mtc include: high connection density, small data volume, insensitive time delay service, low cost of module, long service life and the like.

In early NR deployment, complete NR coverage is difficult to obtain, so typical network coverage is wide-area LTE coverage and isolated island coverage pattern of NR. Moreover, a large amount of LTE is deployed below 6GHz, and the spectrum below 6GHz available for 5G is rare. NR must therefore be studied for spectrum applications above 6GHz, with limited high band coverage and fast signal fading. Meanwhile, in order to protect the early-stage LTE investment of mobile operators, a tight coupling (light interworking) working mode between LTE and NR is provided.

RRC state

In order to reduce air interface signaling, quickly recover wireless connection, and quickly recover data service, 5G defines a new Radio Resource Control (RRC) state, that is, an RRC INACTIVE (RRC _ INACTIVE) state. This state is distinguished from the RRC IDLE (RRC IDLE) state and the RRC ACTIVE (RRC ACTIVE) state. Wherein,

1) RRC _ IDLE state (IDLE state for short): the mobility is cell selection and reselection based on terminal equipment, paging is initiated by a Core Network (CN), and a paging area is configured by the CN. The base station side has no terminal equipment context and no RRC connection.

2) RRC _ CONNECTED state (CONNECTED state for short): the RRC connection exists, and the base station side and the terminal device side have a terminal device context. The network side knows that the location of the terminal device is at a particular cell level. Mobility is network side controlled mobility. Unicast data may be communicated between the terminal device and the base station.

3) RRC _ INACTIVE state (INACTIVE state for short): mobility is based on cell selection reselection of terminal equipment, connection between CN-NR exists, context of the terminal equipment exists on a certain base station, paging is triggered by RAN, a paging area based on the RAN is managed by the RAN, and the network side knows that the position of the terminal equipment is based on the paging area level of the RAN.

MBMS

MBMS is a technology for transmitting data from one data source to a plurality of UEs by sharing network resources, which enables broadcasting and multicasting of a multimedia service at a higher rate (e.g., 256 kbps) by effectively using network resources while providing the multimedia service.

Because the MBMS spectrum efficiency is low, it is not enough to effectively carry and support the operation of the mobile tv type service. Therefore, in LTE, 3GPP explicitly proposes to enhance the support capability for downlink high-speed MBMS services, and determines the design requirements for the physical layer and air interface.

The 3GPP R9 introduces evolved MBMS (eMBMS) into LTE. eMBMS proposes a Single Frequency Network (SFN) concept, that is, a Multimedia Broadcast multicast service Single Frequency Network (MBSFN), where MBSFN employs a uniform Frequency to simultaneously transmit service data in all cells, but needs to ensure synchronization between the cells. The method can greatly improve the distribution of the overall signal-to-noise ratio of the cell, and the frequency spectrum efficiency can be correspondingly and greatly improved. eMBMS implements broadcast and multicast of services based on IP multicast protocol.

In LTE or LTE-Advanced (LTE-a), MBMS has only a broadcast bearer mode and no multicast bearer mode. In addition, the reception of the MBMS service is applicable to the UE in an idle state or a connected state.

A Single Cell Point To multipoint (SC-PTM) concept is introduced into a 3GPP R13, and the SC-PTM is based on an MBMS network architecture.

MBMS introduces new logical channels including a Single Cell-Multicast Control Channel (SC-MCCH) and a Single Cell-Multicast Transport Channel (SC-MTCH). The SC-MCCH and the SC-MTCH are mapped to a Downlink-Shared Channel (DL-SCH), and the DL-SCH is further mapped to a Physical Downlink Shared Channel (PDSCH), wherein the SC-MCCH and the SC-MTCH belong to a logical Channel, the DL-SCH belongs to a transport Channel, and the PDSCH belongs to a Physical Channel. The SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat reQuest (HARQ) operation.

MBMS introduces a new System Information Block (SIB) type, SIB20. Specifically, the configuration information of the SC-MCCH is transmitted through the SIB20, and one cell has only one SC-MCCH. The configuration information of the SC-MCCH comprises the following steps: the modification period of the SC-MCCH, the repetition period of the SC-MCCH, and the scheduling of the wireless frame and the subframe of the SC-MCCH. Further, 1) the boundary of the modification period of the SC-MCCH satisfies SFN mod m =0, where SFN represents the system frame number of the boundary, and m is the modification period of the SC-MCCH configured in SIB20 (i.e., SC-MCCH-modification period). 2) And scheduling the radio frame of the SC-MCCH to meet the following requirements: SFN mod MCCH-repetition period = MCCH-Offset, where SFN represents a system frame number of a radio frame, MCCH-repetition period represents a repetition period of the SC-MCCH, and MCCH-Offset represents an Offset of the SC-MCCH. 3) The sub-frame of the SC-MCCH is scheduled and indicated by SC-MCCH-Subframe.

The SC-MCCH is scheduled through a Physical Downlink Control Channel (PDCCH). On one hand, a new Radio Network Temporary Identity (RNTI), that is, a Single Cell RNTI (SC-RNTI), is introduced to identify a PDCCH (such as an SC-MCCH PDCCH) for scheduling an SC-MCCH, and optionally, the SC-RNTI is fixedly valued as FFFC. On the other hand, a new RNTI, that is, a Single Cell Notification RNTI (SC-N-RNTI) is introduced to identify a PDCCH (e.g., notification PDCCH) for indicating a change Notification of the SC-MCCH, and optionally, the SC-N-RNTI is fixedly set to FFFB; further, the change notification may be indicated with one bit of 8 bits (bits) of DCI 1C. In LTE, the configuration information of SC-PTM is based on SC-MCCH configured by SIB20, and then SC-MCCH configures SC-MTCH which is used for transmitting service data.

Specifically, the SC-MCCH transmits only one message (i.e., SCPTMConfiguration) for configuring configuration information of the SC-PTM. The configuration information of SC-PTM includes: temporary Mobile Group Identity (TMGI), session Identity (session id), group RNTI (G-RNTI), discontinuous Reception (DRX) configuration information, SC-PTM service information of the neighbor cell, and the like. It should be noted that SC-PTM in R13 does not support Robust Header Compression (ROHC) function.

The downlink discontinuous reception of SC-PTMs is controlled by the following parameters: ondurationTimerSCPTM, drx-InactivetTimeSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.

When [ (SFN x 10) + subframe number ] module (SC-MTCH-scheduling cycle) = SC-MTCH-scheduling offset is satisfied, a timer onDurationTimerSCPTM is started;

when receiving downlink PDCCH dispatching, starting a timer drx-InactivetyTimerSCPTM;

the downlink SC-PTM service is received only when the timer onDurationTimerSCPTM or drx-inactivityttimerscptm is running.

SC-PTM service continuity adopts the MBMS service continuity concept based on SIB15, namely, SIB15+ MBMSIntestrindication mode. The traffic continuity of idle UEs is based on the concept of frequency priority.

In the technical solution of the embodiment of the present application, a new SIB (referred to as a first SIB) is defined, where the first SIB includes configuration information of a first MCCH, where the first MCCH is a control channel of an MBMS service, in other words, the first SIB is used to configure configuration information of a control channel of an NR MBMS, and optionally, the control channel of the NR MBMS may also be referred to as an NR MCCH (i.e., the first MCCH).

Further, the first MCCH is used to carry a first signaling, and in this embodiment of the present application, the name of the first signaling is not limited, for example, the first signaling is signaling a, the first signaling includes configuration information of at least one first MTCH, where the first MTCH is a traffic channel (also referred to as a data channel or a transport channel) of an MBMS service, and the first MTCH is used to transmit MBMS service data (e.g., service data of NR MBMS). In other words, the first MCCH is used to configure configuration information of a traffic channel of the NR MBMS, which may also be called NR MTCH (i.e., the first MTCH) optionally.

Specifically, the first signaling is used to configure a service channel of the NR MBMS, service information corresponding to the service channel, and scheduling information corresponding to the service channel. Further, optionally, the service information corresponding to the service channel, for example, the identification information for identifying the service, such as the TMGI, the session id, and the like. The scheduling information corresponding to the traffic channel, for example, the RNTI used when the MBMS service data corresponding to the traffic channel is scheduled, such as G-RNTI, DRX configuration information, and the like.

It should be noted that the transmission of the first MCCH and the first MTCH is scheduled based on the PDCCH. Wherein, the RNTI used by the PDCCH for scheduling the first MCCH uses a network-wide unique identifier, which is a fixed value. The RNTI used by the PDCCH for scheduling the first MTCH is configured through the first MCCH.

It should be noted that, in the embodiment of the present application, naming of the first SIB, the first MCCH, and the first MTCH is not limited. For convenience of description, the first SIB may also be referred to as SIB, the first MCCH may also be referred to as MCCH, the first MTCH may also be referred to as MTCH, and a PDCCH for scheduling MCCH (i.e., MCCH PDCCH) and a notification PDCCH are configured through SIB, wherein DCI carried through the MCCH PDCCH schedules PDSCH for transmitting MCCH (i.e., MCCH PDSCH). Further, M PDCCHs (namely MTCH 1 PDCCH, MTCH 2 PDCCH, 8230; MTCH M PDCCH) for scheduling MTCH are configured through the MCCH, wherein DCI carried by the MTCH n PDCCH schedules PDSCH (namely MTCH n PDSCH) for transmitting MTCH n, and n is an integer which is more than or equal to 1 and less than or equal to M. The MCCH and MTCH are mapped to DL-SCH, which belongs to logical channels, further to transport channels, and PDSCH to physical channels.

It should be noted that the MBMS service in the foregoing solution includes, but is not limited to, a multicast service and a multicast service. In the embodiment of the present application, MBS service is taken as an example for explanation, and the description of "MBS service" may also be replaced by "multicast service" or "MBMS service".

In NR, the terminal device can receive the MBS service after entering the connected state, so the terminal device needs to enter the connected state in order to receive the MBS service. Some MBS services require the terminal device to enter a connected state through paging to perform MBS service reception. Therefore, there is a need to quickly establish the MBS service, and how to effectively establish the MBS service is an optimization. Therefore, the following technical scheme of the embodiment of the application is provided.

Fig. 2 is a first flowchart illustrating a method for establishing an MBS service according to an embodiment of the present application, where as shown in fig. 2, the method for establishing an MBS service includes the following steps:

step 201: the method comprises the steps that terminal equipment sends a first RRC message to network equipment, wherein the first RRC message is an RRC connection establishment request message or an RRC connection recovery request message, the first RRC message carries a first reason value, and the first reason value is used for indicating that the reason initiated by the first RRC message is MBS service establishment.

In this embodiment, the network device may be a base station, such as a gNB.

In the embodiment of the application, the terminal device sends the first RRC message to the network device, and accordingly, the network device receives the first RRC message sent by the terminal device. Here, the first RRC message is an RRC connection setup request message or an RRC connection restoration request message.

In an optional manner, before the terminal device sends the first RRC message to the network device, the terminal device initiates a random access procedure to a currently camped serving cell, and specifically, the terminal device sends a preamble (i.e., msg 1) to the network device, receives an uplink grant (i.e., msg 2) sent by the network device, and sends the first RRC message (i.e., msg 3) to the network device based on the uplink grant.

In this embodiment of the present application, the first RRC message carries a first cause value, where the first cause value is used to indicate that a cause initiated by the first RRC message is MBS service establishment. Therefore, the network equipment can distinguish whether the service to be established is the MBS service establishment or other services according to the first reason value.

In an optional manner of this application, the first cause value is provided by a Non-Access Stratum (NAS) layer of the terminal device to an Access Stratum (AS) layer. And adding the first cause value in an RRC connection establishment request message or an RRC connection recovery request message by the AS layer.

In the embodiment of the present application, for the case of establishing the initial MBS service, the terminal device serves as a Mobile Originating (MO). For the MBS service setup case where the terminal device is paged to initiate, the terminal device is called (MT). These two cases will be described below.

● The first condition is as follows: terminal equipment as MO

The value of the first cause value is one of the following values:

a first value, wherein the first value is used for representing that data is to be initiated;

a second value, wherein the second value is used for representing that the initiated service is an MBS service;

a third value, wherein the third value is used for representing that the initiated MBS service has a first priority;

and a fourth value, wherein the fourth value is used for representing that the initiated MBS service has a second priority.

In the above scheme, the first priority is different from the second priority, and optionally, the first priority is higher than the second priority.

In one example, the first value is MO-data. MO-data characterizes that there is data to be launched.

In one example, the second value is MO-MBS. The MO-MBS represents that the initiated service is MBS service.

In one example, the third value is MO-MBS-highpriority. The MO-MBS-highpriority represents that the initiated MBS service has high priority.

In one example, the fourth value is MO-MBS-lowpriority. The MO-MBS-lowpriority represents that the initiated MBS service has low priority.

In an optional manner of this application, before the terminal device sends the first RRC message to the network device, the terminal device may obtain MBS service information in any one of the following manners.

The first method is as follows: the network equipment sends system broadcast information to the terminal equipment, correspondingly, the terminal equipment receives the system broadcast information sent by the network equipment, and acquires MBS service information of a service cell from the system broadcast information.

Here, the system broadcast information carries MBS service information of a serving cell.

The second method comprises the following steps: the network equipment sends RRC dedicated signaling to the terminal equipment, and correspondingly, the terminal equipment receives the RRC dedicated signaling sent by the network equipment and acquires MBS service information from the RRC dedicated signaling. Here, optionally, the RRC dedicated signaling is an RRC release message.

Here, the RRC dedicated signaling carries MBS service information.

In the foregoing solution, the MBS service information includes at least one of the following: identification information of MBS service, transmission state of MBS service, zone information of MBS service transmission.

Here, the transmission state of the MBS service is used to characterize the state of the MBS service as upcoming, ongoing, or finished.

Here, the zone information transmitted by the MBS service is characterized by at least one of: a cell list, a RAN code list, a Tracking Area (TA) list.

After the terminal equipment resides in or reselects a cell, the identification of the cell is obtained, then the identification is compared with the zone information transmitted by the MBS service, if the identification can be matched with the zone information, the establishment of the MBS service is triggered, otherwise, the establishment of the MBS service is not triggered.

● Case two: terminal equipment as MT

The first cause value is one of the following values:

a fifth value, the fifth value being used to represent that there is data to receive;

a sixth value, wherein the sixth value is used for representing that the received service is an MBS service;

a seventh value, wherein the seventh value is used for representing that the received MBS service has a first priority;

and an eighth value, wherein the eighth value is used for representing that the received MBS service has a second priority.

In one example, the fifth value is MT-data. MT-data characterizes that there is data to receive.

In one example, the sixth value is MT-MBS. And the MT-MBS represents that the received service is the MBS service.

In one example, the seventh value is MT-MBS-highpriority. The MT-MBS-high priority characterizes that the received MBS service has high priority.

In one example, the eighth value is MT-MBS-lowpreference. The MT-MBS-lowpriority characterizes that the received MBS service has low priority.

In an optional mode of the present application, before the terminal device sends the first RRC message to the network device, the network device sends a paging message to the terminal device, and accordingly, the terminal device receives the paging message sent by the network device, where the paging message carries first indication information, and the first indication information is used to indicate that the paging message is triggered by an MBS service and/or indicates an identifier of the MBS service.

Here, the paging message carries first indication information, and the terminal device can distinguish MBS service triggered paging or other service triggered paging according to the first indication information. For example: the first indication information comprises 1 bit indication information, and if the value of the 1 bit is 1, the paging message is triggered by the MBS service. For example: the first indication information may also include an identification (e.g., TMGI) of the MBS service, and may also characterize that the paging message is triggered by the MBS service.

Further, optionally, the paging message further carries identification information (i.e., pagingUE-Identity) of the terminal device, where the identification information of the terminal device is a Temporary Mobile Subscriber Identity (Serving-Temporary Mobile Subscriber Identity, S-TMSI); or, the identification information of the terminal device is a temporary identification (i.e., MBS specific temporal UE identity) of the terminal device in a multicast group where the MBS service is located. The terminal device can determine that the paging message is paging itself according to the identification information of the terminal device carried in the paging message.

Step 202: and the terminal equipment receives a second RRC message sent by the network equipment, wherein the second RRC message is an RRC connection establishment message or an RRC connection recovery message.

In this embodiment, the network device sends a second RRC message to the terminal device, and accordingly, the terminal device receives the second RRC message sent by the network device. Here, the terminal device completes establishment of SRB1 or service recovery after receiving the RRC connection setup message or RRC connection recovery cancel.

Further, in an optional manner, the terminal device sends a third RRC message to the network device, and correspondingly, the network device receives the third RRC message sent by the terminal device, where the third RRC message is an RRC connection setup complete message or an RRC connection recovery complete message, and the third RRC message carries identification information of the MBS service to be established.

Here, the identification information of the MBS service is, for example, TMGI. And the network equipment adds the terminal equipment to a multicast group corresponding to the MBS service according to the identification information of the MBS service.

Further, in an optional manner, the network device sends a fourth RRC message to the terminal device, and accordingly, the terminal device receives the fourth RRC message sent by the network device, where the fourth RRC message is an RRC connection reconfiguration message, and the fourth RRC message is used to establish the MBS service.

In the embodiment of the application, in order to enable the terminal device to correctly judge whether the terminal device establishes the MBS service in a unicast mode or the MBS service in a multicast mode when the terminal device establishes the MBS service, the network device needs to know the channel environment of the terminal device in advance to avoid the subsequent switching between the unicast mode and the multicast mode, and therefore, the terminal device reports the channel measurement result to the network device; wherein the channel measurement result is used for the network device to determine whether to send the MBS service in a unicast mode or in a multicast mode. Correspondingly, the network equipment receives the channel measurement result sent by the terminal equipment, and determines whether to send the MBS service in a unicast mode or in a multicast mode based on the channel measurement result.

Here, the terminal device reports the channel measurement result to the network device in an idle state or an inactive state. Or the terminal device reports the channel measurement result to the network device in the RRC connection establishment process or the RRC connection recovery process.

In an example, when the channel measurement result of the terminal device is poor, the network device determines to send the MBS service in a unicast manner, so that the receiving quality of the MBS service can be effectively improved.

In an example, when the channel measurement result of the terminal device is good, the network device determines to send the MBS service in a multicast manner, so that the network resource can be saved on the premise of ensuring the receiving quality of the MBS service.

In the foregoing scheme, the channel measurement result includes at least one of: the channel measurement result of the serving cell, the channel measurement result of the neighbor cell, the channel measurement result of the beam satisfying the condition in the serving cell, and the channel measurement result of the beam satisfying the condition in the neighbor cell. Here, the beam satisfying the condition may be one or more beams having the best channel quality. Alternatively, the beams that satisfy the condition may be one or more beams whose channel quality exceeds a certain threshold.

In the foregoing scheme, optionally, the channel measurement result includes at least one of: channel Quality Indication (CQI) measurement, reference Signal Received Power (RSRP) measurement, reference Signal Received Quality (RSRQ) measurement, signal to Interference plus Noise Ratio (SINR) measurement, and Signal to Interference Ratio (SIR) measurement.

Further, optionally, the terminal device reports, to the network device, identification information of an MBS service that the terminal device desires to receive, in addition to the channel measurement result, where the identification information of the MBS service is used for the network device to determine the MBS service to be received by the terminal device. Correspondingly, the network equipment receives the identification information of the MBS service which is sent by the terminal equipment and is expected to be received by the terminal equipment, and determines the MBS service to be received by the terminal equipment based on the identification information of the MBS service.

According to the technical scheme of the embodiment of the application, the terminal device reports the channel measurement result of the terminal device and the identification information of the MBS service expected to be received to the network device, so that the network device can accurately select the transmission mode (for example, a unicast mode or a multicast mode) of the MBS service, and further, the unnecessary conversion between the unicast mode and the multicast mode can be reduced.

Fig. 3 is a flowchart illustrating a second method for establishing an MBS service according to an embodiment of the present invention, where a terminal device is a UE and a network device is a gNB, as shown in fig. 3, the method for establishing an MBS service includes the following steps:

step 301: and the gNB sends SIB or RRC release message to the UE, carrying MBS service information.

Here, the SIB is system broadcast information, and the RRC release message is RRC dedicated signaling. The SIB or RRC release message carries MBS service information. Wherein, the MBS service information comprises at least one of the following: identification information (such as TMGI) of the MBS service, transmission state of the MBS service and zone information of MBS service transmission.

Step 302: and the UE sends an RRC connection establishment request message or an RRC connection recovery request message to the gNB, and the first reason value is 'MO-MBS'.

Here, the RRC connection establishment request message may also be referred to as "RRCSetupRequest". The RRC connection recovery request message may also be referred to as "RRCResumeRequest".

Step 303: the gNB sends an RRC connection setup message or an RRC connection recovery message to the UE.

Here, the RRC connection setup message may also be referred to as "RRCSetup". The RRC connection resume message may also be referred to as "RRCResume".

Step 304: and the UE sends an RRC connection establishment completion message or an RRC connection recovery completion message to the gNB, and the RRC connection establishment completion message or the RRC connection recovery completion message carries the identification information of the MBS service.

Here, the RRC connection setup complete message may also be referred to as "RRCSetupComplete". The RRC connection restoration complete message may also be referred to as "RRCResumeComplete". The identification information of the MBS service is, for example, TMGI.

Step 305: and the UE sends RRC dedicated signaling to the gNB, and carries the channel measurement result and/or the identification information of the MBS service.

Here, the identification information of the MBS service is, for example, TMGI.

Step 306: and the gNB sends an RRC connection reconfiguration message to the UE.

Here, the RRC connection reconfiguration message may also be referred to as "rrcreeconfiguration".

Step 307: and the UE sends an RRC connection reconfiguration completion message to the gNB.

Here, the RRC connection reconfiguration complete message may also be referred to as "rrcreeconfigurationcomplete".

In the technical solution of the embodiment of the present application, the UE indicates in the RRC connection establishment request message or the RRC connection recovery request message (i.e., msg 3) that the reason for establishing the RRC connection on the network side is the MBS service (i.e., the reason for initiating the RRC connection establishment request or the RRC connection recovery request is the MBS service establishment), if the network side is congested, the network side may not reject the terminal device, and because the UE receives the MBS service in a multicast manner, resource waste is not caused. The gNB can quickly establish the MBS service by informing the network side of the identification information of the MBS service to be received by the UE.

Fig. 4 is a third flowchart illustrating a method for establishing an MBS service according to an embodiment of the present application, where in this embodiment, a terminal device is a UE and a network device is a gNB, as shown in fig. 4, the method for establishing an MBS service includes the following steps:

step 400: and accessing an Access and Mobility Management Function (AMF) network element to send a paging message to the gNB, wherein the paging message carries first indication information for indicating that the paging message is triggered by the MBS service and/or indicating an identifier of the MBS service.

For example: for example: the first indication information comprises 1 bit indication information, and if the value of the 1 bit is 1, the paging message is triggered by the MBS service. For example: the first indication information may also include an identification (e.g., TMGI) of the MBS service, and may also characterize that the paging message is triggered by the MBS service.

Further, optionally, the paging message further carries identification information (i.e., pagingUE-Identity) of the terminal device, where the identification information of the terminal device is S-TMSI or MBS specific temporal UE Identity.

Step 401: and the gNB sends a paging message to the UE, and the gNB carries first indication information for indicating that the paging message is triggered by the MBS service and/or indicating the identification of the MBS service.

Before step 401, optionally, further comprising: and the gNB sends SIB or RRC release message to the UE, carrying MBS service information. Here, the SIB is system broadcast information, and the RRC release message is RRC dedicated signaling. The SIB or RRC release message carries MBS service information. Wherein, the MBS service information comprises at least one of the following: identification information (such as TMGI) of the MBS service, transmission state of the MBS service and zone information of MBS service transmission.

Step 402: and the UE sends an RRC connection establishment request message or an RRC connection recovery request message to the gNB, and the first reason value is 'MO-MBS'.

Here, the RRC connection setup request message may also be referred to as "RRCSetupRequest". The RRC connection recovery request message may also be referred to as "RRCResumeRequest".

Step 403: the gNB sends an RRC connection setup message or an RRC connection resume message to the UE.

Step 404: and the UE sends an RRC connection establishment completion message or an RRC connection recovery completion message to the gNB, and carries the identification information of the MBS service.

Here, the RRC connection setup complete message may also be referred to as "RRCSetupComplete". The RRC connection resume complete message may also be referred to as "RRCResumeComplete". The identification information of the MBS service is, for example, TMGI.

Step 405: and the UE sends RRC dedicated signaling to the gNB, and the RRC dedicated signaling carries the channel measurement result and/or the identification information of the MBS service.

Here, the identification information of the MBS service is, for example, TMGI.

Step 406: and the gNB sends an RRC connection reconfiguration message to the UE.

Step 407: and the UE sends an RRC connection reconfiguration completion message to the gNB.

In the technical scheme of the embodiment of the application, the network side indicates that the paging message is triggered by the MBS service and/or indicates the identification of the MBS service in the paging message, so that the UE can correctly tell the network side that the paged UE establishes the RRC connection, the UE indicates the reason for establishing the RRC connection of the network side in the RRC connection establishment request message or the RRC connection recovery request message (namely Msg 3) as the MBS service (namely the reason for initiating the RRC connection establishment request or the RRC connection recovery request is the MBS service establishment), if the load of the network side is congested, the network side does not need to reject the terminal equipment, and the UE receives the MBS service in a multicast mode, so that the resource waste is avoided. The gNB can quickly establish the MBS service by informing the network side of the identification information of the MBS service to be received by the UE.

Fig. 5 is a schematic structural diagram of a device for establishing an MBS service according to an embodiment of the present application, which is applied to a terminal device, and as shown in fig. 5, the device for establishing an MBS service includes:

a sending unit 501, configured to send a first RRC message to a network device, where the first RRC message is an RRC connection establishment request message or an RRC connection recovery request message, where the first RRC message carries a first cause value, and the first cause value is used to indicate that a cause initiated by the first RRC message is MBS service establishment;

a receiving unit 502, configured to receive a second RRC message sent by the network device, where the second RRC message is an RRC connection setup message or an RRC connection recovery message.

In an optional manner, the sending unit 501 is further configured to send a third RRC message to the network device, where the third RRC message is an RRC connection setup complete message or an RRC connection recovery complete message, and the third RRC message carries identification information of an MBS service to be established.

In an optional manner, the receiving unit 502 is further configured to receive a fourth RRC message sent by the network device, where the fourth RRC message is an RRC connection reconfiguration message, and the fourth RRC message is used to establish the MBS service.

In an alternative, the first cause value is provided to an AS layer by a NAS layer of the terminal device.

In an optional manner, a value of the first cause value is one of:

In an optional manner, the receiving unit 502 is further configured to receive system broadcast information sent by the network device, and acquire MBS service information of a serving cell from the system broadcast information.

In an optional manner, the receiving unit 502 is further configured to receive an RRC dedicated signaling sent by the network device, and acquire MBS service information from the RRC dedicated signaling.

In an optional manner, the MBS service information includes at least one of: the MBS service identification information, the MBS service transmission state and the MBS service transmission area information.

In an optional manner, the transmission state of the MBS service is used to characterize the state of the MBS service as upcoming, ongoing, or finished.

In an optional manner, the zone information transmitted by the MBS service is characterized by at least one of the following: cell list, RAN code list, TA list.

In an optional manner, the value of the first cause value is one of:

In an optional manner, the receiving unit 502 is further configured to receive a paging message sent by the network device, where the paging message carries first indication information, and the first indication information is used to indicate that the paging message is triggered by an MBS service and/or indicate an identifier of the MBS service.

In an optional manner, the paging message also carries identification information of the terminal device,

the identification information of the terminal equipment is S-TMSI; or,

the identification information of the terminal equipment is a temporary identification of the terminal equipment in a multicast group where the MBS service is located.

In an optional manner, the sending unit 501 is further configured to report a channel measurement result to the network device; wherein the channel measurement result is used for the network device to determine whether to send the MBS service in a unicast mode or in a multicast mode.

In an alternative, the channel measurement result includes at least one of:

the channel measurement result of the serving cell, the channel measurement result of the neighbor cell, the channel measurement result of the beam satisfying the condition in the serving cell, and the channel measurement result of the beam satisfying the condition in the neighbor cell.

In an alternative, the channel measurement result includes at least one of:

CQI measurement result, RSRP measurement result, RSRQ measurement result, SINR measurement result, and SIR measurement result.

In an optional manner, the sending unit 501 is further configured to report, to the network device, identification information of an MBS service that the terminal device expects to receive, where the identification information of the MBS service is used for the network device to determine the MBS service to be received by the terminal device.

Those skilled in the art should understand that the related description of the above-mentioned apparatus for establishing an MBS service in the embodiment of the present application may be understood by referring to the related description of the method for establishing an MBS service in the embodiment of the present application.

Fig. 6 is a schematic structural diagram of a device for establishing an MBS service according to an embodiment of the present application, which is applied to a network device, and as shown in fig. 6, the device for establishing an MBS service includes:

a receiving unit 601, configured to receive a first RRC message sent by a terminal device, where the first RRC message is an RRC connection establishment request message or an RRC connection recovery request message, where the first RRC message carries a first cause value, and the first cause value is used to indicate that a cause initiated by the first RRC message is MBS service establishment;

a sending unit 602, configured to send a second RRC message to the terminal device, where the second RRC message is an RRC connection setup message or an RRC connection recovery message.

In an optional manner, the receiving unit 601 is further configured to receive a third RRC message sent by the terminal device, where the third RRC message is an RRC connection setup complete message or an RRC connection recovery complete message, and the third RRC message carries identification information of an MBS service to be established.

In an optional manner, the sending unit 602 is further configured to send a fourth RRC message to the terminal device, where the fourth RRC message is an RRC connection reconfiguration message, and the fourth RRC message is used to establish the MBS service.

In an optional manner, a value of the first cause value is one of:

In an optional manner, the sending unit 602 is further configured to send system broadcast information to the terminal device, where the system broadcast information carries MBS service information of a serving cell.

In an optional manner, the sending unit 602 is further configured to send an RRC dedicated signaling to the terminal device, where the RRC dedicated signaling carries MBS service information.

In an optional manner, the transmission state of the MBS service is used to characterize the state of the MBS service as about to be performed, or being performed, or having ended.

In an optional manner, a value of the first cause value is one of:

a fifth value, the fifth value being used to indicate that there is data to receive;

In an optional manner, the sending unit 602 is further configured to send a paging message to the terminal device, where the paging message carries first indication information, and the first indication information is used to indicate that the paging message is triggered by an MBS service and/or indicate an identifier of the MBS service.

the identification information of the terminal equipment is S-TMSI; or,

the identification information of the terminal equipment is the temporary identification of the terminal equipment in the multicast group where the MBS service is located.

In an optional manner, the receiving unit 601 is further configured to receive a channel measurement result sent by the terminal device;

the device further comprises: a determining unit (not shown in the figure) configured to determine whether to send the MBS service in a unicast manner or in a multicast manner based on the channel measurement result.

In an alternative, the channel measurement result includes at least one of:

the channel measurement result of the serving cell, the channel measurement result of the neighboring cell, the channel measurement result of the beam satisfying the conditions in the serving cell, and the channel measurement result of the beam satisfying the conditions in the neighboring cell.

In an alternative, the channel measurement result includes at least one of:

In an optional manner, the receiving unit 601 is further configured to receive, sent by the terminal device, identification information of an MBS service that the terminal device desires to receive;

the determining unit is further configured to determine, based on the identification information of the MBS service, an MBS service to be received by the terminal device.

Fig. 7 is a schematic structural diagram of a communication device 700 according to an embodiment of the present application. The communication device may be a terminal device or a network device, and the communication device 700 shown in fig. 7 includes a processor 710, and the processor 710 may call and execute a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 7, the communication device 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 a separate device from the processor 710 or may be integrated into the processor 710.

Optionally, as shown in fig. 7, the communication device 700 may further include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate with other devices, and in particular, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 730 may include a transmitter and a receiver, among other things. The transceiver 730 may further include antennas, which may be one or more in number.

Optionally, the communication device 700 may specifically be a network device in the embodiment of the present application, and the communication device 700 may implement a 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 communication device 700 may specifically be a mobile terminal/terminal device according to this embodiment, and the communication device 700 may implement a corresponding process implemented by the mobile terminal/terminal device in each method according to this embodiment, which is not described herein again for brevity.

Fig. 8 is a schematic structural diagram of a chip of the embodiment of the present application. The chip 800 shown in fig. 8 includes a processor 810, and the processor 810 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 8, chip 800 may further include a memory 820. From the memory 820, the processor 810 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 820 may be a separate device from the processor 810 or may be integrated into the processor 810.

Optionally, the chip 800 may further include an input interface 830. The processor 810 may control the input interface 830 to communicate with other devices or chips, and specifically, may obtain information or data transmitted by other devices or chips.

Optionally, the chip 800 may further include an output interface 840. The processor 810 can control the output interface 840 to communicate with other devices or chips, and in particular, can output information or data to other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement a 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.

Optionally, the chip may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, no further description is given here.

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.

Fig. 9 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in fig. 9, the communication system 900 includes a terminal device 910 and a network device 920.

The terminal device 910 may be configured to implement the corresponding function implemented by the terminal device in the foregoing method, and the network device 920 may be configured to implement the corresponding function implemented by the network device in the foregoing method, for brevity, which is not described herein again.

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off the shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with 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. The software module may be located in ram, flash memory, rom, prom, 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.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile 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. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. 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 SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memories are exemplary but not limiting, for example, the memories in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, 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), direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

An embodiment of the present application further provides a computer-readable storage medium for storing a computer program.

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.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions enable the 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 program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instruction causes the computer to execute a 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.

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 a 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.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute a 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.

Those of ordinary 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 implementation. 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 present application.

It is clear to those skilled in the art that, for convenience and brevity 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 above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the 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 units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions may be stored in a computer-readable storage medium if they are implemented in the form of software functional units and sold or used as separate products. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including 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 method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

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

Claims

A method for establishing multimedia multicast service (MBS) service, the method comprises:

a terminal device sends a first Radio Resource Control (RRC) message to a network device, wherein the first RRC message is an RRC connection establishment request message or an RRC connection recovery request message, the first RRC message carries a first cause value, and the first cause value is used for indicating that the reason initiated by the first RRC message is MBS service establishment;

and the terminal equipment receives a second RRC message sent by the network equipment, wherein the second RRC message is an RRC connection establishment message or an RRC connection recovery message.
The method of claim 1, wherein the method further comprises:

and the terminal equipment sends a third RRC message to the network equipment, wherein the third RRC message is an RRC connection establishment completion message or an RRC connection recovery completion message, and the third RRC message carries identification information of the MBS service to be established.
The method of claim 2, wherein the method further comprises:

and the terminal equipment receives a fourth RRC message sent by the network equipment, wherein the fourth RRC message is an RRC connection reconfiguration message and is used for establishing the MBS service.
A method according to any of claims 1 to 3, wherein the first cause value is provided to an access AS layer by a non-access NAS layer of the terminal device.
The method of any one of claims 1 to 4, wherein the value of the first cause value is one of:

a first value, wherein the first value is used for representing that data is to be initiated;

a second value, wherein the second value is used for representing that the initiated service is an MBS service;

a third value, wherein the third value is used for representing that the initiated MBS service has a first priority;

and a fourth value, wherein the fourth value is used for representing that the initiated MBS service has a second priority.
The method of claim 5, wherein prior to the terminal device sending the first RRC message to the network device, the method further comprises:

and the terminal equipment receives the system broadcast information sent by the network equipment and acquires the MBS service information of the service cell from the system broadcast information.
The method of claim 5, wherein prior to the terminal device sending the first RRC message to the network device, the method further comprises:

and the terminal equipment receives the RRC dedicated signaling sent by the network equipment and acquires the MBS service information from the RRC dedicated signaling.
The method of claim 6 or 7, wherein the MBS service information comprises at least one of: the MBS service identification information, the MBS service transmission state and the MBS service transmission area information.
The method of claim 8, wherein the transmission state of the MBS service is used to characterize the state of the MBS service as upcoming, ongoing or ended.
The method of claim 8, wherein the zone information of the MBS service transmission is characterized by at least one of: cell list, RAN code list and tracking area TA list.
The method of any one of claims 1 to 4, wherein the first cause value takes on one of:

a fifth value, the fifth value being used to represent that there is data to receive;

a sixth value, wherein the sixth value is used for representing that the received service is an MBS service;

a seventh value, wherein the seventh value is used for representing that the received MBS service has a first priority;

and an eighth value, wherein the eighth value is used for representing that the received MBS service has a second priority.
The method of claim 11, wherein prior to the terminal device sending the first RRC message to the network device, the method further comprises:

the terminal device receives a paging message sent by the network device, wherein the paging message carries first indication information, and the first indication information is used for indicating that the paging message is triggered by an MBS service and/or indicating an identification of the MBS service.
The method of claim 12, wherein the paging message further carries identification information of the terminal device,

the identification information of the terminal equipment is a temporary mobile subscriber identity (S-TMSI); or,

the identification information of the terminal equipment is a temporary identification of the terminal equipment in a multicast group where the MBS service is located.
The method of any of claims 1 to 13, wherein the method further comprises:

the terminal equipment reports a channel measurement result to the network equipment; wherein, the channel measurement result is used for the network device to determine whether to send the MBS service in a unicast mode or in a multicast mode.
The method of claim 14, wherein the channel measurement results comprise at least one of:

the channel measurement result of the serving cell, the channel measurement result of the neighboring cell, the channel measurement result of the beam satisfying the conditions in the serving cell, and the channel measurement result of the beam satisfying the conditions in the neighboring cell.
The method of claim 14 or 15, wherein the channel measurement results comprise at least one of:

channel quality indicator CQI measurement, reference signal received power RSRP measurement, reference signal received quality RSRQ measurement, signal to interference plus noise ratio SINR measurement, signal to interference ratio SIR measurement.
The method of any of claims 14 to 16, wherein the method further comprises:

the terminal device reports the identification information of the MBS service which the terminal device expects to receive to the network device, and the identification information of the MBS service is used for the network device to determine the MBS service to be received by the terminal device.
A method for establishing MBS service, the method comprises:

network equipment receives a first RRC message sent by terminal equipment, wherein the first RRC message is an RRC connection establishment request message or an RRC connection recovery request message, the first RRC message carries a first reason value, and the first reason value is used for indicating that the reason initiated by the first RRC message is MBS service establishment;

and the network equipment sends a second RRC message to the terminal equipment, wherein the second RRC message is an RRC connection establishment message or an RRC connection recovery message.
The method of claim 18, wherein the method further comprises:

and the network equipment receives a third RRC message sent by the terminal equipment, wherein the third RRC message is an RRC connection establishment completion message or an RRC connection recovery completion message, and the third RRC message carries identification information of the MBS service to be established.
The method of claim 19, wherein the method further comprises:

and the network equipment sends a fourth RRC message to the terminal equipment, wherein the fourth RRC message is an RRC connection reconfiguration message, and is used for establishing the MBS service.
The method of any one of claims 18 to 20, wherein the value of the first cause value is one of:

a first value, wherein the first value is used for representing that data is to be initiated;

a second value, wherein the second value is used for representing that the initiated service is an MBS service;

a third value, wherein the third value is used for representing that the initiated MBS service has a first priority;

and a fourth value, wherein the fourth value is used for representing that the initiated MBS service has a second priority.
The method of claim 21, wherein the method further comprises:

and the network equipment sends system broadcast information to the terminal equipment, wherein the system broadcast information carries MBS service information of a service cell.
The method of claim 21, wherein the method further comprises:

and the network equipment sends an RRC dedicated signaling to the terminal equipment, wherein the RRC dedicated signaling carries MBS service information.
The method of claim 22 or 23, wherein the MBS service information comprises at least one of: the MBS service identification information, the MBS service transmission state and the MBS service transmission area information.
The method of claim 24, wherein the transmission state of the MBS service is used to characterize the state of the MBS service as upcoming, ongoing or ended.
The method of claim 24, wherein the zone information of the MBS service transmission is characterized by at least one of: cell list, RAN code list, TA list.
The method of any one of claims 18 to 20, wherein the first cause value takes on one of:

a fifth value, the fifth value being used to represent that there is data to receive;

a sixth value, wherein the sixth value is used for representing that the received service is an MBS service;

a seventh value, wherein the seventh value is used for representing that the received MBS service has a first priority;

and an eighth value, wherein the eighth value is used for representing that the received MBS service has a second priority.
The method of claim 27, wherein the method further comprises:

the network equipment sends a paging message to the terminal equipment, wherein the paging message carries first indication information, and the first indication information is used for indicating that the paging message is triggered by MBS service and/or indicating the identification of the MBS service.
The method of claim 28, wherein the paging message further carries identification information of the terminal device,

the identification information of the terminal equipment is S-TMSI; or,

the identification information of the terminal equipment is a temporary identification of the terminal equipment in a multicast group where the MBS service is located.
The method of any of claims 18 to 29, wherein the method further comprises:

and the network equipment receives the channel measurement result sent by the terminal equipment and determines whether to send the MBS service in a unicast mode or in a multicast mode based on the channel measurement result.
The method of claim 30, wherein the channel measurement results comprise at least one of:

the channel measurement result of the serving cell, the channel measurement result of the neighbor cell, the channel measurement result of the beam satisfying the condition in the serving cell, and the channel measurement result of the beam satisfying the condition in the neighbor cell.
The method of claim 30 or 31, wherein the channel measurement results comprise at least one of:

CQI measurement results, RSRP measurement results, RSRQ measurement results, SINR measurement results, and SIR measurement results.
The method of any of claims 30 to 32, wherein the method further comprises:

the network equipment receives the identification information of the MBS service which is sent by the terminal equipment and is expected to be received by the terminal equipment, and determines the MBS service to be received by the terminal equipment based on the identification information of the MBS service.
An apparatus for establishing an MBS service, the apparatus comprising:

a sending unit, configured to send a first RRC message to a network device, where the first RRC message is an RRC connection establishment request message or an RRC connection recovery request message, where the first RRC message carries a first cause value, and the first cause value is used to indicate that a cause initiated by the first RRC message is MBS service establishment;

a receiving unit, configured to receive a second RRC message sent by the network device, where the second RRC message is an RRC connection setup message or an RRC connection recovery message.
The apparatus of claim 34, wherein the sending unit is further configured to send a third RRC message to the network device, where the third RRC message is an RRC connection setup complete message or an RRC connection recovery complete message, and the third RRC message carries identification information of an MBS service to be established.
The apparatus of claim 35, wherein the receiving unit is further configured to receive a fourth RRC message sent by the network device, where the fourth RRC message is an RRC connection reconfiguration message, and the fourth RRC message is used to establish the MBS service.
The apparatus of any of claims 34 to 36, wherein the first cause value is provided by a NAS layer of the terminal device to an AS layer.
The apparatus of any one of claims 34 to 37, wherein the value of the first cause value is one of:

a first value, wherein the first value is used for representing that data is to be initiated;

a second value, wherein the second value is used for representing that the initiated service is an MBS service;

a third value, wherein the third value is used for representing that the initiated MBS service has a first priority;

and a fourth value, wherein the fourth value is used for representing that the initiated MBS service has a second priority.
The apparatus of claim 38, wherein the receiving unit is further configured to receive system broadcast information sent by the network device, and acquire MBS service information of a serving cell from the system broadcast information.
The apparatus of claim 38, wherein the receiving unit is further configured to receive an RRC dedicated signaling sent by the network device, and acquire MBS service information from the RRC dedicated signaling.
The apparatus of claim 39 or 40, wherein the MBS service information comprises at least one of: the MBS service identification information, the MBS service transmission state and the MBS service transmission area information.
The apparatus of claim 41, wherein the transmission state of the MBS service is used for characterizing the state of the MBS service as upcoming, ongoing or ended.
The apparatus of claim 41, wherein the zone information of the MBS service transmission is characterized by at least one of: cell list, RAN code list, TA list.
The apparatus of any one of claims 34 to 37, wherein the first cause value is one of:

a fifth value, the fifth value being used to represent that there is data to receive;

a sixth value, wherein the sixth value is used for representing that the received service is an MBS service;

a seventh value, wherein the seventh value is used for representing that the received MBS service has a first priority;

and an eighth value, wherein the eighth value is used for representing that the received MBS service has a second priority.
The apparatus of claim 44, wherein the receiving unit is further configured to receive a paging message sent by the network device, where the paging message carries first indication information, and the first indication information is used to indicate that the paging message is triggered by an MBS service and/or indicate an identifier of the MBS service.
The apparatus of claim 45, wherein the paging message further carries identification information of the terminal device,

the identification information of the terminal equipment is S-TMSI; or,

the identification information of the terminal equipment is a temporary identification of the terminal equipment in a multicast group where the MBS service is located.
The apparatus according to any one of claims 34 to 46, wherein the sending unit is further configured to report a channel measurement result to the network device; wherein the channel measurement result is used for the network device to determine whether to send the MBS service in a unicast mode or in a multicast mode.
The apparatus of claim 47, wherein the channel measurement comprises at least one of:

the channel measurement result of the serving cell, the channel measurement result of the neighbor cell, the channel measurement result of the beam satisfying the condition in the serving cell, and the channel measurement result of the beam satisfying the condition in the neighbor cell.
The apparatus of claim 47 or 48, wherein the channel measurement results comprise at least one of:

CQI measurement result, RSRP measurement result, RSRQ measurement result, SINR measurement result, and SIR measurement result.
The apparatus of any one of claims 47 to 49, wherein the sending unit is further configured to report, to the network device, identification information of an MBS service that the terminal device desires to receive, where the identification information of the MBS service is used for the network device to determine the MBS service to be received by the terminal device.
An apparatus for establishing an MBS service, the apparatus comprising:

a receiving unit, configured to receive a first RRC message sent by a terminal device, where the first RRC message is an RRC connection establishment request message or an RRC connection recovery request message, where the first RRC message carries a first cause value, and the first cause value is used to indicate that a cause initiated by the first RRC message is MBS service establishment;

a sending unit, configured to send a second RRC message to the terminal device, where the second RRC message is an RRC connection setup message or an RRC connection recovery message.
The apparatus of claim 51, wherein the receiving unit is further configured to receive a third RRC message sent by the terminal device, where the third RRC message is an RRC connection setup complete message or an RRC connection recovery complete message, and the third RRC message carries identification information of an MBS service to be established.
The apparatus of claim 52, wherein the sending unit is further configured to send a fourth RRC message to the terminal device, where the fourth RRC message is an RRC connection reconfiguration message, and the fourth RRC message is used to establish the MBS service.
The apparatus of any one of claims 51 to 53, wherein the value of the first cause value is one of:

a first value, wherein the first value is used for representing that data is to be initiated;

a second value, wherein the second value is used for representing that the initiated service is an MBS service;

a third value, wherein the third value is used for representing that the initiated MBS service has a first priority;

and a fourth value, wherein the fourth value is used for representing that the initiated MBS service has a second priority.
The apparatus of claim 54, wherein the sending unit is further configured to send system broadcast information to the terminal device, where the system broadcast information carries MBS service information of a serving cell.
The apparatus of claim 54, wherein the sending unit is further configured to send an RRC dedicated signaling to the terminal device, and the RRC dedicated signaling carries MBS service information.
The apparatus of claim 55 or 56, wherein the MBS service information comprises at least one of: identification information of MBS service, transmission state of MBS service, zone information of MBS service transmission.
The apparatus of claim 57, wherein the transmission status of the MBS service is used to characterize the status of MBS service as upcoming, ongoing or ended.
The apparatus of claim 57, wherein the zone information of the MBS service transmission is characterized by at least one of: cell list, RAN code list, TA list.
The apparatus of any one of claims 51 to 53, wherein the value of the first cause value is one of:

a fifth value, the fifth value being used to represent that there is data to receive;

a sixth value, wherein the sixth value is used for representing that the received service is an MBS service;

a seventh value, wherein the seventh value is used for representing that the received MBS service has a first priority;

and an eighth value, wherein the eighth value is used for representing that the received MBS service has a second priority.
The apparatus of claim 60, wherein the sending unit is further configured to send a paging message to the terminal device, where the paging message carries first indication information, and the first indication information is used to indicate that the paging message is triggered by an MBS service and/or indicate an identifier of the MBS service.
The apparatus of claim 61, wherein the paging message further carries identification information of the terminal device,

the identification information of the terminal equipment is S-TMSI; or,

the identification information of the terminal equipment is the temporary identification of the terminal equipment in the multicast group where the MBS service is located.
The apparatus according to any one of claims 51 to 62, wherein the receiving unit is further configured to receive a channel measurement result sent by the terminal device;

the device further comprises: a determining unit, configured to determine whether to send the MBS service in a unicast manner or in a multicast manner based on the channel measurement result.
The apparatus of claim 63, wherein the channel measurement results comprise at least one of:

the channel measurement result of the serving cell, the channel measurement result of the neighboring cell, the channel measurement result of the beam satisfying the conditions in the serving cell, and the channel measurement result of the beam satisfying the conditions in the neighboring cell.
The apparatus of claim 63 or 64, wherein the channel measurement results comprise at least one of:

CQI measurement results, RSRP measurement results, RSRQ measurement results, SINR measurement results, and SIR measurement results.
The apparatus of any one of claims 63-65,

the receiving unit is further configured to receive, sent by the terminal device, identification information of an MBS service that the terminal device expects to receive;

the determining unit is further configured to determine, based on the identifier information of the MBS service, the MBS service to be received by the terminal device.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and execute the computer program stored in the memory, performing the method of any of claims 1 to 17.
A network device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 18 to 33.
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 one of claims 1 to 17.
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 one of claims 18 to 33.
A computer-readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 17.
A computer-readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 18 to 33.
A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 1 to 17.
A computer program product comprising computer program instructions to cause a computer to perform the method of any of claims 18 to 33.
A computer program for causing a computer to perform the method of any one of claims 1 to 17.
A computer program for causing a computer to perform the method of any one of claims 18 to 33.