A bearer configuration method and device, terminal equipment, and network equipment

Abstract

An embodiment of the present application provides a bearer configuration method and apparatus, a terminal device, and a network device. The method includes: the terminal device receives a bearer configuration instruction sent by the network device, and the bearer configuration instruction is used to configure SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and / or at least one MRB.

Description

[0001] This application is a divisional application of the PCT international patent application PCT / CN2021 / 091695 with an application date of April 30, 2021, which entered the Chinese national phase with Chinese patent application number 202180082804.9 and the invention name being "A bearer configuration method and device, terminal equipment, and network equipment." Technical Field

[0002] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a bearer configuration method and apparatus, terminal equipment, and network equipment. Background Art

[0003] The terminal device needs to enter the Radio Resource Control (RRC) connection state to receive unicast services. The mobility process in the RRC connection state is supported only when the terminal device is in the RRC connection state and there is a bearer for receiving unicast services.

[0004] With the introduction of Multimedia Broadcast Service (MBS), terminal devices receiving multicast MBS services also need to enter the RRC connection state. At this time, how to support mobility in the RRC connection state needs to be clarified. Summary of the invention

[0005] The embodiments of the present application provide a bearer configuration method and apparatus, terminal equipment, and network equipment.

[0006] The bearer configuration method provided in the embodiment of the present application includes:

[0007] The terminal device receives a bearer configuration instruction sent by a network device, and the bearer configuration instruction is used to configure a signaling radio bearer (SRB) 2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one data radio bearer (DRB) and / or at least one multicast radio bearer (MRB).

[0008] The bearer configuration method provided in the embodiment of the present application includes:

[0009] The network device sends a bearer configuration instruction to the terminal device, where the bearer configuration instruction is used to configure SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and / or at least one MRB.

[0010] The bearer configuration device provided in the embodiment of the present application is applied to a terminal device, and the device includes:

[0011] A receiving unit is used to receive a bearer configuration instruction sent by a network device, wherein the bearer configuration instruction is used to configure SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and / or at least one MRB.

[0012] The bearer configuration device provided in the embodiment of the present application is applied to a network device, and the device includes:

[0013] A sending unit is used to send a bearer configuration instruction to a terminal device, wherein the bearer configuration instruction is used to configure SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and / or at least one MRB.

[0014] The terminal device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned bearer configuration method.

[0015] The network device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned bearer configuration method.

[0016] The chip provided in the embodiment of the present application is used to implement the above-mentioned bearer configuration method.

[0017] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned bearer configuration method.

[0018] The computer-readable storage medium provided in the embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned bearer configuration method.

[0019] The computer program product provided in the embodiment of the present application includes computer program instructions, which enable a computer to execute the above-mentioned bearer configuration method.

[0020] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned bearer configuration method.

[0021] Through the above technical solution, the network device configures SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and / or at least one MRB, so that the terminal device can support the mobility process in the RRC connection state based on SRB2 and at least one data bearer. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0023] Figure 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

[0024] Figure 2 This is a transmission network architecture diagram of the MBS service provided in the embodiment of the present application;

[0025] Figure 3 It is a flowchart of a bearer configuration method provided in an embodiment of the present application;

[0026] Figure 4 This is a schematic diagram of the structure of the load-bearing configuration device provided in the embodiment of the present application. Figure 1 ;

[0027] Figure 5 This is a schematic diagram of the structure of the load-bearing configuration device provided in the embodiment of the present application. Figure 2 ;

[0028] Figure 6 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0029] Figure 7 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0030] Figure 8 It is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0031] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0032] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, 5G communication system or future communication system, etc.

[0033] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 1 As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal 120 (or referred to as a communication terminal, terminal). The network device 110 may provide communication coverage for a specific geographical area, and may communicate with terminals located within the coverage area. Optionally, the network device 110 may be an evolved base station (eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle-mounted 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.

[0034] The communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110. As used herein, "terminal" includes but is not limited to connecting via a wired line, such as via a Public Switched Telephone Networks (PSTN), a Digital Subscriber Line (DSL), a digital cable, a direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as, for a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and / or another terminal configured to receive / send communication signals; and / or an Internet of Things (IoT) device. A terminal configured to communicate via a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radiotelephones with data processing, fax, and data communications capabilities; PDAs that may include radiotelephones, pagers, Internet / Intranet access, Web browsers, notepads, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or palmtop receivers or other electronic devices that include radiotelephone transceivers. A terminal may refer to an access terminal, User Equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network, or a terminal in a future evolved PLMN, etc.

[0035] Optionally, the terminals 120 may perform device-to-device (D2D) communication.

[0036] Optionally, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0037] Figure 1 One network device and two terminals are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminals within its coverage area, which is not limited in the embodiments of the present application.

