Detailed Description
The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The technical scheme of the embodiment of the application can be applied to various communication systems, such as a long term evolution (Long Term Evolution, LTE) system, an LTE frequency division duplex (Frequency Division Duplex, FDD) system, an LTE time division duplex (Time Division Duplex, TDD), a system, a 5G communication system or a future communication system and the like.
An exemplary communication system 100 to which embodiments of the present application may be applied 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 base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a 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, etc.
The communication system 100 further includes at least one terminal 120 located within the coverage area of the network device 110. As used herein, a "terminal" includes, but is not limited to, a device configured to receive/transmit communication signals via a wireline connection, such as via a public-switched telephone network (Public Switched Telephone Networks, PSTN), a digital subscriber line (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 (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 another terminal, and/or an internet of things (Internet of Things, ioT) device. Terminals arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones, personal communication systems (Personal Communications System, PCS) terminals that may combine a cellular radiotelephone with data processing, facsimile, and data communication capabilities, PDAs that may include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a global positioning system (Global Positioning System, GPS) receiver, 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), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a 5G network or a terminal in a future evolved PLMN, etc.
Alternatively, direct to Device (D2D) communication may be performed between the terminals 120.
Alternatively, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.
Fig. 1 illustrates one network device and two terminals, alternatively, the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within its coverage area, which is not limited by the embodiment of the present application.
Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited by the embodiment of the present application.
It should be understood that a device having a communication function in a network/system according to an embodiment 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 with communication functions, where the network device 110 and the terminal 120 may be specific devices described above, which are not described herein again, and the communication device may further include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiment of the present application.
It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean that a exists alone, while a and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following describes the technical solutions related to the embodiments of the present application.
With the pursuit of speed, delay, high speed mobility, energy efficiency and diversity and complexity of future life services, the third generation partnership project (3rd Generation Partnership Project,3 GPP) international standards organization has begun to develop 5G for this purpose. The main application scenes of the 5G are enhanced mobile Ultra-wideband (enhanced Mobile Broadband, eMBB), low-delay high-reliability communication (Ultra-Reliable Low-Latency Communications, URLLC) and large-scale machine type communication (MASSIVE MACHINE-Type Communications, mMTC).
On the one hand eMBB still aims at obtaining multimedia content, services and data by users, and the demand for which is growing very rapidly. On the other hand, since eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., the capability and demand of which are also quite different, detailed analysis must be performed in connection with a specific deployment scenario, not in general. Typical applications of URLLC include industrial automation, electrical automation, telemedicine operations (surgery), traffic safety assurance, and the like. mMTC include high connection density, small data volume, delay insensitive traffic, low cost and long life of the module, etc.
At early deployment of NRs, full NR coverage is difficult to acquire, so typical network coverage is wide area LTE coverage and island coverage mode of NRs. And a large amount of LTE is deployed below 6GHz, and the frequency spectrum below 6GHz which can be used for 5G is few. NR must study spectral applications above 6GHz while high-band coverage is limited and signal fading is fast. Meanwhile, in order to protect the early investment of the mobile operators in LTE, a working mode of tight coupling (tight interworking) between LTE and NR is proposed.
RRC state
5G for the purposes of reducing air interface signaling and fast recovery of radio connections, fast recovery of data traffic, a new radio resource control (Radio Resource Control, RRC) state, namely an RRC INACTIVE (RRC_INACTIVE) state, is defined. This state is different from the RRC IDLE (rrc_idle) state and the RRC ACTIVE (rrc_active) state. Wherein,
1) The rrc_idle state (IDLE state) is a mobility based cell selection reselection for a UE, paging is initiated by a Core Network (CN), and a paging area is configured by the CN. The base station side has no UE context and no RRC connection.
2) The rrc_connected state (simply referred to as CONNECTED state) is that there is an RRC connection and there is a UE context at the base station side and the UE side. The network side knows that the location of the UE is cell specific. Mobility is network-side controlled mobility. Unicast data may be transmitted between the UE and the base station.
3) The rrc_inactive state (abbreviated as INACTIVE) mobility is a cell selection reselection based on the UE, there is a connection between CN-NRs, the UE context exists on a certain base station, paging is triggered by RAN, paging area based on RAN is managed by RAN, and network side knows the location of the UE is based on paging area level of RAN.
Multimedia broadcast multicast service (Multimedia Broadcast Multicast Service, MBMS)
MBMS is a technology for transmitting data from one data source to a plurality of terminal equipments through a shared network resource, which can effectively utilize the network resource while providing a multimedia service, and realize broadcasting and multicasting of a multimedia service of a higher rate (e.g., 256 kbps).
Due to the low MBMS spectrum efficiency, it is not sufficient to effectively carry and support the operation of the mobile tv type service. In LTE, 3GPP has therefore explicitly proposed to enhance the support capability for the downlink high speed MBMS service and to determine the design requirements for the physical layer and the air interface.
The 3gpp R9 introduces evolved MBMS (eMBMS) into LTE. eMBMS proposes the concept of a single frequency network (Single Frequency Network, SFN), i.e. a multimedia broadcast multicast service single frequency network (Multimedia Broadcast multicast SERVICE SINGLE Frequency Network, MBSFN), wherein the MBSFN uses a unified frequency to simultaneously transmit service data in all cells, but ensures synchronization between cells. The method can greatly improve the overall signal-to-noise ratio distribution 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 protocols.
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 terminal devices in an idle state or a connected state.
A single cell point-to-multipoint (SINGLE CELL Point To Multiploint, SC-PTM) concept was introduced in 3gpp r13, SC-PTM being based on the MBMS network architecture.
MBMS introduces new logical channels including single cell multicast control channels (SINGLE CELL-Multicast Control Channel, SC-MCCH) and single cell multicast transport channels (SINGLE CELL-Multicast Transport Channel, SC-MTCH). The SC-MCCH and the SC-MTCH are mapped to a Downlink-SHARED CHANNEL, DL-SCH, and further, the DL-SCH is mapped to a physical Downlink-shared channel (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 (Hybrid Automatic Repeat reQuest, HARQ) operations.
MBMS introduces a new system information block (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 information such as a modification period of the SC-MCCH, a repetition period of the SC-MCCH, a radio frame and a subframe for scheduling the SC-MCCH, and the like. 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-ModificationPeriod). 2) The radio frame of the scheduled SC-MCCH satisfies SFN mod MCCH-RepetitionPeriod = MCCH-Offset, where SFN represents the system frame number of the radio frame, MCCH-RepetitionPeriod represents the repetition period of the SC-MCCH, and MCCH-Offset represents the Offset of the SC-MCCH. 3) The subframes for scheduling SC-MCCH are indicated by SC-MCCH-Subframe.
The SC-MCCH is scheduled through a physical downlink control channel (Physical Downlink Control Channel, PDCCH). In one aspect, a new radio network temporary identity (Radio Network Tempory Identity, RNTI), i.e., single cell RNTI (SINGLE CELL RNTI, SC-RNTI), is introduced to identify a PDCCH (e.g., SC-MCCH PDCCH) for scheduling the SC-MCCH, optionally with the SC-RNTI fixed value FFFC. On the other hand, a new RNTI, i.e., a single cell Notification RNTI (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, optionally, the SC-N-RNTI is fixed to FFFB, and further, the change Notification may be indicated by one bit of 8 bits (bits) of the DCI 1C. In LTE, the configuration information of SC-PTM is based on the SC-MCCH configured by SIB20, and then SC-MCCH configures SC-MTCH 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 the SC-PTM comprises a temporary mobile Group identifier (Temporary Mobile Group Identity, TMGI), a session identifier (seession id), a Group RNTI (G-RNTI), discontinuous reception (Discontinuous Reception, DRX) configuration information, SC-PTM service information of a neighbor cell, and the like. Note that SC-PTM in R13 does not support the robust header compression (Robust Header Compression, ROHC) function.
The downlink discontinuous reception of SC-PTM is controlled by onDurationTimerSCPTM, drx-INACTIVITYTIMERSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.
When [ (sfn×10) +subframe number ] module (SC-MTCH-SchedulingCycle) =sc-MTCH-SchedulingOffset is satisfied, a timer onDurationTimerSCPTM is started;
When receiving downlink PDCCH scheduling, starting a timer drx-INACTIVITYTIMERSCPTM;
The downstream SC-PTM service is received only when the timer onDurationTimerSCPTM or drx-INACTIVITYTIMERSCPTM is running.
The SC-PTM service continuity adopts the MBMS service continuity concept based on SIB15, namely a mode of SIB15 plus MBMSInterestIndication. The traffic continuity of the terminal device in idle state is based on the concept of frequency priority.
As can be seen from the above description, the configuration of the SC-PTM configures the SC-MCCH based on SIB20 and then configures the SC-MTCH based on the SC-MCCH. One cell has and only one SC-MCCH, that is, the SC-MCCH needs to be reacquired after the terminal device performs cell reselection, which will cause service interruption.
In NR systems, many scenarios require support of multicast and broadcast traffic demands, such as in the internet of vehicles, industrial internet, etc. It is necessary to introduce MBMS in the NR.
It should be noted that, the MBMS service in the above scheme includes, but is not limited to, a multicast service, an MBS service, and the like. The embodiment of the application is illustrated by taking MBS service as an example, and the description of the MBS service can be replaced by multicast service or broadcast service or MBMS service.
NR supports MBS services of broadcast type, configures MCCH through BCCH and configures MTCH through MCCT. Wherein, MCCH is used for transmitting configuration information of MBS service, and MTCH is used for transmitting MBS service data. One cell has only one MCCH, and the MCCH carries signaling (hereinafter referred to as MCCH signaling) to configure configuration information of a plurality of MBS services.
The terminal equipment in the RRC idle state, the RRC inactive state and the RRC connection state can receive the broadcasted MBS service. In order to ensure continuity of receiving broadcast MBS service by the terminal equipment in RRC connection state, the terminal equipment needs to indicate the network side terminal equipment to be interested in or receiving the identification information of the MBS service when in RRC connection state, so that the network side can take priority of the cell supporting the MBS service as a target cell for handover when making handover decision.
In NR, unlike LTE, after the terminal device enters the RRC connected state, the network side configures the terminal device with multiple dedicated BWP (e.g., up to 4 dedicated BWP), and the terminal device may switch between these dedicated BWP in the RRC connected state, for example, based on a mechanism such as DCI or a timer. The terminal device receives the broadcast MBS service in the RRC idle state or the RRC inactive state, after entering the RRC connection state from the RRC idle state or the RRC inactive state, the network side does not know the MBS service received before the terminal device, if the special BWP is configured for the terminal device according to the current mode, the terminal device can not normally receive the MBS service. For this reason, the following technical solutions of the embodiments of the present application are provided.
According to the technical scheme provided by the embodiment of the application, the terminal equipment reports the identification information of the MBS service which is interested in or is being received in the RRC idle state or the RRC inactive state, so that the network side is convenient to configure the proper special BWP, the terminal equipment is prevented from carrying out unnecessary BWP switching, and the MBS service is ensured to be normally received.
Fig. 2 is a flow chart of a method for indicating MBS service according to an embodiment of the present application, as shown in fig. 2, the method for indicating MBS service includes the following steps:
Step 201, a terminal device sends identification information of MBS service to a network device, the network device receives the identification information of MBS service sent by the terminal device, wherein the MBS service is expected by the terminal device or is being received, the identification information of the MBS service is used for configuring a special downlink BWP of the terminal device and/or the identification information of the MBS service is used for determining a target cell to be switched by the terminal device.
In the embodiment of the present application, the identification information of the MBS service is used for the network device to configure a dedicated downlink BWP for the terminal device and/or the identification information of the MBS service is used for the network device to select a target cell to be switched for the terminal device.
In the embodiment of the application, the terminal equipment can receive the broadcasted MBS service in the RRC idle state, the RRC inactive state or the RRC connection state. In the case that the terminal device receives the broadcast MBS service in the RRC idle state or the RRC inactive state, if the terminal device enters the RRC connected state from the RRC idle state or the RRC inactive state, the terminal device may send identification information of the MBS service to the network device after entering the RRC connected state or in the process of entering the RRC connected state, where the MBS service refers to an MBS service expected by the terminal device in the previous RRC idle state or the RRC inactive state or an MBS service being received, so that the network device may configure a dedicated downlink BWP for the terminal device and/or select a target cell to be switched for the terminal device according to the identification information of the MBS service indicated by the terminal device.
In the embodiment of the application, the identification information of the MBS service can be, but is not limited to, TMGI, G-RNTI and the like.
In the embodiment of the present application, the description of the "expected MBS service" may be replaced by the "interested MBS service".
The following describes the technical scheme of the embodiment of the present application in detail in combination with different cases.
Case one
After entering the RRC connection state, the terminal equipment sends the identification information of the MBS service to the network equipment through the RRC message.
Here, the RRC message may be an RRC message that is not security processed or an RRC message that is security processed. It should be noted that the RRC message transmitted before the AS layer security activation belongs to an RRC message that is not processed securely, and the RRC message transmitted after the AS layer security activation belongs to an RRC message that is processed securely. Wherein, the AS layer security activation takes a security activation completion (Securtiy mode complete) message AS a judgment standard.
In one scenario, the MBS service is a desired MBS service or a receiving MBS service of the terminal equipment in an RRC idle state, before the terminal equipment enters an RRC connection state, the terminal equipment sends an RRC establishment request message to the network equipment, the network equipment receives the RRC establishment request message sent by the terminal equipment, the network equipment sends an RRC establishment message to the terminal equipment, and the terminal equipment receives the RRC establishment message sent by the network equipment.
In another application scenario, the MBS service is expected MBS service or MBS service being received by the terminal equipment in an RRC inactive state, before the terminal equipment enters an RRC connection state, the terminal equipment sends an RRC recovery request message to the network equipment, the network equipment receives the RRC recovery request message sent by the terminal equipment, wherein the RRC recovery process is backed to an RRC establishment process, the network equipment sends an RRC establishment message to the terminal equipment, and the terminal equipment receives the RRC establishment message sent by the network equipment.
In an alternative manner, the terminal device sends the identification information of the MBS service to the network device through a first RRC message, and the network device receives the identification information of the MBS service sent by the terminal device through the first RRC message, where the first RRC message is an RRC message that is not subjected to security processing. In one example, the first RRC message is an RRC setup complete message or an MBS interest indication (MBSInterestingIndication) message.
In another alternative manner, the terminal device sends the identification information of the MBS service to the network device through a second RRC message, and the network device receives the identification information of the MBS service sent by the terminal device through the second RRC message, where the second RRC message is a RRC message that is processed safely. In one example, the second RRC message is a security activation complete message, or the second RRC message is a UE assistance information UEAssistanceInformation message, or the second RRC message is an MBS indication message, such as an MBS interest indication (MBSInterestingIndication) message.
In the embodiment of the present application, after a terminal device enters an RRC connection state, the network device sends an RRC reconfiguration message to the terminal device, and the terminal device receives the RRC reconfiguration message sent by the network device, where the RRC reconfiguration message carries first configuration information, and the first configuration information is used to determine configuration information of the dedicated downlink BWP.
(II) case two
After entering the RRC connection state, the terminal equipment sends the identification information of the MBS service to the network equipment through the RRC message.
In one scenario, the MBS service is a desired MBS service or a receiving MBS service of the terminal equipment in an RRC inactive state, before the terminal equipment enters an RRC connection state, the terminal equipment sends an RRC restoration request message to the network equipment, the network equipment receives the RRC restoration request message sent by the terminal equipment, the network equipment sends an RRC restoration message to the terminal equipment, and the terminal equipment receives the RRC restoration message sent by the network equipment and then enters the RRC connection state. After the terminal equipment enters the RRC connection state, the terminal equipment sends the identification information of the MBS service to the network equipment through an RRC recovery completion message, and the network equipment receives the identification information of the MBS service sent by the terminal equipment through the RRC recovery completion message.
In the above solution, optionally, the RRC restoration request message is used to determine first indication information, where the first indication information is used to indicate whether the terminal device is receiving a broadcast MBS service. Here, the implementation of the first indication information may be as follows:
The RRC recovery request message carries the first indication information in the mode I), wherein the value of the idle bit in the RRC recovery request message is used for representing the first indication information.
And II) the RRC restoration request message carries the first indication information, wherein the value of the restoration reason in the RRC restoration request message is used for representing the first indication information.
Mode III) the value of the logic channel identifier of the CCCH corresponding to the RRC resume request message is used to characterize the first indication information.
Here, the logical channel identifier of the CCCH is carried in a packet header corresponding to the RRC restoration request message in the MAC TB.
In the foregoing scenario, optionally, the RRC recovery message carries second configuration information, where the second configuration information is used to determine BWP configuration information of the PCell, and the bandwidth of the first active downlink BWP of the PCell includes the bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell. Here, the bandwidth of the MBS BWP of the PCell is determined by the network device according to the bandwidth of the MBS BWP corresponding to the MBS service identifier indicated by the terminal device. Specifically, the bandwidth of the MBS BWP of the PCell is the bandwidth of the MBS BWP corresponding to the MBS service identifier indicated by the terminal device.
In the embodiment of the present application, after a terminal device sends an RRC recovery complete message to a network device, the network device sends an RRC reconfiguration message to the terminal device, and the terminal device receives the RRC reconfiguration message sent by the network device, where the RRC reconfiguration message carries first configuration information, and the first configuration information is used to determine configuration information of the dedicated downlink BWP.
(III) case III
After entering the RRC connection state, the terminal equipment sends the identification information of the MBS service to the network equipment through the RRC message.
In one scenario, the MBS service is a desired MBS service or a receiving MBS service of the terminal equipment in an RRC inactive state, before the terminal equipment enters an RRC connection state, the terminal equipment sends an RRC restoration request message to the network equipment, the network equipment receives the RRC restoration request message sent by the terminal equipment, the network equipment sends an RRC restoration message to the terminal equipment, and the terminal equipment receives the RRC restoration message sent by the network equipment and then enters the RRC connection state. After entering the RRC connection state, the terminal equipment sends the identification information of the MBS service to the network equipment through an RRC recovery completion message.
In the above solution, optionally, the terminal device may send first indication information to the network device, where the first indication information is used to indicate whether the terminal device is receiving the broadcast MBS service.
In an alternative manner, the RRC restoration request message is used to determine first indication information, where the first indication information is used to indicate whether the terminal device is receiving the broadcast MBS service. Here, the implementation of the first indication information may be as follows:
The RRC recovery request message carries the first indication information in the mode I), wherein the value of the idle bit in the RRC recovery request message is used for representing the first indication information.
And II) the RRC restoration request message carries the first indication information, wherein the value of the restoration reason in the RRC restoration request message is used for representing the first indication information.
Mode III) the value of the logic channel identifier of the CCCH corresponding to the RRC resume request message is used to characterize the first indication information.
Here, the logical channel identifier of the CCCH is carried in a packet header corresponding to the RRC restoration request message in the MAC TB.
In another alternative, before the terminal device sends the RRC resume request message to the network device, the method further includes that the terminal device sends MSG1 or MSGA to the network device, the network device receives MSG1 or MSGA sent by the terminal device, and the MSG1 or MSGA is used for determining first indication information, where the first indication information is used for indicating at least one of whether the terminal device is receiving broadcast MBS service, and identification information of the MBS service that the terminal device is receiving.
In the above scheme, the preamble and/or the RO resource corresponding to the MSG1 or MSGA has an association relationship with whether the terminal equipment is receiving the broadcast MBS service, and/or the preamble and/or the RO resource corresponding to the MSG1 or MSGA has an association relationship with the identification information of the MBS service received by the terminal equipment. Here, optionally, the association relationship is configured by a system broadcast message. Based on this, the terminal device determines the preamble and/or RO resource corresponding to the MSG1 or MSGA according to whether the broadcast MBS service is being received and/or the identification information of the received MBS service.
In the foregoing scenario, optionally, the RRC recovery message carries second configuration information, where the second configuration information is used to determine BWP configuration information of the PCell, and the bandwidth of the first active downlink BWP of the PCell includes the bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell. Here, the bandwidth of the MBS BWP of the PCell is determined by the network device according to the bandwidth of the MBS BWP corresponding to the MBS service identifier indicated by the terminal device. Specifically, the bandwidth of the MBS BWP of the PCell is the bandwidth of the MBS BWP corresponding to the MBS service identifier indicated by the terminal device.
In the embodiment of the present application, after a terminal device sends an RRC recovery complete message to a network device, the network device sends an RRC reconfiguration message to the terminal device, and the terminal device receives the RRC reconfiguration message sent by the network device, where the RRC reconfiguration message carries first configuration information, and the first configuration information is used to determine configuration information of the dedicated downlink BWP.
(IV) case four
Before the terminal equipment enters the RRC connection state, the network equipment sends the identification information of the MBS service to the network equipment through the MSG1 or MSGA, and the network equipment receives the identification information of the MBS service sent by the terminal equipment through the MSG1 or MSGA.
Specifically, the MSG1 or MSGA is configured to determine first indication information, where the first indication information is configured to indicate at least one of:
whether the terminal equipment is receiving the broadcast MBS service;
the terminal equipment receives the identification information of the MBS service.
In the above scheme, the preamble and/or the RO resource corresponding to the MSG1 or MSGA has an association relationship with whether the terminal equipment is receiving the broadcast MBS service, and/or the preamble and/or the RO resource corresponding to the MSG1 or MSGA has an association relationship with the identification information of the MBS service received by the terminal equipment. Here, optionally, the association relationship is configured by a system broadcast message. Based on this, the terminal device determines the preamble and/or RO resource corresponding to the MSG1 or MSGA according to whether the broadcast MBS service is being received and/or the identification information of the received MBS service.
In the above solution, for MSGA including MSG1 and Payload (Payload is carried in PUSCH), the first indication information may be an implicit indication by a preamble of MSG1 and/or RO resource, or the first indication information may also carry an explicit indication in Payload.
In one scenario, the MBS service is a desired MBS service or a receiving MBS service in an RRC inactive state of the terminal equipment, before the terminal equipment enters an RRC connection state, the terminal equipment sends identification information of the MBS service to the network equipment through MSG1 or MSGA, the terminal equipment receives MSG2 sent by the network equipment, then the terminal equipment sends an RRC recovery request message to the network equipment, the network equipment receives the RRC recovery request message sent by the terminal equipment, the network equipment sends an RRC recovery message to the terminal equipment, the terminal equipment receives the RRC recovery message sent by the network equipment, the RRC recovery message carries first configuration information, the first configuration information is used for determining configuration information of the special downlink BWP, and then the terminal equipment enters the RRC connection state. After entering the RRC connection state, the terminal equipment sends an RRC recovery completion message to the network equipment.
For the schemes described in the first to fourth cases, the network device may obtain the identification information of the MBS service sent by the terminal device, and the network device may configure a dedicated downlink BWP for the terminal device and/or select a target cell to be switched for the terminal device according to the identification information of the MBS service.
For handover, the identification information of the MBS service is used for the network device to select a cell supporting the MBS service indicated by the identification information of the MBS service as a target cell for handover, and specifically, the network device selects, according to the identification information of the MBS service, a cell supporting the MBS service indicated by the identification information of the MBS service as a target cell for handover. Further, optionally, before the network device selects a cell supporting the MBS service indicated by the identification information of the MBS service as the target cell for handover, the cell interacts with its neighboring cell with the identification information about the MBS service supported by each cell or the MBS service being transmitted.
Wherein, for the special downlink BWP, the configuration information of the special downlink BWP is embodied by the first configuration information in the above scheme. The first configuration information in the schemes described in the first to fourth cases is described below.
A) In an alternative manner, the first configuration information is used to determine configuration information of a dedicated downlink BWP of the PCell, where the bandwidth of the dedicated downlink BWP of the PCell includes a bandwidth of an initial downlink BWP of the PCell and/or a bandwidth of an MBS BWP of the PCell.
B) In another alternative, the first configuration information is used to determine configuration information of a dedicated downlink BWP of the SCell, where the bandwidth of the dedicated downlink BWP of the SCell comprises a bandwidth of an initial downlink BWP of the SCell and/or a bandwidth of an MBS BWP of the SCell.
Optionally, the network device sends second indication information to the terminal device, and the terminal device receives the second indication information sent by the network device, where the second indication information is used to instruct the terminal device to receive the broadcast MBS service on the SCell.
In one example, if the terminal device receives a broadcast MBS service on the SCell, the SCell is in an active state or in an active state with non-dormant non-dormancy behavior.
In one example, if the terminal device receives the broadcasted MBS service on the SCell, and the SCell is in a deactivated state or in an activated state with sleep dormancy, the terminal device has the following actions of monitoring a PDCCH scrambled by a G-RNTI and receiving a PDSCH corresponding to the PDCCH on the SCell, and not monitoring a PDCCH scrambled by a C-RNTI and not receiving a PDSCH corresponding to the PDCCH on the SCell. Further, the bandwidth of the first activated downlink BWP of the SCell may include the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
It should be noted that, the "identification information of MBS service" described in the above scheme of the present application may refer to identification information of one MBS service or identification information of a plurality of MBS services (i.e. MBS identification information list).
The technical solution of the embodiment of the present application is illustrated below with reference to a specific application example, and it should be noted that in the following application example, a terminal device is taken as an example of UE, and a network device is taken as an example of gNB.
Application example one
An application example corresponds to the first case in the above scheme, referring to fig. 3, fig. 3 is a flow chart diagram of a method for indicating MBS service provided by an embodiment of the present application, as shown in fig. 3, where the method for indicating MBS service includes the following steps:
step 301, the ue is in RRC idle state and is receiving the broadcast MBS service.
Here, the identification information of the broadcast MBS service is TMGI-1.
Step 302 the ue sends an RRC setup request (RRCSetupRequest) message to the gNB.
Here, the UE transmits an RRC setup request message to the gNB through SRB 0.
Step 303, gNB sends RRC setup (RRCSetup) message to UE.
Here, the gNB sends an RRC setup message to the UE through SRB 1.
Step 304 the ue enters RRC connected state.
Step 305, the UE reports identification information of MBS services interested by the UE or being received to the gNB.
Here, the identification information of the MBS service the UE is interested in or receiving is, for example, TMGI-1.
It should be noted that, the identification information of the MBS service that the UE is interested in or receiving is not limited to one TMGI, but may be one TMGI list.
In the embodiment of the application, the UE reports the identification information of the MBS service interested by the UE or being received to the gNB in the following ways:
mode 1-1 the UE reports the identification information of MBS service the UE is interested in or is receiving through RRC setup complete (RRCSetupComplete) message. Here, the RRC setup complete message (i.e., MSG 5) is transmitted through SRB 1.
Mode 1-2 the UE reports the identity information of MBS services that the UE is interested in or is receiving through a new RRC message. Here, the new RRC message is, for example, an MBS interest indication (MBSInterestingIndication) message.
It should be noted that, the foregoing modes 1-1 and 1-2 do not take security into consideration, that is, the RRC message carrying the identification information of the MBS service is not processed safely, so that the foregoing mode 1-1 or 1-2 may be used to report the identification information of the MBS service without security problems.
Mode 2-1 the UE reports the identification information of MBS service the UE is interested in or is receiving through a security activation completion (SecurityModeComplete) message.
Mode 2-2 the UE reports the identification information of MBS service the UE is interested in or is receiving through the UE assistance information (UEAssistanceInformation) message.
Mode 2-3 the UE reports the identification information of MBS service the UE is interested in or is receiving through a new RRC message. Here, the new RRC message is, for example, an MBS interest indication (MBSInterestingIndication) message.
It should be noted that, the foregoing manner 2-1, manner 2-2, and manner 2-3 take security into consideration, that is, the RRC message carrying the identification information of the MBS service is securely processed (that is, the RRC message is not reported until the AS layer is securely activated), so that the identification information of the MBS service may be reported using the foregoing manner 2-1, manner 2-2, or manner 2-3 without or with security problems.
Step 306, the gNB sends an RRC reconfiguration (RRCReconfiguration) message to the UE, carrying configuration information of the dedicated downlink BWP.
Here, after the gNB acquires the identification information about the MBS service that the UE is interested in or receiving, the configuration information of the dedicated downlink BWP is configured through the RRC reconfiguration message, specifically:
The gNB, when configuring the dedicated DL BWP of the PCell to the UE, the bandwidth of the dedicated DL BWP includes the bandwidth of the initial DL BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell. Or alternatively
The gNB may instruct the UE to receive MBS traffic on a certain SCell, the bandwidth of the dedicated DL BWP configuring the SCell comprising the bandwidth of the initial DL BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
Further, if the UE receives the broadcasted MBS service on the SCell, the SCell cannot be deactivated and dormant BWP cannot be configured (i.e., the SCell cannot be in an active state with dormant behavior). Or if the UE receives the broadcasted MBS service on the SCell, if the SCell is deactivated, or if dormant BWP is configured and dormant BWP is activated, the UE only allows the G-RNTI scrambled PDCCH and corresponding PDSCH reception to continue listening in that cell, but cannot receive the C-RNTI scrambled PDCCH and corresponding PDSCH reception. And the bandwidth of the first activated DL BWP of the SCell must include the bandwidth of the initial DL BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
Step 307 the ue sends an RRC reconfiguration complete (RRCReconfigurationComplete) message to the gNB.
Here, the UE transmits an RRC reconfiguration complete message to the gNB through SRB 1.
Application example two
The second application example corresponds to the second case in the above solution, referring to fig. 4, fig. 4 is a flowchart of a third flowchart of an indication method of MBS service provided by an embodiment of the present application, as shown in fig. 4, where the indication method of MBS service includes the following steps:
Step 401, the UE is in RRC inactive state, and the UE is receiving the broadcasted MBS service.
Here, the identifier of the broadcast MBS service is TMGI-1.
In step 402, the UE sends an RRC resume request (RRCResumeRequest) message to the target gNB, where the 1-bit indication information is used to indicate whether the UE is receiving MBS service.
Here, the UE transmits an RRC resume request message to the target gNB through SRB 0.
Here, the RRC recovery request message is used to determine 1-bit indication information, and the 1-bit indication information is used to indicate whether the UE is receiving the MBS service. For example, a value of 1 for the 1-bit indication information indicates that the UE is receiving MBS service, and a value of 0 for the 1-bit indication information indicates that the UE is not receiving MBS service. The implementation of the 1-bit indication information is as follows:
1) The UE carries 1-bit indication information in the RRC resume request message, for example, indicates this 1-bit indication information with an idle bit (spark bit) in the RRC resume request message.
2) The UE indicates, through the LCID of the CCCH corresponding to the RRC connection resume request message, that the UE is receiving the broadcast MBS service, for example, defines a new LCID for the CCCH, which is used to indicate that the UE is receiving the broadcast MBS service when the UE initiates RRC connection resume. The LCID indicated in the header corresponding to the RLC PDU of the RRC resume request message at this time is the LCID newly defined above.
3) The UE carries 1 bit of indication information in the RRC resume request message, for example, indicates that the UE is receiving the broadcast MBS service by using the value of the resume reason (resume casue) in the RRC resume request message.
Step 403, the target gNB sends an RRC recovery message to the UE, wherein the RRC recovery message carries configuration information of BWP of the PCell.
Here, the target gNB transmits an RRC resume message to the UE through SRB 1.
Here, after acquiring the 1-bit indication information regarding the MBS service in which the UE is receiving broadcast from the RRC restoration request message transmitted by the UE, the target gNB configures the BWP of the PCell to the UE through the RRC restoration (RRCResume) message, specifically, the bandwidth of the first activated DL BWP of the PCell includes the bandwidth of the initial DL BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell.
It should be noted that, before receiving the 1-bit indication information of the MBS service of interest or being received, which is reported by the UE, the network side does not trigger the UE to perform the BWP handover operation, at least for the PCell.
Step 404 the ue enters RRC connected state.
Step 405, the UE reports the identification information of the MBS service the UE is interested in or is receiving through RRC restoration complete (RRCResumeComplete) message.
Here, the UE transmits an RRC restoration complete message through SRB 1.
Step 406, the gNB sends an RRC reconfiguration (RRCReconfiguration) message to the UE, carrying configuration information of the dedicated downlink BWP.
Here, the gNB sends an RRC reconfiguration message to the UE through SRB 1.
Here, after the gNB acquires the identification information about the MBS service that the UE is interested in or receiving, the configuration information of the dedicated downlink BWP is configured through the RRC reconfiguration message, specifically:
The gNB, when configuring the dedicated DL BWP of the PCell to the UE, the bandwidth of the dedicated DL BWP includes the bandwidth of the initial DL BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell. Or alternatively
The gNB may instruct the UE to receive MBS traffic on a certain SCell, the bandwidth of the dedicated DL BWP configuring the SCell comprising the bandwidth of the initial DL BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
Further, if the UE receives the broadcasted MBS service on the SCell, the SCell cannot be deactivated and dormant BWP cannot be configured (i.e., the SCell cannot be in an active state with dormant behavior). Or if the UE receives the broadcasted MBS service on the SCell, if the SCell is deactivated, or if dormant BWP is configured and dormant BWP is activated, the UE only allows the G-RNTI scrambled PDCCH and corresponding PDSCH reception to continue listening in that cell, but cannot receive the C-RNTI scrambled PDCCH and corresponding PDSCH reception. And the bandwidth of the first activated DL BWP of the SCell must include the bandwidth of the initial DL BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
Step 407 the ue sends an RRC reconfiguration complete (RRCReconfigurationComplete) message to the gNB.
Here, the UE transmits an RRC reconfiguration complete message to the gNB through SRB 1.
Application example three
The third application example corresponds to the third case in the above solution, referring to fig. 5, fig. 5 is a flow chart diagram of a method for indicating MBS service provided by an embodiment of the present application, as shown in fig. 5, where the method for indicating MBS service includes the following steps:
in step 501, the UE is in an RRC inactive state, and the UE is receiving a broadcast MBS service.
Here, the identifier of the broadcast MBS service is TMGI-1.
Step 502, the UE receives a system broadcast message sent by the target gNB and configures a first association relationship and/or a second association relationship.
Here, the "association relationship" may also be referred to as "mapping relationship (mapping relationship)".
Here, the first association relationship is an association relationship between preamble and/or RO (rach occasion) resources and whether MBS service is ongoing. The second association relationship is the association relationship between the preamble and/or RO (rach occasion) resources and the MBS service identifier (i.e. the identifier information of the MBS service).
It should be noted that, the step 501 and the step 502 are not sequential.
Step 503, the ue sends MSG1 to the target gNB.
Here, the UE selects a corresponding preamble and/or RO resource to transmit MSG1 according to whether the MBS service is currently being received and/or identification information of the received MBS service.
In step 504, the target gNB determines whether the UE is receiving MBS service and/or identification information of the receiving MBS service according to the preamble and/or RO resource of the MSG 1.
Step 505, the target gNB sends MSG2 to the UE.
Step 506 the ue sends an RRC resume request (RRCResumeRequest) message to the target gNB.
Here, the UE transmits an RRC resume request message to the target gNB through SRB 0.
In step 507, the target gNB sends an RRC recovery message to the UE, carrying configuration information of BWP of the PCell.
Here, the target gNB transmits an RRC resume message to the UE through SRB 1.
Here, after acquiring the 1-bit indication information regarding the MBS service in which the UE is receiving broadcast from the RRC restoration request message transmitted by the UE, the target gNB configures the BWP of the PCell to the UE through the RRC restoration (RRCResume) message, specifically, the bandwidth of the first activated DL BWP of the PCell includes the bandwidth of the initial DL BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell.
It should be noted that, before receiving the 1-bit indication information of the MBS service of interest or being received, which is reported by the UE, the network side does not trigger the UE to perform the BWP handover operation, at least for the PCell.
Step 508 the ue enters RRC connected state.
Step 509, the UE reports the identification information of the MBS service that the UE is interested in or is receiving through RRC recovery complete (RRCResumeComplete) message.
Here, the UE transmits an RRC restoration complete message through SRB 1.
Step 510, the gNB sends an RRC reconfiguration (RRCReconfiguration) message to the UE, carrying configuration information of the dedicated downstream BWP.
Here, the gNB sends an RRC reconfiguration message to the UE through SRB 1.
Here, after the gNB acquires the identification information about the MBS service that the UE is interested in or receiving, the configuration information of the dedicated downlink BWP is configured through the RRC reconfiguration message, specifically:
The gNB, when configuring the dedicated DL BWP of the PCell to the UE, the bandwidth of the dedicated DL BWP includes the bandwidth of the initial DL BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell. Or alternatively
The gNB may instruct the UE to receive MBS traffic on a certain SCell, the bandwidth of the dedicated DL BWP configuring the SCell comprising the bandwidth of the initial DL BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
Further, if the UE receives the broadcasted MBS service on the SCell, the SCell cannot be deactivated and dormant BWP cannot be configured (i.e., the SCell cannot be in an active state with dormant behavior). Or if the UE receives the broadcasted MBS service on the SCell, if the SCell is deactivated, or if dormant BWP is configured and dormant BWP is activated, the UE only allows the G-RNTI scrambled PDCCH and corresponding PDSCH reception to continue listening in that cell, but cannot receive the C-RNTI scrambled PDCCH and corresponding PDSCH reception. And the bandwidth of the first activated DL BWP of the SCell must include the bandwidth of the initial DL BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
Step 511 the ue sends an RRC reconfiguration complete (RRCReconfigurationComplete) message to the gNB.
Here, the UE transmits an RRC reconfiguration complete message to the gNB through SRB 1.
Application example four
The fourth application example corresponds to the fourth case in the above solution, referring to fig. 6, fig. 6 is a flow chart diagram of a method for indicating an MBS service provided by an embodiment of the present application, as shown in fig. 6, where the method for indicating an MBS service includes the following steps:
In step 601, the UE is in an RRC inactive state, and the UE is receiving the broadcasted MBS service.
Here, the identifier of the broadcast MBS service is TMGI-1.
Step 602, the UE receives a system broadcast message sent by the target gNB and configures a first association relationship and/or a second association relationship.
Here, the "association relationship" may also be referred to as "mapping relationship (mapping relationship)".
Here, the first association relationship is an association relationship between preamble and/or RO (rach occasion) resources and whether MBS service is ongoing. The second association relationship is the association relationship between the preamble and/or RO (rach occasion) resources and the MBS service identifier (i.e. the identifier information of the MBS service).
It should be noted that, the step 501 and the step 502 are not sequential.
Step 603, the ue sends MSG1 to the target gNB.
Here, the UE selects a corresponding preamble and/or RO resource to transmit MSG1 according to whether the MBS service is currently being received and/or identification information of the received MBS service.
In step 604, the target gNB determines whether the UE is receiving the MBS service and/or the identification information of the MBS service being received according to the preamble and/or the RO resource of the MSG 1.
Step 605, the target gNB sends MSG2 to the UE.
Step 606 the ue sends an RRC resume request (RRCResumeRequest) message to the target gNB.
Here, the UE transmits an RRC resume request message to the target gNB through SRB 0.
In step 607, the target gNB sends an RRC recovery message to the UE, carrying configuration information of the dedicated downlink BWP.
Here, the target gNB transmits an RRC resume message to the UE through SRB 1.
Here, after the gNB acquires the identification information about the MBS service that the UE is interested in or is receiving, the configuration information of the dedicated downlink BWP is configured through the RRC restore message, specifically:
The gNB, when configuring the dedicated DL BWP of the PCell to the UE, the bandwidth of the dedicated DL BWP includes the bandwidth of the initial DL BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell. Or alternatively
The gNB may instruct the UE to receive MBS traffic on a certain SCell, the bandwidth of the dedicated DL BWP configuring the SCell comprising the bandwidth of the initial DL BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
Further, if the UE receives the broadcasted MBS service on the SCell, the SCell cannot be deactivated and dormant BWP cannot be configured (i.e., the SCell cannot be in an active state with dormant behavior). Or if the UE receives the broadcasted MBS service on the SCell, if the SCell is deactivated, or if dormant BWP is configured and dormant BWP is activated, the UE only allows the G-RNTI scrambled PDCCH and corresponding PDSCH reception to continue listening in that cell, but cannot receive the C-RNTI scrambled PDCCH and corresponding PDSCH reception. And the bandwidth of the first activated DL BWP of the SCell must include the bandwidth of the initial DL BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
Step 608 the ue enters RRC connected state.
Step 609 the ue sends an RRC resume complete (RRCResumeComplete) message.
Here, the UE transmits an RRC restoration complete message through SRB 1.
Step 610 the gNB sends an RRC reconfiguration (RRCReconfiguration) message to the UE,
Step 611. The ue sends an RRC reconfiguration complete (RRCReconfigurationComplete) message to the gNB.
Here, the UE transmits an RRC reconfiguration complete message to the gNB through SRB 1.
Fig. 7 is a schematic diagram of the structural composition of an indication device for MBS service provided in an embodiment of the present application, which is applied to a terminal device, as shown in fig. 7, where the indication device for MBS service includes:
a communication unit 701, configured to send identification information of an MBS service to a network device, where the MBS service is an MBS service expected by the terminal device or an MBS service being received;
The identification information of the MBS service is used for configuring the special downlink BWP of the terminal equipment and/or the identification information of the MBS service is used for determining a target cell to be switched by the terminal equipment.
In an alternative manner, the communication unit 701 is configured to send identification information of an MBS service to the network device through a first RRC message, where the first RRC message is an RRC message that is not subjected to security processing.
In an alternative way, the first RRC message is an RRC setup complete message, or
The first RRC message is an MBS indication message.
In an alternative manner, the communication unit 701 is configured to send the identification information of the MBS service to the network device through a second RRC message, where the second RRC message is a RRC message that is subjected to security processing.
In an alternative way, the second RRC message is a security activation complete message, or
The second RRC message is a UE assistance information UEAssistanceInformation message, or
The second RRC message is an MBS indication message.
In an alternative manner, the MBS service is a desired MBS service or a receiving MBS service in an RRC idle state of the terminal device;
the communication unit 701 is further configured to send an RRC establishment request message to the network device, and receive the RRC establishment message sent by the network device.
In an alternative manner, the MBS service is a desired MBS service or a receiving MBS service in an RRC inactive state of the terminal device;
The communication unit 701 is further configured to send an RRC restoration request message to the network device, where the RRC restoration process is retracted to an RRC establishment process, and receive an RRC establishment message sent by the network device.
In an alternative manner, the communication unit 701 is configured to send, to the network device, identification information of an MBS service through an RRC restoration complete message.
In an optional manner, the communication unit 701 is further configured to send an RRC restoration request message to the network device, and receive an RRC restoration message sent by the network device.
In an alternative manner, the RRC restoration request message is used to determine first indication information, where the first indication information is used to indicate whether the terminal device is receiving the broadcast MBS service.
In an alternative manner, the RRC restoration request message carries the first indication information, wherein,
The value of the idle bit in the RRC recovery request message is used for representing the first indication information, or
And the value of the recovery reason in the RRC recovery request message is used for representing the first indication information.
In an optional manner, the value of the logic channel identifier of the CCCH corresponding to the RRC resume request message is used to characterize the first indication information.
In an alternative manner, the logical channel identifier of the CCCH is carried in a packet header corresponding to the RRC restoration request message in the MAC TB.
In an alternative manner, the communication unit 701 is further configured to send MSG1 or MSGA to the network device, where the MSG1 or MSGA is configured to determine first indication information, where the first indication information is configured to indicate at least one of:
whether the terminal equipment is receiving the broadcast MBS service;
the terminal equipment receives the identification information of the MBS service.
In an alternative manner, the RRC recovery message carries second configuration information, where the second configuration information is used to determine BWP configuration information of the PCell, and the bandwidth of the first active downlink BWP of the PCell includes the bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell.
In an alternative manner, the bandwidth of the MBS BWP of the PCell is determined by the network device according to the bandwidth of the MBS BWP corresponding to the MBS service identifier indicated by the terminal device.
In an optional manner, the communication unit 701 is further configured to receive an RRC reconfiguration message sent by the network device, where the RRC reconfiguration message carries first configuration information, and the first configuration information is used to determine configuration information of the dedicated downlink BWP.
In an alternative manner, the communication unit 701 is configured to send, to the network device, identification information of an MBS service through MSG1 or MSGA.
In an alternative manner, the MSG1 or MSGA is configured to determine first indication information, where the first indication information is configured to indicate at least one of:
whether the terminal equipment is receiving the broadcast MBS service;
the terminal equipment receives the identification information of the MBS service.
In an optional manner, the communication unit 701 is further configured to send an RRC restoration request message to the network device, and receive an RRC restoration message sent by the network device, where the RRC restoration message carries first configuration information, and the first configuration information is used to determine configuration information of the dedicated downlink BWP.
In an alternative manner, the preamble and/or RO resource corresponding to the MSG1 or MSGA has an association relationship with whether the terminal device is receiving the broadcast MBS service, and/or,
And the lead code and/or RO resource corresponding to the MSG1 or MSGA has an association relation with the identification information of the MBS service received by the terminal equipment.
In an alternative manner, the association is configured by a system broadcast message.
In an alternative, the apparatus further comprises:
A determining unit 702, configured to determine the preamble and/or RO resource corresponding to the MSG1 or MSGA according to whether the broadcast MBS service is being received and/or the identification information of the received MBS service.
In an alternative manner, the first configuration information is used to determine configuration information of a dedicated downlink BWP of the PCell, where the bandwidth of the dedicated downlink BWP of the PCell includes a bandwidth of an initial downlink BWP of the PCell and/or a bandwidth of an MBS BWP of the PCell.
In an alternative manner, the first configuration information is used to determine configuration information of a dedicated downlink BWP of the SCell, where the bandwidth of the dedicated downlink BWP of the SCell includes a bandwidth of an initial downlink BWP of the SCell and/or a bandwidth of an MBS BWP of the SCell.
In an alternative manner, the communication unit 701 is further configured to receive second indication information sent by the network device, where the second indication information is used to instruct the terminal device to receive the broadcast MBS service on the SCell.
In an alternative manner, if the terminal device receives the broadcast MBS service on the SCell, the SCell is in an active state or in an active state with non-dormant non-dormancy behavior.
In an alternative manner, if the terminal device receives the broadcast MBS service on the SCell, and the SCell is in a deactivated state or in an activated state with sleep dormancy, the terminal device has the following actions:
monitoring a PDCCH scrambled by the G-RNTI on the SCell and receiving a PDSCH corresponding to the PDCCH;
And not monitoring the PDCCH scrambled by the C-RNTI and not receiving the PDSCH corresponding to the PDCCH on the SCell.
In an alternative manner, the bandwidth of the first activated downlink BWP of the SCell comprises the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
In an optional manner, the identifying information of the MBS service is used by the network device to select a target cell to be switched for the terminal device, including:
The identification information of the MBS service is used for the network equipment to select a cell supporting the MBS service indicated by the identification information of the MBS service as a target cell for switching.
In an alternative manner, before the network device selects a cell supporting the MBS service indicated by the identification information of the MBS service as a target cell for handover, the cell interacts with its neighbor with identification information about the MBS service supported by each cell or the MBS service being transmitted.
It should be understood by those skilled in the art that the description of the indication device for MBS service according to the embodiment of the present application may be understood by referring to the description of the indication method for MBS service according to the embodiment of the present application.
Fig. 8 is a schematic diagram ii of the structural composition of an indication device for MBS service provided in an embodiment of the present application, which is applied to a network device, as shown in fig. 8, where the indication device for MBS service includes:
A communication unit 801, configured to receive identification information of an MBS service sent by a terminal device, where the MBS service is an MBS service expected by the terminal device or an MBS service being received;
the network device is configured with a dedicated downlink BWP for the terminal device and/or the identification information of the MBS service is used for the network device to select a target cell to be switched for the terminal device.
In an alternative manner, the communication unit 801 is configured to receive identification information of an MBS service sent by the terminal device through a first RRC message, where the first RRC message is an RRC message that is not subjected to security processing.
In an alternative way, the first RRC message is an RRC setup complete message, or
The first RRC message is an MBS indication message.
In an alternative manner, the communication unit 801 is configured to receive identification information of an MBS service sent by the terminal device through a second RRC message, where the second RRC message is a RRC message subjected to security processing.
In an alternative way, the second RRC message is a security activation complete message, or
The second RRC message is a UE assistance information UEAssistanceInformation message, or
The second RRC message is an MBS indication message.
In an alternative manner, the MBS service is a desired MBS service or a receiving MBS service in an RRC idle state of the terminal device;
The communication unit 801 is further configured to receive an RRC establishment request message sent by the terminal device, and send an RRC establishment message to the terminal device.
In an alternative manner, the MBS service is an expected MBS service or an MBS service being received by the terminal device in an RRC inactive state, and the communication unit 801 is further configured to receive an RRC resume request message sent by the terminal device, where an RRC resume process is returned to an RRC establishment process, and send an RRC establishment message to the terminal device.
In an alternative manner, the communication unit 801 is configured to receive identification information of an MBS service sent by the terminal device through an RRC resume complete message.
In an optional manner, the communication unit 801 is further configured to receive an RRC restoration request message sent by the terminal device, and send an RRC restoration message to the terminal device.
In an alternative manner, the RRC restoration request message is used to determine first indication information, where the first indication information is used to indicate whether the terminal device is receiving the broadcast MBS service.
In an alternative manner, the RRC restoration request message carries the first indication information, wherein,
The value of the idle bit in the RRC recovery request message is used for representing the first indication information, or
And the value of the recovery reason in the RRC recovery request message is used for representing the first indication information.
In an optional manner, the value of the logic channel identifier of the CCCH corresponding to the RRC resume request message is used to characterize the first indication information.
In an alternative manner, the logical channel identifier of the CCCH is carried in a packet header corresponding to the RRC restoration request message in the MAC TB.
In an alternative manner, the communication unit 801 is further configured to receive MSG1 or MSGA sent by the terminal device, where the MSG1 or MSGA is configured to determine first indication information, where the first indication information is used to indicate at least one of the following:
whether the terminal equipment is receiving the broadcast MBS service;
the terminal equipment receives the identification information of the MBS service.
In an alternative manner, the RRC recovery message carries second configuration information, where the second configuration information is used to determine BWP configuration information of the PCell, and the bandwidth of the first active downlink BWP of the PCell includes the bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell.
In an alternative manner, the bandwidth of the MBS BWP of the PCell is determined by the network device according to the bandwidth of the MBS BWP corresponding to the MBS service identifier indicated by the terminal device.
In an alternative manner, the communication unit 801 is further configured to send an RRC reconfiguration message to the terminal device, where the RRC reconfiguration message carries first configuration information, and the first configuration information is used to determine configuration information of the dedicated downlink BWP.
In an alternative manner, the communication unit 801 is configured to receive identification information of an MBS service sent by the terminal device through MSG1 or MSGA.
In an alternative manner, the MSG1 or MSGA is configured to determine first indication information, where the first indication information is configured to indicate at least one of:
whether the terminal equipment is receiving the broadcast MBS service;
the terminal equipment receives the identification information of the MBS service.
In an alternative manner, the communication unit 801 is further configured to receive an RRC restoration request message sent by the terminal device, and send an RRC restoration message to the terminal device, where the RRC restoration message carries first configuration information, and the first configuration information is used to determine configuration information of the dedicated downlink BWP.
In an alternative manner, the preamble and/or RO resource corresponding to the MSG1 or MSGA has an association relationship with whether the terminal device is receiving the broadcast MBS service, and/or,
And the lead code and/or RO resource corresponding to the MSG1 or MSGA has an association relation with the identification information of the MBS service received by the terminal equipment.
In an alternative manner, the association is configured by a system broadcast message.
In an alternative manner, the first configuration information is used to determine configuration information of a dedicated downlink BWP of the PCell, where the bandwidth of the dedicated downlink BWP of the PCell includes a bandwidth of an initial downlink BWP of the PCell and/or a bandwidth of an MBS BWP of the PCell.
In an alternative manner, the first configuration information is used to determine configuration information of a dedicated downlink BWP of the SCell, where the bandwidth of the dedicated downlink BWP of the SCell includes a bandwidth of an initial downlink BWP of the SCell and/or a bandwidth of an MBS BWP of the SCell.
In an alternative manner, the communication unit 801 is further configured to send second indication information to the terminal device, where the second indication information is used to instruct the terminal device to receive the broadcast MBS service on the SCell.
In an alternative manner, if the terminal device receives the broadcast MBS service on the SCell, the SCell is in an active state or in an active state with non-dormancy behavior.
In an alternative manner, if the terminal device receives the broadcast MBS service on the SCell, and the SCell is in a deactivated state or in an activated state with dormancy actions, the terminal device has the following actions:
monitoring a PDCCH scrambled by the G-RNTI on the SCell and receiving a PDSCH corresponding to the PDCCH;
And not monitoring the PDCCH scrambled by the C-RNTI and not receiving the PDSCH corresponding to the PDCCH on the SCell.
In an alternative manner, the bandwidth of the first activated downlink BWP of the SCell comprises the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
In an alternative, the apparatus further comprises:
And a selecting unit 802, configured to select, according to the identification information of the MBS service, a cell supporting the MBS service indicated by the identification information of the MBS service as a target cell for handover.
In an alternative manner, before the network device selects a cell supporting the MBS service indicated by the identification information of the MBS service as a target cell for handover, the cell interacts with its neighbor with identification information about the MBS service supported by each cell or the MBS service being transmitted.
It should be understood by those skilled in the art that the description of the indication device for MBS service according to the embodiment of the present application may be understood by referring to the description of the indication method for MBS service according to the embodiment of the present application.
Fig. 9 is a schematic block diagram of a communication device 900 according to an embodiment of the present application. The communication device may be a terminal device or a network device, and the communication device 900 shown in fig. 9 includes a processor 910, where the processor 910 may call and execute a computer program from a memory to implement a method according to an embodiment of the present application.
Optionally, as shown in fig. 9, the communication device 900 may also include a memory 920. Wherein the processor 910 may invoke and run a computer program from the memory 920 to implement the method in the embodiments of the present application.
Wherein the memory 920 may be a separate device from the processor 910 or may be integrated in the processor 910.
Optionally, as shown in fig. 9, the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.
Wherein transceiver 930 may include a transmitter and a receiver. Transceiver 930 may further include antennas, the number of which may be one or more.
Optionally, the communication device 900 may be specifically a network device in the embodiment of the present application, and the communication device 900 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the communication device 900 may be specifically a mobile terminal/terminal device according to an embodiment of the present application, and the communication device 900 may implement corresponding processes implemented by the mobile terminal/terminal device in each method according to the embodiment of the present application, which are not described herein for brevity.
Fig. 10 is a schematic structural view of a chip of an embodiment of the present application. The chip 1000 shown in fig. 10 includes a processor 1010, and the processor 1010 may 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. 10, the chip 1000 may further include a memory 1020. Wherein the processor 1010 may call and run a computer program from the memory 1020 to implement the methods in embodiments of the present application.
The memory 1020 may be a separate device from the processor 1010 or may be integrated into the processor 1010.
Optionally, the chip 1000 may also include an input interface 1030. The processor 1010 may control the input interface 1030 to communicate with other devices or chips, and in particular, may obtain information or data sent by the other devices or chips.
Optionally, the chip 1000 may further include an output interface 1040. Wherein the processor 1010 may control the output interface 1040 to communicate with other devices or chips, and in particular, may 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 flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the chip may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.
Fig. 11 is a schematic block diagram of a communication system 1100 provided by an embodiment of the present application. As shown in fig. 11, the communication system 1100 includes a terminal device 1110 and a network device 1120.
The terminal device 1110 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1120 may be used to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.
It should be appreciated that the processor of an embodiment 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 implemented by integrated logic circuits of hardware in a processor or instructions in software form. The Processor may be a general purpose Processor, a digital signal Processor (DIGITAL SIGNAL Processor, DSP), an Application SPECIFIC INTEGRATED Circuit (ASIC), an off-the-shelf programmable gate array (Field Programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks 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 embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate Synchronous dynamic random access memory (Double DATA RATE SDRAM, DDR SDRAM), enhanced Synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and Direct memory bus 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 appreciated that the above memory is exemplary and not limiting, and for example, the memory in the embodiments of the present application may be static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (double DATA RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous connection dynamic random access memory (SYNCH LINK DRAM, SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
The embodiment of the application also provides a computer readable storage medium for storing a computer program.
Optionally, the computer readable storage medium may be applied to a network device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which is not described herein for brevity.
The embodiment of the application also provides a computer program product comprising computer program instructions.
Optionally, the computer program product may be applied to a network device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the network device in each method in the embodiment of the present application, which are not described herein for brevity.
Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which are not described herein for brevity.
The embodiment of the application also provides a computer program.
Optionally, the computer program may be applied to a network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein 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 solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. The storage medium includes a U disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.