[0038] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0039] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal 120 with communication functions. The network device 110 and the terminal 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0040] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0041] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application are described below.

[0042] With the pursuit of speed, latency, high-speed mobility, energy efficiency and the diversity and complexity of services in future life, the Third Generation Partnership Project (3GPP) rd The 3rd Generation Partnership Project (3GPP) international standard organization has begun to develop 5G. The main application scenarios of 5G are: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC).

[0043] On the one hand, eMBB still aims at users to obtain multimedia content, services and data, and its demand is growing rapidly. On the other hand, since eMBB may be deployed in different scenarios, such as indoors, in urban areas, and in rural areas, its capabilities and requirements vary greatly, so it cannot be generalized and must be analyzed in detail in combination with specific deployment scenarios. Typical applications of URLLC include: industrial automation, power automation, remote medical operations (surgery), traffic safety, etc. Typical features of mMTC include: high connection density, small data volume, latency-insensitive services, low cost and long service life of modules, etc.

[0044] In the early days of NR deployment, complete NR coverage was difficult to obtain, so the typical network coverage was wide-area LTE coverage and NR island coverage. In addition, a large number of LTEs are deployed below 6GHz, and there is little spectrum below 6GHz available for 5G. Therefore, NR must study spectrum applications above 6GHz, but high-frequency bands have limited coverage and fast signal fading. At the same time, in order to protect mobile operators' early investments in LTE, a tight interworking working mode between LTE and NR was proposed.

[0045] RRC Status

[0046] In order to reduce air interface signaling and quickly restore wireless connections and data services, 5G defines a new Radio Resource Control (RRC) state, namely the RRC inactive (RRC_INACTIVE) state. This state is different from the RRC idle (RRC_IDLE) state and the RRC active (RRC_ACTIVE) state.

[0047] in,

[0048] 1) RRC_IDLE state (abbreviated as idle state): Mobility is based on cell selection and reselection of terminal equipment, paging is initiated by the core network (CN), and the paging area is configured by the CN. There is no terminal equipment context on the base station side, and there is no RRC connection.

[0049] 2) RRC_CONNECTED state (referred to as connected state): There is an RRC connection, and there is a terminal device context on the base station side and the terminal device side. The network side knows the location of the terminal device at the specific cell level. The mobility is the mobility controlled by the network side. Unicast data can be transmitted between the terminal device and the base station.

[0050] 3) RRC_INACTIVE state (abbreviated as inactive state): Mobility is based on cell selection reselection of the terminal device, there is a connection between CN-NR, the terminal device context exists on a certain base station, paging is triggered by RAN, and the paging area based on RAN is managed by RAN. The network side knows the location of the terminal device based on the paging area level of RAN.

[0051] MBMS

[0052] MBMS is a technology that transmits data from one data source to multiple terminal devices by sharing network resources. While providing multimedia services, this technology can effectively utilize network resources and achieve broadcast and multicast of multimedia services at a higher rate (such as 256kbps).

[0053] Since MBMS spectrum efficiency is low, it is not enough to effectively carry and support the operation of mobile TV services. Therefore, in LTE, 3GPP explicitly proposed to enhance the support capability for downlink high-speed MBMS services and determined the design requirements for the physical layer and air interface.

[0054] 3GPP R9 introduced evolved MBMS (eMBMS) into LTE. eMBMS proposed the concept of Single Frequency Network (SFN), namely Multimedia Broadcast multicast service Single Frequency Network (MBSFN). MBSFN uses a unified frequency to send service data in all cells at the same time, but synchronization between cells must be guaranteed. This method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the spectrum efficiency will also be greatly improved accordingly. eMBMS implements broadcast and multicast of services based on the IP multicast protocol.

[0055] In LTE or enhanced LTE (LTE-Advanced, LTE-A), MBMS has only a broadcast bearer mode, but no multicast bearer mode. In addition, the reception of MBMS services is applicable to terminal devices in an idle state or a connected state.

[0056] 3GPP R13 introduced the concept of Single Cell Point To Multipoint (SC-PTM), which is based on the MBMS network architecture.

[0057] MBMS introduces new logical channels, including Single Cell-Multicast Control Channel (SC-MCCH) and Single Cell-Multicast Transport Channel (SC-MTCH). SC-MCCH and SC-MTCH are mapped to Downlink Shared Channel (DL-SCH), and further, DL-SCH is mapped to Physical Downlink Shared Channel (PDSCH), where SC-MCCH and SC-MTCH are logical channels, DL-SCH is a transport channel, and PDSCH is a physical channel. SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat reQuest (HARQ) operation.

[0058] MBMS introduces a new type of System Information Block (SIB), namely SIB20. Specifically, the configuration information of SC-MCCH is transmitted through SIB20, and there is only one SC-MCCH in a cell. The configuration information of SC-MCCH includes: the modification period of SC-MCCH, the repetition period of SC-MCCH, and the radio frame and subframe for scheduling SC-MCCH. Further, 1) The boundary of the modification period of SC-MCCH satisfies SFN mod m = 0, where SFN represents the system frame number of the boundary, and m is the modification period of SC-MCCH configured in SIB20 (i.e., sc-mcch-ModificationPeriod). 2) The radio frame for scheduling 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 SC-MCCH, and mcch-Offset represents the offset of SC-MCCH. 3) The subframe for scheduling SC-MCCH is indicated by sc-mcch-Subframe.

[0059] SC-MCCH is scheduled through the Physical Downlink Control Channel (PDCCH). On the one hand, a new Radio Network Temporary Identity (RNTI), namely the Single Cell RNTI (SC-RNTI), is introduced to identify the PDCCH (such as SC-MCCHPDCCH) used to schedule SC-MCCH. Optionally, the SC-RNTI is fixed to FFFC. On the other hand, a new RNTI, namely the Single Cell Notification RNTI (SC-N-RNTI), is introduced to identify the PDCCH (such as the notification PDCCH) used to indicate the change notification of SC-MCCH. Optionally, the SC-N-RNTI is fixed to FFFB; further, one of the 8 bits of DCI 1C can be used to indicate the change notification. In LTE, the configuration information of SC-PTM is based on the SC-MCCH configured by SIB20, and then the SC-MCCH configures the SC-MTCH, which is used to transmit service data.

[0060] Specifically, SC-MCCH only transmits one message (i.e., SCPTMConfiguration), which is used to configure the configuration information of SC-PTM. The configuration information of SC-PTM includes: Temporary Mobile Group Identity (TMGI), session id, group RNTI (G-RNTI), discontinuous reception (DRX) configuration information, and SC-PTM service information of neighboring cells. It should be noted that SC-PTM in R13 does not support the robust header compression (ROHC) function.

[0061] The downlink discontinuous reception of SC-PTM is controlled by the following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.

[0062] When [(SFN*10)+subframe number]modulo(SC-MTCH-SchedulingCycle)=SC-MTCH-SchedulingOffset is satisfied, the timer onDurationTimerSCPTM is started;

[0063] When receiving downlink PDCCH scheduling, start the timer drx-InactivityTimerSCPTM;

[0064] Downlink SC-PTM services are received only when the timer onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running.

[0065] SC-PTM service continuity adopts the MBMS service continuity concept based on SIB15, namely the "SIB15+MBMSInterestIndication" mode. The service continuity of idle terminal devices is based on the concept of frequency priority.

[0066] It should be noted that, although the above solution is described using MBMS as an example, the description of "MBMS" can also be replaced by "MBS". The embodiment of the present application is described using MBS as an example, and the description of "MBS service" can also be replaced by "MBMS".

[0067] In the NR system, many scenarios need to support multicast and broadcast service requirements, such as in the Internet of Vehicles and the Industrial Internet. Therefore, it is necessary to introduce multicast and broadcast MBS services in NR. It should be noted that multicast MBS services refer to MBS services transmitted by multicast. Broadcast MBS services refer to MBS services transmitted by broadcast.

[0068] In the NR system, for multicast MBS services, the MBS services are sent to all terminal devices in a group. The terminal device receives multicast MBS services in the RRC connection state. The terminal device can receive multicast MBS service data through point-to-multipoint (PTM) or point-to-point (PTP). Among them, the MBS service data of the PTM mode is scrambled with the corresponding scheduling information through the G-RNTI configured on the network side, and the MBS service data of the PTP mode is scrambled with the corresponding scheduling information through the C-RNTI.

[0069] The MSB service is transmitted via multicast. In other words, the MSB service is a multicast type MBS service. Specifically, after the base station receives the MBS service sent by the core network from the shared tunnel (tunnel), it can send the MSB service to all terminal devices in a group through the air interface. Here, the base station can send the MSB service to all terminal devices in a group via the PTP method and / or the PTM method. For example: a group includes terminal device 1, terminal device 2 and terminal device 3. The base station can send the MBS service to terminal device 1 via the PTP method, send the MBS service to terminal device 2 via the PTP method, and send the MBS service to terminal device 3 via the PTP method; or, the base station can send the MBS service to terminal device 1 via the PTP method, and send the MBS service to terminal device 2 and terminal device 3 via the PTM method; or, the base station can send the MBS service to terminal device 1, terminal device 2 and terminal device 3 via the PTM method. Refer to Figure 2 A shared GTP tunnel is used between the core network and the base station to transmit MBS services, that is, both PTM and PTP MBS services share this GTP tunnel. The base station sends MBS service data to UE1 and UE2 in PTM mode, and sends MBS service data to UE3 in PTP mode.

[0070] For terminal devices that receive MBS services, they also receive other non-MBS services, such as eMBB services. Therefore, when there is no MBS service transmission, the terminal device can be released to an idle state or an inactive state by the network side or remain in a connected state. When the terminal device is in an idle state or an inactive state, when the data of the MBS service arrives, the network side can wake up the terminal device through paging to receive the MBS service.

[0071] When the terminal device is in the RRC connection state and there is a bearer for receiving unicast services, the terminal device supports mobility processes in the RRC connection state, such as the switching process, the RRC connection reestablishment process, and the terminal device context request process. With the introduction of MBS services, the terminal device needs to enter the RRC connection state to receive services. There are scenarios where only MBS services are received but no unicast services are received, there are scenarios where only unicast services are received but no MBS services are received, and there are scenarios where both MBS services and unicast services are received. At this time, how to support the mobility of the terminal device needs to be clarified.

[0072] To this end, the following technical solutions of the embodiments of the present application are proposed.

[0073] Figure 3is a flow chart of a bearer configuration method provided in an embodiment of the present application, such as Figure 3 As shown, the bearer configuration method includes the following steps:

[0074] Step 301: The network device sends a bearer configuration instruction to the terminal device, and the terminal device receives the bearer configuration instruction sent by the network device, where the bearer configuration instruction is used to configure signaling SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and / or at least one MRB.

[0075] In some optional implementations of the present application, the network device may be a base station.

[0076] In the embodiment of the present application, the types of Radio Bearer (RB) can be divided into: SRB, DRB, MRB. Among them, SRB belongs to signaling bearer, DRB and MRB belong to data bearer. Furthermore, the DRB is a bearer for the terminal device to receive unicast services. The MRB is a bearer for the terminal device to receive multicast services, where the multicast service refers to the MBS service in multicast mode. The following is an explanation of SRB.

[0077] SRB is used to transmit signaling. SRB0 is the default bearer, which already exists when the terminal device is in the RRC idle state or the RRC inactive state. The RRC entity is the entity that manages the bearer, and completes the establishment, modification and release of the bearer through the interaction of RRC signaling. Because SRB0 does not need to be established, the terminal device can obtain the configuration and resources of SRB0 in the RRC idle state or the RRC inactive state, and can use it directly if necessary. SRB1 can be established by transmitting signaling on SRB0. After SRB1 is established, the terminal device enters the RRC connected state, and then transmits signaling through SRB1 to establish SRB2. SRB2 is used to transmit non-access stratum (NAS) signaling; data bearers can also be established by transmitting signaling through SRB1, and data bearers are used to transmit service data. During the service process, the bearer is managed through SRB1. When the service is completed, the signaling transmitted on SRB1 can release all data bearers and signaling bearers, so that the terminal device enters the RRC idle state. , When needed, the only resource that the UE can use is SRB0, and it needs to be done after completing random access.

[0078] The RRC Setup message is used to establish SRB1, which is carried in SRB0.

[0079] The RRC Reconfiguration message is used to modify the RRC connection and is carried in SRB1.

[0080] It should be noted that the establishment of SRB2 and data bearers is initiated only after the access stratum (AS) security is activated. For SRB2 and DRB, E-UTRAN will not establish these bearers before activating security.

[0081] In the embodiment of the present application, when the network device configures the bearer for the terminal device, the bearer is configured under certain configuration constraints. Here, the configuration constraint is: SRB2 and data bearer must be configured at the same time. The network device cannot be configured with only one SRB2 or only at least one data bearer.

[0082] Based on this configuration constraint, the bearer configuration instruction sent by the network device to the terminal device is used to configure SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and / or at least one MRB. Here, the terminal device is a terminal device in an RRC connected state, that is, SRB1 has been established.

[0083] In the above solution, the bearer configuration instruction is an RRC dedicated signaling. The bearer configuration instruction is carried in SRB1.

[0084] In the embodiment of the present application, due to the existence of the above configuration constraint, the network device also needs to follow the configuration constraint when releasing the bearer. Based on this configuration constraint, if all of the at least one data bearer are released, the SRB2 is also released; or, if the SRB2 is released, all of the at least one data bearer are also released. Optionally, further, if the SRB2 and all of the at least one data bearer are released, the RRC connection is also released.

[0085] For example, when the network device releases the data bearer, if all the data bearers of the terminal device (such as MRB and DRB) are released, SRB2 also needs to be released. Furthermore, the RRC connection of the terminal device also needs to be released (ie, SRB1 is released).

[0086] In the embodiment of the present application, after the terminal device is configured with the above-mentioned bearer, it supports the mobility process in the following multiple scenarios.

[0087] Scenario 1: Switching scenes

[0088] After the AS is securely activated and the SRB2 and the at least one data bearer are established based on the bearer configuration instruction, the terminal device is able to receive synchronous reconfiguration, wherein the synchronous reconfiguration is carried in an RRC reconfiguration message, and the at least one data bearer includes at least one DRB and / or at least one MRB.

[0089] Here, synchronous reconfiguration is called "reconfigurationWithSync", where reconfigurationWithSync is contained in the "masterCellGroup" configuration.

[0090] Here, the masterCellGroup configuration is carried in the RRCReconfiguration message.

[0091] It should be noted that, in the above solution, after the SRB2 and the at least one data bearer are established, the SRB2 and the at least one data bearer need not be in a suspended state so that the terminal device can receive the synchronous reconfiguration.

[0092] The meaning of the above scheme in the embodiment of the present application can also refer to the contents of the following Table 1.

[0093]

[0094] Table 1

[0095] Scenario 2: RRC connection reestablishment scenario

[0096] After the AS is securely activated and the SRB2 and the at least one data bearer are established based on the bearer configuration instruction, the terminal device can trigger the RRC connection reconstruction process, and the at least one data bearer includes at least one DRB and / or at least one MRB.

[0097] The meaning of the above scheme in the embodiment of the present application can also refer to the contents of the following Table 2.

[0098]

[0099] Table 2

[0100] In some optional implementations of the present application, the terminal device does not support the mobility process in the following scenarios.

[0101] If the terminal device is configured with MRB and not configured with DRB, the terminal device cannot receive synchronous reconfiguration, wherein the synchronous reconfiguration is carried in the RRC reconfiguration message. If the terminal device is configured with MRB and not configured with DRB, the terminal device cannot trigger the RRC connection reestablishment process.

[0102] Here, when the terminal device is only configured with MRB but not DRB, regardless of whether AS security is activated at this time, the terminal device does not support receiving synchronous reconfiguration and triggering the RRC connection reestablishment process. Here, synchronous reconfiguration is called "reconfigurationWithSync", where reconfigurationWithSync is included in the "masterCellGroup" configuration. The masterCellGroup configuration is carried in the RRC reconfiguration (RRCReconfiguration) message.

[0103] Since the terminal device does not support the above mobility process, if a failure event occurs, the terminal device directly enters the RRC idle state. As an example, the failure event includes at least one of the following: radio link failure, RRC reconfiguration failure, integrity protection verification failure.

[0104] The technical solution of the embodiment of the present application provides configuration constraints for the bearer and behavior constraints for the terminal device when introducing the MBS service in multicast mode, so that the MBS configuration is reasonable and effective.

[0105] Figure 4 This is a schematic diagram of the structure of the load-bearing configuration device provided in the embodiment of the present application. Figure 1 , applied to terminal devices, such as Figure 4 As shown, the load-bearing configuration device includes:

[0106] The receiving unit 401 is used to receive a bearer configuration instruction sent by a network device, where the bearer configuration instruction is used to configure SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and / or at least one MRB.

[0107] In some optional implementations of the present application, the bearer configuration instruction is RRC dedicated signaling.

[0108] In some optional embodiments of the present application, after the AS is securely activated and after the SRB2 and the at least one data bearer are established based on the bearer configuration instruction, the terminal device is able to receive synchronous reconfiguration, wherein the synchronous reconfiguration is carried in an RRC reconfiguration message, and the at least one data bearer includes at least one DRB and / or at least one MRB.

[0109] In some optional embodiments of the present application, after the AS is securely activated and after the SRB2 and the at least one data bearer are established based on the bearer configuration instruction, the terminal device can trigger the RRC connection reconstruction process, and the at least one data bearer includes at least one DRB and / or at least one MRB.

[0110] In some optional implementations of the present application, if the terminal device is configured with MRB but not with DRB, the terminal device cannot receive synchronous reconfiguration, wherein the synchronous reconfiguration is carried in an RRC reconfiguration message.

[0111] In some optional implementations of the present application, if the terminal device is configured with MRB but not with DRB, the terminal device cannot trigger the RRC connection reconstruction process.

[0112] In some optional embodiments of the present application, the device further includes:

[0113] A state control unit is used to control the terminal device to enter an RRC idle state if a failure event occurs.

[0114] In some optional implementations of the present application, the failure event includes at least one of the following:

[0115] Radio link failure, RRC reconfiguration failure, integrity protection verification failure.

[0116] In some optional implementations of the present application, if all of the at least one data bearer are released, the SRB2 is also released; or,

[0117] If the SRB2 is released, all of the at least one data bearer are also released.

[0118] In some optional embodiments of the present application, if the SRB2 and all of the at least one data bearer are released, the RRC connection is also released.

[0119] In some optional implementations of the present application, the MRB is a bearer for the terminal device to receive multicast services.

[0120] Those skilled in the art should understand that the relevant description of the above-mentioned bearer configuration device in the embodiment of the present application can be understood by referring to the relevant description of the bearer configuration method in the embodiment of the present application.

[0121] Figure 5 This is a schematic diagram of the structure of the load-bearing configuration device provided in the embodiment of the present application. Figure 2 , applied to network equipment, such as Figure 5 As shown, the load-bearing configuration device includes:

[0122] The sending unit 501 is used to send a bearer configuration instruction to a terminal device, where the bearer configuration instruction is used to configure SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and / or at least one MRB.

[0123] In some optional implementations of the present application, the bearer configuration instruction is RRC dedicated signaling.

[0124] In some optional implementations of the present application, if all of the at least one data bearer are released, the SRB2 is also released; or,

[0125] If the SRB2 is released, all of the at least one data bearer are also released.

[0126] In some optional embodiments of the present application, if the SRB2 and all of the at least one data bearer are released, the RRC connection is also released.

[0127] In some optional implementations of the present application, the MRB is a bearer for the terminal device to receive multicast services.

[0128] Those skilled in the art should understand that the relevant description of the above-mentioned bearer configuration device in the embodiment of the present application can be understood by referring to the relevant description of the bearer configuration method in the embodiment of the present application.

[0129] Figure 6 600 is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. The communication device may be a terminal device or a network device. Figure 6 The communication device 600 shown includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0130] Alternatively, if Figure 6 As shown, the communication device 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0131] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0132] Alternatively, if Figure 6 As shown, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0133] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of the antennas may be one or more.

[0134] Optionally, the communication device 600 may specifically be a network device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0135] Optionally, the communication device 600 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0136] Figure 7 It is a schematic structural diagram of the chip of an embodiment of the present application. Figure 7 The chip 700 shown includes a processor 710, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0137] Alternatively, if Figure 7 As shown, the chip 700 may further include a memory 720. The processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.

[0138] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0139] Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0140] Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0141] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0142] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0143] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0144] Figure 8 8 is a schematic block diagram of a communication system 800 provided in an embodiment of the present application. Figure 8 As shown, the communication system 800 includes a terminal device 810 and a network device 820 .

[0145] Among them, the terminal device 810 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 820 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0146] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0147] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0148] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0149] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0150] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0151] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0152] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0153] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0154] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0155] The embodiment of the present application also provides a computer program.

[0156] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0157] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0158] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0159] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0160] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0161] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple 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.

[0162] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0163] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0164] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A bearer configuration method, the method comprising: The terminal device receives a bearer configuration instruction sent by the network device, where the bearer configuration instruction is used to configure a signaling radio bearer SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one data radio bearer DRB and / or at least one multicast radio bearer MRB, Wherein, the method further comprises: If the terminal device is configured with an MRB and not configured with a DRB, the terminal device is unable to receive a synchronous reconfiguration, wherein the synchronous reconfiguration is carried in a radio resource control RRC reconfiguration message; or If the terminal device is configured with MRB but not with DRB, the terminal device cannot trigger the RRC connection reconstruction process.

2. The method according to claim 1, wherein: The bearer configuration instruction is RRC dedicated signaling.

3. The method according to claim 1 or 2, wherein: The method further comprises: After the access layer AS is securely activated and the SRB2 and the at least one data bearer are established based on the bearer configuration instruction, the terminal device is able to receive synchronous reconfiguration, wherein the synchronous reconfiguration is carried in the RRC reconfiguration message, and the at least one data bearer includes at least one DRB and / or at least one MRB.

4. The method according to claim 1 or 2, wherein: The method further comprises: After the AS is securely activated and the SRB2 and the at least one data bearer are established based on the bearer configuration instruction, the terminal device can trigger the RRC connection reconstruction process, and the at least one data bearer includes at least one DRB and / or at least one MRB.

5. A bearer configuration method, the method comprising: The network device sends a bearer configuration instruction to the terminal device, where the bearer configuration instruction is used to configure a signaling radio bearer SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one data radio bearer DRB and / or at least one multicast radio bearer MRB, The network device further sends a radio resource control RRC reconfiguration message carrying synchronization reconfiguration. If the terminal device is configured with an MRB but not with a DRB, the synchronous reconfiguration cannot be received by the terminal device; or If the terminal device is configured with MRB but not with DRB, the RRC connection reestablishment process cannot be triggered by the terminal device.

6. A bearer configuration device, applied to a terminal device, the device comprising: A receiving unit, configured to receive a bearer configuration instruction sent by a network device, wherein the bearer configuration instruction is used to configure a signaling radio bearer SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one data radio bearer DRB and / or at least one multicast radio bearer MRB, Wherein, if the terminal device is configured with an MRB and is not configured with a DRB, the terminal device cannot receive a synchronous reconfiguration, wherein the synchronous reconfiguration is carried in a radio resource control RRC reconfiguration message; or If the terminal device is configured with MRB but not with DRB, the terminal device cannot trigger the RRC connection reconstruction process.

7. The device according to claim 6, wherein: The bearer configuration instruction is RRC dedicated signaling.

8. The device according to claim 6 or 7, wherein: After the access layer AS is securely activated and the SRB2 and the at least one data bearer are established based on the bearer configuration instruction, the terminal device is able to receive synchronous reconfiguration, wherein the synchronous reconfiguration is carried in the RRC reconfiguration message, and the at least one data bearer includes at least one DRB and / or at least one MRB.

9. The device according to claim 6 or 7, wherein: After the AS is securely activated and the SRB2 and the at least one data bearer are established based on the bearer configuration instruction, the terminal device can trigger the RRC connection reconstruction process, and the at least one data bearer includes at least one DRB and / or at least one MRB.

10. A bearer configuration device, applied to a network device, the device comprising: a sending unit, configured to send a bearer configuration instruction to a terminal device, wherein the bearer configuration instruction is used to configure a signaling radio bearer SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one data radio bearer DRB and / or at least one multicast radio bearer MRB, The sending unit is further configured to send a radio resource control RRC reconfiguration message carrying synchronization reconfiguration. If the terminal device is configured with an MRB but not with a DRB, the synchronous reconfiguration cannot be received by the terminal device; or If the terminal device is configured with MRB but not with DRB, the RRC connection reestablishment process cannot be triggered by the terminal device.

Images