Configuration method for bearer service, and system

Abstract

Disclosed in the present application are a configuration method for a bearer service, and a system. The method comprises: a first base station receiving a first core network message from a core network, or receiving a first inter-station message from a second base station, wherein the first core network message or the first inter-station message includes at least one of the following: restrictions on emergency service support by one or more radio access technologies, whether a cell allows an IP multimedia subsystem (IMS) emergency bearer service to be used for a reduced capability (RedCap) terminal, and whether the cell allows the IMS emergency bearer service to be used for an enhanced reduced capability (eRedCap) terminal. The present application solves the technical problem of an existing 3GPP Rel-18 protocol not being possible to meet the requirements of emergency call requests for RedCap terminals and ordinary terminals.

Description

Method and system for configuring a bearer service

[0001] Cross-reference to Related Applications

[0002] This application is based on the CN application number 202410536286.9, filed on April 29, 2024, and claims priority thereto, the disclosure of which is incorporated herein in its entirety. TECHNICAL FIELD

[0003] The present application relates to the technical field of wireless communication, in particular to a method and system for configuring a bearer service. BACKGROUND

[0004] The emergency call function of 5G technology is usually designed as a high-priority communication mechanism for communication with emergency services (such as police, fire, medical rescue) in emergency situations. This function aims to provide a faster and more reliable communication channel to ensure timely assistance in emergency situations.

[0005] In an emergency situation, a call made through the 5G network will be prioritized and ensured to be connected to the appropriate emergency service as soon as possible. However, ensuring the reliability of the emergency call function also requires comprehensive consideration of network coverage, device support, service provider settings, and other factors. Therefore, compared to ordinary services, emergency call services have different handling processes in access control and resource allocation, resulting in differences in related standard mechanisms. SUMMARY

[0006] The embodiments of the present application provide a method and system for configuring a bearer service to at least solve the technical problem that the current 3GPP Rel-18 protocol cannot meet the emergency call request of RedCap terminals and ordinary terminals.

[0007] According to an aspect of an embodiment of the present application, a method for configuring a bearer service is provided, applied to a first base station, comprising: receiving, by the first base station, a first core network message from a core network or a first inter-station message from a second base station, wherein the first core network message or the first inter-station message contains at least one of the following: one or more wireless access technologies support restrictions for emergency services, whether a cell allows IP multimedia subsystem (IMS) emergency bearer services for reduced capability (RedCap) terminals, and whether the cell allows IMS emergency bearer services for enhanced reduced capability (eRedCap) terminals.

[0008] In some embodiments, the method further comprises: receiving, by the first base station, a first core network message sent by the core network, or receiving a first inter-station message sent by the second base station; and determining, by the first base station, whether to set dual connectivity for emergency services according to the restriction information of one or more radio access technologies for emergency services support.

[0009] In some embodiments, in the dual connectivity, the first base station is configured to serve as a master node of the dual connectivity, and the third base station is configured to serve as a secondary node of the dual connectivity, wherein whether the third base station is allowed to serve as the secondary node of the dual connectivity is determined by the restriction information of one or more radio access technologies for emergency services support in the first core network message or the first inter-station message.

[0010] In some embodiments, in the case where the third base station is allowed to serve as the secondary node of the dual connectivity, a radio access technology adopted by the third base station is one indicated in the multiple restriction information of the restriction information of one or more radio access technologies for emergency services support.

[0011] In some embodiments, the first core network message is used to establish or modify context or bearer configuration information of a user, and the restriction information of one or more radio access technologies for emergency services support is included in the first core network message.

[0012] In some embodiments, the restriction information of one or more radio access technologies for emergency services support is included in the first inter-station message.

[0013] In some embodiments, the restriction information of one or more radio access technologies for emergency services support supports being set in one or more public land mobile networks (PLMNs) or being set to be not associated with any PLMN.

[0014] In some embodiments, the method further comprises: sending, by the first base station, an indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services in a broadcast message; wherein the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services is used to indicate whether RedCap terminals or eRedCap terminals support initiation of emergency services.

[0015] In some embodiments, the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services supports being configured to be set in one or more public land mobile networks (PLMNs) or being set to be applicable to all PLMNs without being associated with a PLMN.

[0016] In some embodiments, the method further comprises: receiving, by the first base station, a second inter-station message sent by the second base station, wherein the second inter-station message includes the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services.

[0017] In some embodiments, the method further comprises: sending, by the first base station, a third inter-station message to the second base station, wherein the third inter-station message comprises an indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services.

[0018] In some embodiments, in a case where the first base station receives a handover request message for the Internet of Things terminal sent by the second base station, when an address resolution protocol (ARP) value of a bearer carried in the handover request message does not belong to emergency services, the terminal handover is allowed to be admitted at the first base station.

[0019] In some embodiments, in a case where the first base station receives a handover request message for the Internet of Things terminal sent by the second base station, when the ARP value of the bearer carried in the handover request message belongs to emergency services, and when the terminal is a RedCap or eRedCap 1Rx, the terminal handover is allowed to be admitted at the first base station in a case where a current cell is set to RedCap 1Rx or eRedCap 1Rx to allow access, and an indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services is set to yes, and is not allowed to be admitted in other cases, and a handover failure cause is determined, the handover failure cause comprising at least one of: RedCap terminals are not allowed to access emergency services, eRedCap terminals are not allowed to access emergency services, RedCap terminals are not allowed to access, and eRedCap terminals are not allowed to access.

[0020] In some embodiments, in a case where the first base station receives a handover request message for the Internet of Things terminal sent by the second base station, when the ARP value of the bearer carried in the handover request message belongs to emergency services, and when the terminal is a RedCap or eRedCap 2Rx, the terminal handover is allowed to be admitted at the first base station in a case where a current cell is set to RedCap 2Rx or eRedCap 2Rx to allow access, and an indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services is set to yes, and is not allowed to be admitted in other cases, and a handover failure cause is determined, the handover failure cause comprising at least one of: RedCap terminals are not allowed to access emergency services, eRedCap terminals are not allowed to access emergency services, RedCap terminals are not allowed to access, and eRedCap terminals are not allowed to access.

[0021] In some embodiments, the method further comprises: sending, by the first base station, a handover request of the terminal to the second base station, wherein the handover request comprises one or more radio access technology limitations on emergency service support, the one or more radio access technology limitations on emergency service support being set for one or more public land mobile networks (PLMNs) or being set to be not associated with any PLMN.

[0022] According to an aspect of the embodiments of the present application, another method for configuring a bearer service is also provided, which is applied to a first base station centralized entity, and includes: receiving, by the first base station centralized entity, a first core network message from a core network or a first inter-station message from a second base station, wherein the first core network message or the first inter-station message includes at least one of: a restriction of one or more radio access technologies for emergency service support, whether the cell allows an IP multimedia subsystem (IMS) emergency bearer service for a reduced capability (RedCap) terminal, or whether the cell allows the IMS emergency bearer service for an enhanced RedCap (eRedCap) terminal; and receiving, by the first base station centralized entity, a first intra-station message sent by a first base station separated entity, wherein the first intra-station message carries first restriction information, and the first restriction information indicates at least one of: whether the cell allows the IMS emergency bearer service for the RedCap terminal, or whether the cell allows the IMS emergency bearer service for the eRedCap terminal.

[0023] In some embodiments, the method further includes: receiving, by the first base station centralized entity, a first core network message sent by the core network or a first inter-station message sent by the second base station; and determining, by the first base station centralized entity, whether to set dual connectivity for emergency service according to the restriction of the one or more radio access technologies for emergency service support.

[0024] In some embodiments, in the dual connectivity, the first base station is used as a master node of the dual connectivity, and the third base station is used as a secondary node of the dual connectivity, wherein whether the third base station is allowed to be the secondary node of the dual connectivity is determined by the restriction of the one or more radio access technologies for emergency service support in the first core network message or the first inter-station message.

[0025] In some embodiments, in the case where the third base station is allowed to be the secondary node of the dual connectivity, a radio access technology used by the third base station is one indicated in the multiple restriction information of the restriction of the one or more radio access technologies for emergency service support.

[0026] In some embodiments, the first core network message is used to establish or modify context or bearer configuration information of a user, and the first core network message includes the restriction of the one or more radio access technologies for emergency service support.

[0027] In some embodiments, the first inter-station message includes the restriction of the one or more radio access technologies for emergency service support.

[0028] In some embodiments, the restriction of the one or more radio access technologies for emergency service support is set in one or more public land mobile networks (PLMNs) or is set to be not associated with any PLMN.

[0029] In some embodiments, the method further comprises: receiving, by the first base station centralized entity, a first intra-site message from the first base station distributed entity, wherein the first intra-site message carries an indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services.

[0030] In some embodiments, the first base station distributed entity is configured to send, in the broadcast message, an indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services, wherein the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services is used to indicate whether RedCap or eRedCap terminals support initiation of emergency services.

[0031] In some embodiments, the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services is configured to be set for one or more public land mobile networks (PLMNs) or not set in association with the PLMNs.

[0032] In some embodiments, the method further comprises: receiving, by the first base station centralized entity, a second inter-site message sent by a second base station, wherein the second inter-site message includes the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services.

[0033] In some embodiments, the method further comprises: sending, by the first base station centralized entity, a third inter-site message to the second base station, wherein the third inter-site message includes the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services.

[0034] In some embodiments, in a case where the first base station centralized entity receives a handover request message sent by the second base station for an Internet of Things terminal, when an address resolution protocol (ARP) value of a bearer carried in the handover request message does not belong to emergency services, terminal handover is allowed to be admitted at the first base station centralized entity.

[0035] In some embodiments, in case the first set of base stations entity receives a handover request message for the terminal sent by the second base station, when the ARP value of the bearer carried in the handover request message belongs to the emergency service, and when the terminal is a RedCap or eRedCap 1Rx, the terminal handover is allowed to be admitted by the first set of base stations entity in case that the current cell is set to RedCap 1Rx or eRedCap 1Rx allowing access, and the indication of whether to allow RedCap terminal or eRedCap terminal emergency service access is set to yes, otherwise not allowed to be admitted, and a handover failure cause is determined, the handover failure cause includes at least one of: not allowed RedCap terminal emergency service, not allowed eRedCap terminal emergency service, not allowed RedCap terminal access, not allowed eRedCap terminal access.

[0036] In some embodiments, in case the first set of base stations entity receives a handover request message for the terminal sent by the second base station, when the ARP value of the bearer carried in the handover request message belongs to the emergency service, and when the terminal is a RedCap or eRedCap 2Rx, the terminal handover is allowed to be admitted by the first set of base stations entity in case that the current cell is set to RedCap 2Rx or eRedCap 2Rx allowing access, and the indication of whether to allow RedCap terminal or eRedCap terminal emergency service access is set to yes, otherwise not allowed to be admitted, and a handover failure cause is determined, the handover failure cause includes at least one of: not allowed RedCap terminal emergency service, not allowed eRedCap terminal emergency service, not allowed RedCap terminal access, not allowed eRedCap terminal access.

[0037] In some embodiments, the method further comprises: the first set of base stations entity sends a handover request for the terminal to the second base station, wherein the handover request comprises one or more radio access technologies for emergency service support restrictions, and the one or more radio access technologies for emergency service support restrictions support being set in one or more public land mobile networks (PLMNs) or being set to not be associated with any PLMN.

[0038] According to an aspect of the embodiments of the present application, another method for configuring a bearer service is also provided, including: receiving, by a terminal, at least one of the following from a first base station broadcast message: whether a reduced capability RedCap terminal or an enhanced reduced capability eRedCap terminal emergency service access indication is allowed, whether a cell is prohibited from being accessed, whether eRedCap 1Rx access is allowed, whether eRedCap 2Rx access is allowed, whether RedCap 1Rx access is allowed, and whether RedCap 2Rx access is allowed; and the terminal is not allowed to select or reselect a current cell in a case of including an emergency call, except for a first case, a second case, a third case, and a fourth case; wherein the first case is that: eRedCap 1Rx in the broadcast message is set to not allow access, an eRedCap terminal only supports a 1Rx channel, the current cell is an acceptable cell and a selection condition of the cell is met, the cell is not set to be prohibited from being accessed in a MIB message, an eRedCap terminal emergency service access indication is set to yes, and in a case of eRedCap only supporting half duplex FDD operation, whether eRedCap half duplex is allowed in the broadcast message is set to yes; the second case is that: eRedCap 2Rx in the broadcast message is set to not allow access, an eRedCap terminal only supports a 2Rx channel, the current cell is an acceptable cell and a selection condition of the cell is met, the cell is not set to be prohibited from being accessed in a MIB message, an eRedCap terminal emergency service access indication is set to yes, and in a case of eRedCap only supporting half duplex FDD operation, whether eRedCap half duplex is allowed in the broadcast message is set to yes; the third case is that: RedCap 1Rx in the broadcast message is set to not allow access, a RedCap terminal only supports a 1Rx channel, the current cell is an acceptable cell and a selection condition of the cell is met, the cell is not set to be prohibited from being accessed in a MIB message, a RedCap terminal emergency service access indication is set to yes, and in a case of RedCap only supporting half duplex FDD operation, whether RedCap half duplex is allowed in the broadcast message is set to yes; and the fourth case is that: RedCap 2Rx in the broadcast message is set to not allow access, a RedCap terminal only supports a 2Rx channel, the current cell is an acceptable cell and a selection condition of the cell is met, the cell is not set to be prohibited from being accessed in a MIB message, a RedCap terminal emergency service access indication is set to yes, and in a case of RedCap only supporting half duplex FDD operation, whether RedCap half duplex is allowed in the broadcast message is set to yes.

[0039] According to an aspect of the embodiments of the present application, a method for configuring a bearer service is also provided. The method is applied to a second base station and includes: sending, by the second base station, a first inter-station message to a first base station or a first base station centralized entity, wherein the first inter-station message includes at least one of: a restriction of one or more radio access technologies on support for emergency services, whether a cell allows an IP multimedia subsystem (IMS) emergency bearer service for a reduced capability (RedCap) terminal, and whether the cell allows the IMS emergency bearer service for an enhanced RedCap (eRedCap) terminal.

[0040] In some embodiments, the restriction of the one or more radio access technologies on support for emergency services is set for one or more public land mobile networks (PLMNs) or is set to be not associated with any PLMN.

[0041] In some embodiments, the method further includes: sending, by the second base station, a second inter-station message to the first base station or the first base station centralized entity, wherein the second inter-station message includes: an indication of whether a RedCap terminal or an eRedCap terminal is allowed to access emergency services; and wherein the indication of whether the RedCap terminal or the eRedCap terminal is allowed to access emergency services indicates whether the RedCap terminal or the eRedCap terminal supports initiation of emergency services.

[0042] In some embodiments, the method further includes: receiving, by the second base station, a third inter-station message sent by the first base station or the first base station centralized entity, wherein the third inter-station message includes the indication of whether the RedCap terminal or the eRedCap terminal is allowed to access emergency services.

[0043] In some embodiments, the method further includes: sending, by the second base station, a handover request message for an Internet of Things (IoT) terminal to the first base station or the first base station centralized entity.

[0044] In some embodiments, when an address resolution protocol (ARP) value of a bearer carried in the handover request message does not belong to emergency services, the terminal is allowed to be admitted at the first base station or the first base station centralized entity.

[0045] In some embodiments, when the ARP value of the bearer carried in the handover request message belongs to emergency service, and when the terminal is RedCap or eRedCap 1Rx, the terminal is allowed to be admitted at the first base station in the case that the current cell is set to RedCap 1Rx or eRedCap 1Rx allowing access, and the indication of whether to allow RedCap terminal or eRedCap terminal emergency service access is set to yes, otherwise not allowed to be admitted, wherein the cause of handover failure includes at least one of: not allowed RedCap terminal emergency service, not allowed eRedCap terminal emergency service, not allowed RedCap terminal access, and not allowed eRedCap terminal access.

[0046] In some embodiments, when the ARP value of the bearer carried in the handover request message belongs to emergency service, and when the terminal is RedCap or eRedCap 2Rx, the terminal is allowed to be admitted at the first base station in the case that the current cell is set to RedCap 2Rx or eRedCap 2Rx allowing access, and the indication of whether to allow RedCap terminal or eRedCap terminal emergency service access is set to yes, otherwise not allowed to be admitted, wherein the cause of handover failure includes at least one of: not allowed RedCap terminal emergency service, not allowed eRedCap terminal emergency service, not allowed RedCap terminal access, and not allowed eRedCap terminal access.

[0047] In some embodiments, the method further comprises: receiving, by the second base station, a handover request of the terminal sent by the first base station or a centralized entity of the first base station, wherein the handover request comprises one or more radio access technologies for emergency service support restrictions, and the one or more radio access technologies for emergency service support restrictions are set to support one or more public land mobile networks (PLMNs) or are set to be not associated with any PLMN.

[0048] According to an aspect of some embodiments of the present application, a system for configuring a bearer service is provided. The system includes a first base station and a second base station. The first base station includes a first base station centralized entity and a first base station distributed entity. The first base station or the first base station centralized entity receives a first core network message sent by a core network or a first inter-station message sent by the second base station. The first core network message or the first inter-station message includes at least one of a restriction of one or more radio access technologies for emergency service support, whether the cell allows IP multimedia subsystem (IMS) emergency bearer service for a reduced capability (RedCap) terminal, or whether the cell allows IMS emergency bearer service for an enhanced RedCap (eRedCap) terminal. The first base station centralized entity receives a first intra-station message sent by the first base station distributed entity or the first base station receives a second inter-station message sent by the second base station. The first intra-station message and the second inter-station message both carry first restriction information indicating at least one of whether the cell allows IMS emergency bearer service for a RedCap terminal or whether the cell allows IMS emergency bearer service for an eRedCap terminal.

[0049] According to an aspect of some embodiments of the present application, a method for configuring a bearer service is provided. The method is performed by a first base station and includes receiving a first inter-station message from a second base station. The first inter-station message includes at least one of whether a cell allows IP multimedia subsystem (IMS) emergency bearer service for a reduced capability (RedCap) terminal or whether the cell allows IMS emergency bearer service for an enhanced RedCap (eRedCap) terminal. The method further includes sending a second inter-station message. The second inter-station message includes at least one of whether the cell allows IMS emergency bearer service for a RedCap terminal or whether the cell allows IMS emergency bearer service for an eRedCap terminal.

[0050] In some embodiments, the method further includes receiving a first core network message from a core network. The first core network message includes at least one of whether a cell allows IP multimedia subsystem (IMS) emergency bearer service for a reduced capability (RedCap) terminal or whether the cell allows IMS emergency bearer service for an enhanced RedCap (eRedCap) terminal.

[0051] In some embodiments, receiving the first inter-station message from the second base station includes receiving a first broadcast message from the second base station to obtain the first inter-station message. The first inter-station message is sent by the second base station through broadcasting.

[0052] In some embodiments, the second inter-station message is sent through a second broadcast message.

[0053] In some embodiments, whether the cell allows IP Multimedia Subsystem, IMS, emergency bearer services in the first inter-station message is used to indicate whether the RedCap terminal supports initiation of emergency services at the second base station; whether the cell allows IP Multimedia Subsystem, IMS, emergency bearer services in the first inter-station message is used to indicate whether the eRedCap terminal supports initiation of emergency services at the second base station.

[0054] In some embodiments, whether the cell allows IP Multimedia Subsystem, IMS, emergency bearer services in the second inter-station message is used to indicate whether the RedCap terminal supports initiation of emergency services at the first base station; whether the cell allows IP Multimedia Subsystem, IMS, emergency bearer services in the second inter-station message is used to indicate whether the eRedCap terminal supports initiation of emergency services at the first base station.

[0055] In some embodiments, the first inter-station message or the second inter-station message further comprises one or more radio access technologies' limitation information for emergency services support.

[0056] In some embodiments, the first core network message further comprises one or more radio access technologies' limitation information for emergency services support.

[0057] In some embodiments, the one or more radio access technologies' limitation information for emergency services support comprises: being set for one or more Public Land Mobile Networks, PLMNs, or being set for not being associated with any PLMN.

[0058] In some embodiments, at least one of whether the RedCap terminal supports initiation of emergency services or whether the eRedCap terminal supports initiation of emergency services is set for one or more PLMNs, or is set for not being associated with any PLMN, wherein, when being set for not being associated with any PLMN, at least one of whether the RedCap terminal supports initiation of emergency services or whether the eRedCap terminal supports initiation of emergency services is applicable to all PLMNs.

[0059] In some embodiments, the method further comprises: determining whether to set dual connectivity for emergency services according to the one or more radio access technologies' limitation information for emergency services support.

[0060] In some embodiments, at least one of receiving the first inter-station message from the second base station or transmitting the second inter-station message is performed by a centralized entity of the first base station; the method further includes: receiving, by the centralized entity of the first base station, a first intra-station message transmitted by a distributed entity of the first base station, wherein the first intra-station message carries the first restriction information, and the first restriction information is used to indicate at least one of whether the cell allows IMS emergency bearer service for RedCap terminals or whether the cell allows IMS emergency bearer service for eRedCap terminals.

[0061] According to an aspect of embodiments of the present application, a method for configuring a bearer service is provided, which is performed by a terminal and includes: obtaining a broadcast message from a first base station, the broadcast message including at least one of: an indication of whether reduced capability RedCap terminals or enhanced reduced capability eRedCap terminals are allowed to access emergency services, whether a cell is barred from access, whether eRedCap 1Rx is allowed to access, whether eRedCap 2Rx is allowed to access, whether RedCap 1Rx is allowed to access, whether RedCap 2Rx is allowed to access.

[0062] In some embodiments, the method further comprises: according to the broadcast message, the terminal is allowed to select or reselect the cell of the first base station in one or more of the following cases if an emergency call occurs: the eRedCap 1Rx in the broadcast message is set to not allow access, the eRedCap terminal only supports a 1Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set to be barred in the MIB message, and the indication of whether to allow eRedCap terminal emergency service access is set to yes, and in the case that the eRedCap only supports half duplex FDD operation, the broadcast message whether to allow eRedCap half duplex is set to yes; the eRedCap 2Rx in the broadcast message is set to not allow access, the eRedCap terminal only supports a 2Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set to be barred in the MIB message, and the indication of whether to allow eRedCap terminal emergency service access is set to yes, and in the case that the eRedCap only supports half duplex FDD operation, the broadcast message whether to allow eRedCap half duplex is set to yes; the RedCap 1Rx in the broadcast message is set to not allow access, the RedCap terminal only supports a 1Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set to be barred in the MIB message, and the indication of whether to allow RedCap terminal emergency service access is set to yes, and in the case that the RedCap only supports half duplex FDD operation, the broadcast message whether to allow RedCap half duplex is set to yes; or the RedCap 2Rx in the broadcast message is set to not allow access, the RedCap terminal only supports a 2Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set to be barred in the MIB message, and the indication of whether to allow RedCap terminal emergency service access is set to yes, and in the case that the RedCap only supports half duplex FDD operation, the broadcast message whether to allow RedCap half duplex is set to yes.

[0063] According to an aspect of an embodiment of the present application, a network device is provided, comprising: a memory; and a processor coupled to the memory, the processor being configured to perform any of the methods above based on instructions stored in the memory.

[0064] According to an aspect of an embodiment of the present application, a computer readable storage medium having computer instructions stored thereon is provided, the instructions being executed by a processor to implement any of the methods of configuring a service above.

[0065] According to an aspect of an embodiment of the present application, a computer program product is provided, comprising a computer program or instructions, the computer program or instructions being executed by a processor to implement the method of any of claims 1 to 53.

[0066] According to an aspect of the embodiments of the present application, a communication system is provided, comprising: a first base station configured to perform any of the bearer service configuration methods performed by the first base station; and a terminal configured to perform any of the bearer service configuration methods performed by the terminal.

[0067] In some embodiments, the system further comprises: a second base station configured to perform any of the bearer service configuration methods performed by the second base station.

[0068] In some embodiments, the first base station comprises: a first base station centralized entity configured to perform any of the bearer service configuration methods performed by the first base station centralized entity; and a first base station distributed entity configured to send, in a broadcast message, an indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services, wherein the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services is used to indicate whether RedCap or eRedCap terminals support the initiation of emergency services.

[0069] In the embodiments of the present application, the first base station receives a first core network message from a core network or a first inter-station message from a second base station, wherein the first core network message or the first inter-station message contains at least one of the following: a restriction on emergency service support by one or more radio access technologies, whether a cell allows IP multimedia subsystem (IMS) emergency bearer services for RedCap terminals, whether the cell allows IMS emergency bearer services for enhanced RedCap (eRedCap) terminals, and a manner in which the cell allows at least one of the following: IMS emergency bearer services for RedCap terminals, IMS emergency bearer services for eRedCap terminals, and emergency call capabilities for RedCap terminals in a centralized unit (CU) / distributed unit (DU) split architecture. By supporting a base station to determine whether to configure a secondary node for a terminal for an emergency call based on the configuration information, the need to support emergency calls for RedCap terminals in forbidden cells and emergency calls for ordinary terminals in a dual connectivity scenario is achieved, thereby solving the technical problem that the current 3GPP Rel-18 protocol cannot meet the emergency call request for RedCap terminals and ordinary terminals. BRIEF DESCRIPTION OF DRAWINGS

[0070] The accompanying drawings, which are included to provide a further understanding of the present application and constitute a part of this application, illustrate certain illustrative embodiments of the present application and together with the description serve to explain the present application. In the drawings:

[0071] FIG. 1 is a flow diagram of a bearer service configuration method according to an embodiment of the present application;

[0072] FIG. 2 is a flow diagram of another method for configuring a bearer service according to an embodiment of the present application;

[0073] FIG. 3 is a flow diagram of yet another method for configuring a bearer service according to an embodiment of the present application;

[0074] FIG. 4 is a flow diagram of still another method for configuring a bearer service according to an embodiment of the present application;

[0075] FIG. 5 is a structural diagram of a system for configuring a bearer service according to an embodiment of the present application;

[0076] FIG. 6 is a diagram of a process for establishing an F1 interface between a split entity and a centralized entity according to an embodiment of the present application;

[0077] FIG. 7 is a diagram of a configuration update process for a split entity according to an embodiment of the present application.

[0078] FIG. 8 is a diagram of a network device according to an embodiment of the present application.

[0079] FIG. 9 is a diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0080] In order to make the personnel in the technical field better understand the present application scheme, the technical scheme in the present application embodiment will be described clearly and completely below in combination with the drawings in the present application embodiment. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by the person of ordinary skill in the art without making creative labor should belong to the scope of protection of the present application.

[0081] It should be noted that the terms "first", "second", and the like in the specification and claims of the present application and the above-described drawings are used to distinguish similar objects, and do not necessarily have to describe a specific order or a sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not have to be limited to those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0082] In 3GPP R17 version, in order to meet the terminal specific requirements in the middle-end Internet of Things application scenarios such as industrial wireless sensors, video monitoring and wearable devices, 3GPP defines a 5G RedCap device type, which further reduces the complexity and cost of 5G terminals by reducing terminal complexity, reducing device size, etc., and RedCap does not support multi-carrier capabilities such as carrier aggregation and dual connectivity. However, for low-speed wide Internet of Things scenarios such as smart power grids, smart cities, industrial automation, and industrial monitoring sensors, which have lower speed requirements and are more sensitive to terminal costs, there is still some resource redundancy in using the RedCap technical capabilities of the R17 version.

[0083] In order to further expand the application scenarios of R17 RedCap terminals and reduce terminal complexity and cost, 3GPP R18 version proposes 5G RedCap evolution technology research, referred to as eRedCap((Enhanced Reduced Capability, enhanced reduced capability). Compared with RedCap terminals, eRedCap further reduces the peak rate to 10Mbps, and eRedCap is aimed at low-speed wide Internet of Things scenarios, which have lower speed requirements and are more sensitive to terminal costs.

[0084] 1) Further reduce complexity: mainly including further reducing terminal bandwidth, reducing peak rate, and relaxing terminal processing time, wherein the eRedCap peak rate is reduced to 10Mbps uplink and downlink, while the RedCap can reach 100-200Mbps. In addition, there are differences in channel bandwidth between the two, wherein RedCap supports channel bandwidth configuration of not more than 20MHz, while eRedCap requires the scheduling bandwidth of PDSCH(Physical Downlink Shared Channel, downlink shared channel) / PUSCH(Physical Uplink Shared Channel, uplink shared channel) to be up to 5MHz.

[0085] 2) Energy saving technology evolution: support eDRx(Extended Discontinuous Reception, extended discontinuous reception) cycle greater than 10.24 seconds in the inactive state.

[0086] In the current SIB1 broadcast message, the access control includes the following contents:

[0087] 1) cellBarredRedCap1Rx-r17: used to control the terminal restriction of terminal access capability for terminal single reception;

[0088] 2) cellBarredRedCap2Rx-r17: used to control the terminal's access capability for terminals with dual reception;

[0089] 3) intraFreqReselectionRedCap: used to control the terminal's intra-frequency reselection capability, when this field is set to not supported, neither single-reception nor dual-reception terminals are allowed to access the current cell.

[0090] The emergency call function of 5G technology is usually designed as a high-priority communication mechanism for communication with emergency services (such as police, fire, medical rescue) in emergency situations. This function aims to provide a faster and more reliable communication channel to ensure timely assistance in emergency situations. In the 5G network, the emergency call function may have the following characteristics:

[0091] 1) High priority service: Emergency calls are usually assigned higher network priority to ensure communication capabilities in network congestion or other situations.

[0092] 2) Precise positioning: 5G technology usually supports more accurate positioning functions, which helps emergency services locate the source of the call and improves rescue efficiency.

[0093] 3) Multimedia support: 5G networks provide higher bandwidth and lower latency, allowing emergency calls to support a wider variety of communications, such as video, images, location sharing, etc., which helps better understand and handle situations in emergency situations.

[0094] 4) Adaptive network: 5G networks usually have adaptability, which can adjust resource allocation according to real-time network conditions to ensure the priority and stability of emergency calls.

[0095] In emergency situations, calls made through 5G networks will be prioritized and ensured to connect to the appropriate emergency services as soon as possible. However, ensuring the reliability of the emergency call function also requires comprehensive consideration of network coverage, device support, service provider settings, and other factors. Therefore, compared to ordinary services, emergency call services have different handling processes in access control and resource allocation, resulting in differences in related standard mechanisms.

[0096] In the 3GPP R16 stage, the related technology will issue a mobile restriction list to the core network for the opening restriction of different types of users. The main purpose is to implement all major access restrictions, and the related access must be deployed in different tracking area codes. Users cannot use the specific access to access the network in the TA area. When all secondary access restrictions are met, the user cannot use the access as a secondary access. The specific "Extended RAT Restriction Information" information is shown in the following table.

[0097] From the above, it can be seen that the restricted access of RAT (Radio Access Technology) does not involve the restricted access in the emergency call, and the protocol confirms that some access restrictions can be avoided to a certain extent in the emergency call. Therefore, when the base station supports terminals including RedCap, eRedCap, NR (New Radio) UE (User Equipment), etc., if the emergency call process is triggered, the current specification will have the following problems:

[0098] 1) For non-RedCap terminals, it cannot be determined whether to configure a dual connection state: the core network will in principle prohibit some RATs from being configured as carriers when making emergency calls, but the current specification does not support the above restrictions, resulting in the inability to restrict the terminal to use which carrier for emergency services. The dual connection can ensure that the terminal service can be camped on the appropriate carrier without switching, thereby ensuring the continuity of the service;

[0099] 2) For RedCap terminals, it cannot support accessing emergency services when the cell is prohibited: the current protocol does not support the terminal camping when the cell is prohibited, so it will not support emergency calls, but some scenarios need to ignore the cell prohibition of the base station and still support emergency call services. For example, children's watches and other terminals usually have only 1Rx (one receive antenna) reception capability, and these types of terminals need to perform emergency call capabilities in some special scenarios;

[0100] 3) In the CU / DU separation architecture, the transmission of the RedCap terminal emergency call capability is not supported: the current protocol does not support the transmission of the RedCap terminal emergency call capability in the F1 interface, so the CU does not know whether the DU allows the RedCap terminal emergency call.

[0101] Based on the above demand and reason analysis, it can be concluded that the current 3GPP Rel-18 protocol cannot meet the emergency call requirements of RedCap and ordinary terminals, and new standardized methods need to be used to enhance the functions to meet the needs of network deployment and optimization.

[0102] To solve the above problems, the related solutions in the embodiments of the present application are provided, which are described in detail below.

[0103] According to the embodiments of the present application, a method for configuring a bearer service is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order from here.

[0104] The embodiments of the present application provide a method for configuring a bearer service, and the execution subject is a first base station. FIG. 1 is a schematic diagram of a method flow for configuring a bearer service according to an embodiment of the present application. As shown in FIG. 1, the method includes the following steps:

[0105] In step S102, the first base station receives a first core network message from the core network or a first inter-station message from the second base station, wherein the first core network message or the first inter-station message contains at least one of the following: one or more wireless access technologies support restrictions for emergency services, whether the cell allows IP multimedia subsystem (IMS) emergency bearer service for reduced capability (RedCap) terminals, and whether the cell allows IMS emergency bearer service for enhanced reduced capability (eRedCap) terminals.

[0106] Through the above steps, by supporting the base station to determine whether to configure a secondary node for the terminal for emergency call according to the configuration information, and configuring the emergency call capability in the CU / DU separation architecture for RedCap, the purpose of supporting the emergency call of RedCap terminals in the forbidden cell and the emergency call of ordinary terminals in the dual connectivity scenario is achieved, thereby solving the technical problem that the current 3GPP Rel-18 protocol cannot meet the emergency call requirements of RedCap terminals and ordinary terminals.

[0107] In some embodiments, the first inter-station message is sent by the second base station in a broadcast manner, and the information contained therein is information for the cell of the second base station. Through inter-station interaction, the first base station receiving the first inter-station message obtains at least one of the following: one or more wireless access technologies support restrictions for emergency services of the cell of the second base station, whether the cell allows IP multimedia subsystem (IMS) emergency bearer service for reduced capability (RedCap) terminals, and whether the cell allows IMS emergency bearer service for enhanced reduced capability (eRedCap) terminals.

[0108] The configuration method of the bearer service in step S102 of the embodiment of the present application is further described below.

[0109] In the embodiment of the present application, the first base station sends whether the cell prohibits access, an emergency service access indication (used to indicate whether the terminal can perform emergency service when in a restricted state), whether to allow RedCap terminal or eRedCap terminal emergency service access indication, etc. in a broadcast message. The specific steps are as follows.

[0110] In some embodiments of the present application, the method further comprises the following steps: the first base station sends whether to allow RedCap terminal or eRedCap terminal emergency service access indication in a broadcast message; wherein the whether to allow RedCap terminal or eRedCap terminal emergency service access indication is used to indicate whether the RedCap terminal or eRedCap terminal supports the initiation of emergency service.

[0111] The whether to allow RedCap terminal or eRedCap terminal emergency service access indication supports being configured to be set when one or more public land mobile networks (PLMNs) or not associated with any PLMN, which means that the above configuration is applicable to all PLMNs.

[0112] In the embodiment of the present application, the first base station can receive a first core network message sent by the core network, wherein the first core network message is used to establish or modify the context or bearer configuration information of the user, and the first core network message includes the restriction of one or more radio access technologies for emergency service support.

[0113] In some embodiments, the message sent by the first base station through broadcasting is information for the cell of the first base station. One or more base stations receiving the broadcast message obtain at least one of the following from the cell of the first base station: the restriction of one or more radio access technologies for emergency service support, whether the cell allows IP multimedia subsystem (IMS) emergency bearer service for RedCap terminals, and whether the cell allows IMS emergency bearer service for eRedCap terminals.

[0114] In some embodiments of the present application, the restriction of one or more radio access technologies for emergency service support is set for one or more public land mobile networks (PLMNs) or is set to be not associated with any PLMN.

[0115] Alternatively, the first base station can also receive a first inter-station message sent by the second base station, wherein the first inter-station message includes the restriction of one or more radio access technologies for emergency service support.

[0116] In some embodiments of the present application, the restriction of one or more radio access technologies for emergency service support is set in one or more public land mobile networks (PLMNs) or is set to be not associated with any PLMN.

[0117] After the first base station receives the first core network message or the first inter-station message, the first base station can determine whether to set dual connectivity for emergency services according to the restriction of one or more radio access technologies for emergency service support.

[0118] Specifically, the first base station can determine whether a certain radio access technology can be used as a secondary node of dual connectivity for the terminal according to the restriction of one or more radio access technologies for emergency service support in the received first core network message or first inter-station message and whether the dual connectivity is supported in the wireless capability of the terminal.

[0119] In some embodiments of the present application, in dual connectivity, the first base station is used as a master node of dual connectivity and the third base station is used as a secondary node of dual connectivity, wherein the radio access technologies used by the first base station and the third base station are different, and whether the third base station is allowed to be a secondary node of dual connectivity is determined by the restriction of one or more radio access technologies for emergency service support in the first core network message or the first inter-station message.

[0120] In some embodiments of the present application, in the case where the third base station is allowed to be a secondary node of dual connectivity, the radio access technology used by the third base station is one indicated in the multiple restriction information of the restriction of one or more radio access technologies for emergency service support.

[0121] In addition, the first base station can also receive a second inter-station message from the second base station, wherein the second inter-station message includes an indication of whether a RedCap terminal or an eRedCap terminal is allowed to access emergency services.

[0122] In some embodiments of the present application, the method further includes the following steps: the first base station sends a third inter-station message to the second base station, wherein the third inter-station message includes an indication of whether a RedCap terminal or an eRedCap terminal is allowed to access emergency services.

[0123] The first base station receives a handover request message for an Internet of Things terminal sent by the second base station, wherein the acceptable scheme is as follows:

[0124] 1) In the case where the first base station receives a handover request message for an Internet of Things terminal sent by the second base station, when the address resolution protocol (ARP) value of the carried bearer in the handover request message does not belong to emergency services, the terminal handover is allowed to be accepted at the first base station, i.e., the terminal handover can be normally accepted at the first base station.

[0125] 2) In case the first base station receives a handover request message for the terminal sent by the second base station, when the ARP value of the carried bearer in the handover request message belongs to emergency service, and when the terminal is RedCap or eRedCap 1Rx, the terminal handover is allowed to be admitted in the first base station if the current cell is set to RedCap 1Rx or eRedCap 1Rx allowed access, and the indication of whether to allow RedCap terminal or eRedCap terminal emergency service access is set to yes, otherwise not allowed to be admitted, and the handover failure reason is determined, including at least one of: not allowed RedCap terminal emergency service, not allowed eRedCap terminal emergency service, not allowed RedCap terminal access, not allowed eRedCap terminal access.

[0126] Specifically, if the ARP value of the carried bearer belongs to emergency service and the terminal is RedCap or eRedCap 1Rx, if the current cell is not forbidden access, the terminal handover can be normally admitted in the first base station or the first base station set entity; if the current cell is forbidden access, and the indication of allowing RedCap or eRedCap terminal emergency service access is configured, the terminal handover can be normally admitted in the first base station or the first base station set entity; otherwise, the terminal access is rejected.

[0127] 3) In case the first base station receives a handover request message for the terminal sent by the second base station, when the ARP value of the carried bearer in the handover request message belongs to emergency service, and when the terminal is RedCap or eRedCap 2Rx, the terminal handover is allowed to be admitted in the first base station if the current cell is set to RedCap 2Rx or eRedCap 2Rx allowed access, and the indication of whether to allow RedCap terminal or eRedCap terminal emergency service access is set to yes, otherwise not allowed to be admitted, and the handover failure reason is determined, including at least one of: not allowed RedCap terminal emergency service, not allowed eRedCap terminal emergency service, not allowed RedCap terminal access, not allowed eRedCap terminal access.

[0128] Specifically, when the ARP value of the carried bearer belongs to emergency service and the terminal is RedCap or eRedCap 2Rx, if the current cell is forbidden access, the terminal access is rejected; otherwise, the terminal handover can be normally admitted in the first base station or the first base station set entity.

[0129] In some embodiments of the present application, the method further comprises the following steps: the first base station sends a handover request of the terminal to the second base station, wherein the handover request comprises the restriction of one or more radio access technologies for emergency service support, and the restriction of one or more radio access technologies for emergency service support is set for one or more public land mobile networks (PLMNs) or is set to be not associated with any PLMN.

[0130] According to the embodiments of the present application, another embodiment of a method for configuring a bearer service is also provided, wherein the execution subject is a first base station centralized entity. FIG. 2 is a flowchart of another method for configuring a bearer service according to an embodiment of the present application. As shown in FIG. 2, the method comprises the following steps:

[0131] In step S202, the first base station centralized entity receives a first core network message from a core network or a first inter-station message from a second base station, wherein the first core network message or the first inter-station message comprises at least one of the following: a restriction of one or more radio access technologies for emergency service support, whether a cell allows an IP multimedia subsystem (IMS) emergency bearer service for a reduced capability (RedCap) terminal, and whether the cell allows the IMS emergency bearer service for an enhanced RedCap (eRedCap) terminal.

[0132] In step S204, the first base station centralized entity receives a first intra-station message sent by a first base station separated entity, wherein the first intra-station message carries first restriction information, and the first restriction information is used to indicate at least one of the following: whether the cell allows the IMS emergency bearer service for the RedCap terminal, and whether the cell allows the IMS emergency bearer service for the eRedCap terminal.

[0133] The first restriction information is used to indicate whether an Internet of Things (IoT) terminal can access the network in an emergency service when a first base station cell is set as barred.

[0134] The method for configuring a bearer service in steps S202 to S204 of the embodiments of the present application is further described below.

[0135] In the embodiments of the present application, the first base station separated entity sends whether a cell is barred, an emergency service access indication (used to indicate whether a terminal can perform an emergency service in a restricted state), and an indication of whether a RedCap terminal or an eRedCap terminal is allowed to access an emergency service, etc. in a broadcast message. The specific steps are as follows.

[0136] In some embodiments of the present application, the first base station separation entity is configured to send, in the broadcast message, an indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services, wherein the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services is configured to indicate whether RedCap or eRedCap terminals support initiation of emergency services.

[0137] The indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services is configured to be set for one or more public land mobile networks (PLMNs) or not to be set for all PLMNs.

[0138] In embodiments of the present application, the first base station centralized entity can receive a first core network message sent by a core network, wherein the first core network message is configured to establish or modify context or bearer configuration information of a user, and the first core network message includes one or more radio access technologies (RATs) for which support for emergency services is limited.

[0139] The one or more RATs for which support for emergency services is limited are configured to be set for one or more public land mobile networks (PLMNs) or not to be set for any PLMNs.

[0140] Alternatively, the first base station centralized entity can also receive a first inter-station message sent by a second base station, wherein the first inter-station message includes the one or more RATs for which support for emergency services is limited.

[0141] The one or more RATs for which support for emergency services is limited are configured to be set for one or more public land mobile networks (PLMNs) or not to be set for any PLMNs.

[0142] After the first base station centralized entity receives the first core network message or the first inter-station message, the first base station centralized entity can determine whether to set dual connectivity for emergency services based on the one or more RATs for which support for emergency services is limited.

[0143] Specifically, the first base station centralized entity can determine whether a certain radio access technology can be used as a secondary node for dual connectivity for a terminal based on the one or more RATs for which support for emergency services is limited in the received first core network message or the first inter-station message and whether the terminal supports dual connectivity in its radio capabilities.

[0144] In some embodiments of the present application, in dual connectivity, the first base station is used as the master node of dual connectivity, and the third base station is used as the secondary node of dual connectivity, wherein the radio access technologies adopted by the first base station and the third base station are different, and whether the third base station is allowed to be the secondary node of dual connectivity is determined by one or more of the following: the restriction of the emergency service support of the radio access technology in the first core network message, or the restriction of the emergency service support of the radio access technology in the first inter-station message.

[0145] In some embodiments of the present application, in the case where the third base station is allowed to be the secondary node of dual connectivity, the radio access technology adopted by the third base station is one indicated in the multiple restriction information of the emergency service support of the radio access technology.

[0146] In addition, the first base station centralized entity can also receive a first intra-station message from the first base station separated entity, wherein the first intra-station message carries a broadcast message including an indication of whether the RedCap terminal or the eRedCap terminal is allowed to access the emergency service.

[0147] Alternatively, the first base station centralized entity can also receive a second inter-station message sent by the second base station, wherein the second inter-station message includes an indication of whether the RedCap terminal or the eRedCap terminal is allowed to access the emergency service.

[0148] In some embodiments of the present application, the method further comprises the following steps: the first base station centralized entity sends a third inter-station message to the second base station, wherein the third inter-station message includes an indication of whether the RedCap terminal or the eRedCap terminal is allowed to access the emergency service.

[0149] The first base station centralized entity receives a handover request message for the Internet of Things terminal sent by the second base station, wherein the acceptable scheme is as follows:

[0150] 1) In the case where the first base station centralized entity receives a handover request message for the Internet of Things terminal sent by the second base station, when the address resolution protocol (ARP) value of the carried bearer in the handover request message does not belong to the emergency service, the terminal handover is allowed to be accepted by the first base station centralized entity, i.e., the terminal handover can be normally accepted by the first base station centralized entity.

[0151] 2) In case the first set of base station entity receives the handover request message for the terminal of the Internet of Things sent by the second base station, when the ARP value of the carried bearer in the handover request message belongs to the emergency service, and when the terminal is RedCap or eRedCap 1Rx, in case the current cell is set to RedCap 1Rx or eRedCap 1Rx allowed access, and the indication of whether to allow RedCap terminal or eRedCap terminal emergency service access is set to yes, the terminal handover is allowed to be admitted by the first set of base station entity, otherwise it is not allowed to be admitted, and the handover failure reason is determined, including at least one of: not allowed RedCap terminal emergency service, not allowed eRedCap terminal emergency service, not allowed RedCap terminal access, not allowed eRedCap terminal access.

[0152] Specifically, if the ARP value of the carried bearer belongs to the emergency service and the terminal is RedCap or eRedCap 1Rx, if the current cell is not forbidden access, the terminal handover can be normally admitted by the first base station or the first set of base station entities; if the current cell is forbidden access, and the indication of allowing RedCap or eRedCap terminal emergency service access is configured, the terminal handover can be normally admitted by the first base station or the first set of base station entities; otherwise, the terminal access is rejected.

[0153] In some embodiments, if the ARP value of the carried bearer belongs to the emergency service and the terminal is RedCap (or eRedCap terminal), if the current cell is RedCap 1Rx (or eRedCap terminal) allowed access, and the indication of allowing RedCap (or eRedCap terminal) terminal emergency service access is configured, the terminal handover can be normally admitted by the first base station or the first set of base station entities; if the current cell is RedCap 1Rx (or eRedCap terminal) forbidden access, or the indication of not allowing RedCap (or eRedCap) terminal emergency service access is configured, the terminal access is rejected; if the current cell is RedCap 1Rx (or eRedCap terminal) forbidden access, and the indication of not allowing RedCap (or eRedCap) terminal emergency service access is configured, the terminal access is rejected.

[0154] 3) In case the first set of base station entities receives the handover request message for the terminal of the Internet of Things sent by the second base station, when the ARP value of the carried bearer in the handover request message belongs to the emergency service, and when the terminal is RedCap or eRedCap 2Rx, in case the current cell is set to RedCap 2Rx or eRedCap 2Rx to allow access, and in case the indication of whether to allow RedCap terminal or eRedCap terminal emergency service access is set to yes, the terminal handover is allowed to be admitted by the first set of base station entities, otherwise it is not allowed to be admitted, and the handover failure reason is determined, the handover failure reason including at least one of: not allowed RedCap terminal emergency service, not allowed eRedCap terminal emergency service, not allowed RedCap terminal access, not allowed eRedCap terminal access.

[0155] Specifically, when the ARP value of the carried bearer belongs to the emergency service and the terminal is RedCap or eRedCap 2Rx, if the current cell is forbidden to access, the terminal access is rejected; otherwise, the terminal handover can be normally admitted by the first base station or the first set of base station entities.

[0156] In some embodiments, when the ARP value of the carried bearer belongs to the emergency service and the terminal is RedCap (or eRedCap terminal), if the current cell is RedCap 2Rx (or eRedCap terminal) to allow access, and the indication of whether to allow RedCap terminal (or eRedCap terminal) emergency service access is set to yes, the terminal handover can be normally admitted by the first base station or the first set of base station entities; if the current cell is RedCap 2Rx (or eRedCap 2Rx) to not allow access, or the indication of whether to allow RedCap terminal (or eRedCap) terminal emergency service access is set to no, it is not allowed to be admitted; if the current cell is RedCap 2Rx (or eRedCap 2Rx) to not allow access, and the indication of whether to allow RedCap terminal (or eRedCap) terminal emergency service access is set to no, it is not allowed to be admitted.

[0157] In some embodiments of the present application, the method further comprises the following steps: the first set of base station entities sends a handover request of the terminal to the second base station, wherein the handover request includes one or more radio access technologies for emergency service support restrictions, and the one or more radio access technologies for emergency service support restrictions are set to support one or more public land mobile networks (PLMNs) or are set to not be associated with any PLMN.

[0158] It should be noted that the embodiment in this embodiment is a method embodiment corresponding to the configuration method of the bearer service shown in FIG. 1, therefore, the related explanation and description of the above-mentioned configuration method of the bearer service also apply to the embodiment of the present application, and will not be repeated here.

[0159] According to the embodiments of the present application, another embodiment of the configuration method of the bearer service whose execution subject is a terminal is also provided. FIG. 3 is a flowchart of another configuration method of a bearer service according to an embodiment of the present application, as shown in FIG. 3, the method comprises the following steps:

[0160] In step S302, the terminal receives at least one of whether to allow a RedCap terminal or an enhanced RedCap (eRedCap) terminal to access an emergency service, whether a cell is prohibited from being accessed, whether an eRedCap 1Rx is allowed to access, whether an eRedCap 2Rx is allowed to access, whether a RedCap 1Rx is allowed to access, and whether a RedCap 2Rx is allowed to access from a first base station broadcast message.

[0161] In step S304, the terminal does not allow to select or reselect the current cell in addition to the first case, the second case, the third case and the fourth case in the case of including an emergency call.

[0162] The first case is that the eRedCap 1Rx in the broadcast message is set to not allow access, one eRedCap terminal only supports a 1Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set to be prohibited from being accessed in the MIB message, the indication of whether to allow an eRedCap terminal to access an emergency service is set to yes, and in the case that the eRedCap only supports a half duplex FDD (Frequency Division Duplex) operation, the broadcast message indicates that the eRedCap half duplex is allowed.

[0163] The second case is that the eRedCap 2Rx in the broadcast message is set to not allow access, one eRedCap terminal only supports a 2Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set to be prohibited from being accessed in the MIB message, the indication of whether to allow an eRedCap terminal to access an emergency service is set to yes, and in the case that the eRedCap only supports a half duplex FDD operation, the broadcast message indicates that the eRedCap half duplex is allowed.

[0164] The third case is: the RedCap 1Rx in the broadcast message is set to not allow access, a RedCap terminal only supports a 1Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set to be forbidden to access in the MIB message, the indication of whether to allow the RedCap terminal to access emergency services is set to yes, and in the case that the RedCap only supports half-duplex FDD operation, the indication of whether to allow the RedCap half-duplex in the broadcast message is yes;

[0165] The fourth case is: the RedCap 2Rx in the broadcast message is set to not allow access, a RedCap terminal only supports a 2Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set to be forbidden to access in the MIB message, the indication of whether to allow the RedCap terminal to access emergency services is set to yes, and in the case that the RedCap only supports half-duplex FDD operation, the indication of whether to allow the RedCap half-duplex in the broadcast message is yes.

[0166] In some embodiments, the case of allowing selection or reselection of the current cell is not limited to the above four cases, and can be added as needed.

[0167] It should be noted that the embodiment in the present embodiment is a method embodiment corresponding to the configuration method of the bearer service shown in FIG. 1 and FIG. 2, and therefore the related explanations and descriptions of the configuration method of the bearer service described above also apply to the present embodiment, which will not be repeated here.

[0168] According to the embodiment of the present application, another embodiment of the configuration method of the bearer service is also provided. FIG. 4 is a flowchart of another configuration method of the bearer service according to an embodiment of the present application, as shown in FIG. 4, the method comprises the following steps:

[0169] In step S402, the second base station sends a first inter-station message to the first base station or a first base station centralized entity, wherein the first inter-station message contains at least one of: the limitation of one or more radio access technologies for emergency service support, whether the cell allows IP multimedia subsystem (IMS) emergency bearer service for a RedCap terminal, and whether the cell allows IMS emergency bearer service for an enhanced RedCap terminal.

[0170] The configuration method of the bearer service in step S402 of the embodiment of the present application is further described below.

[0171] In the embodiments of the present application, the second base station can send a first inter-station message to the first base station or a first base station centralized entity, wherein the first inter-station message comprises at least one of the following: a restriction of one or more radio access technologies for emergency service support, whether the cell allows IP multimedia subsystem (IMS) emergency bearer service for a reduced capability (RedCap) terminal, and whether the cell allows IMS emergency bearer service for an enhanced reduced capability (eRedCap) terminal.

[0172] The restriction of one or more radio access technologies for emergency service support is supported in one or more public land mobile networks (PLMNs) or is set to be not associated with any PLMN.

[0173] After the first base station or the first base station centralized entity receives the first inter-station message, the first base station or the first base station centralized entity can determine whether to set dual connectivity for emergency service according to the restriction of one or more radio access technologies for emergency service support.

[0174] In addition, in some embodiments of the present application, the method further comprises the following steps: the second base station sends a second inter-station message to the first base station or the first base station centralized entity, wherein the second inter-station message comprises an indication of whether a reduced capability (RedCap) terminal or an enhanced RedCap (eRedCap) terminal is allowed to access emergency service; and the indication of whether the RedCap terminal or the eRedCap terminal is allowed to access emergency service is used to indicate whether the RedCap terminal or the eRedCap terminal supports initiation of emergency service.

[0175] In some embodiments of the present application, the method further comprises the following steps: the second base station receives a third inter-station message sent by the first base station or the first base station centralized entity, wherein the third inter-station message comprises the indication of whether the RedCap terminal or the eRedCap terminal is allowed to access emergency service.

[0176] In the embodiments of the present application, the second base station can also send a handover request message for an Internet of Things (IoT) terminal to the first base station or the first base station centralized entity.

[0177] The first base station or the first base station centralized entity receives the handover request message for the IoT terminal sent by the second base station, wherein the following scheme can be accepted:

[0178] 1) When the address resolution protocol (ARP) value of the bearer carried in the handover request message does not belong to emergency service, the terminal handover is allowed to be accepted at the first base station or the first base station centralized entity, that is, the terminal handover can be normally accepted at the first base station or the first base station centralized entity.

[0179] 2) When the ARP value of the carried bearer in the handover request message belongs to emergency service, and when the terminal is RedCap or eRedCap 1Rx, the terminal is admitted at the first base station in the case that the current cell is set to RedCap 1Rx or eRedCap 1Rx allowing access, and the indication of whether to allow RedCap terminal or eRedCap terminal emergency service access is set to yes, otherwise it is not allowed to be admitted, wherein the cause of handover failure includes at least one of: not allowed RedCap terminal emergency service, not allowed eRedCap terminal emergency service, not allowed RedCap terminal access, not allowed eRedCap terminal access.

[0180] Specifically, if the ARP value of the carried bearer belongs to emergency service and the terminal is RedCap or eRedCap 1Rx, if the current cell is not forbidden access, the terminal handover can be normally admitted at the first base station or the first base station set entity; if the current cell is forbidden access, and the indication of allowing RedCap or eRedCap terminal emergency service access is configured, the terminal handover can be normally admitted at the first base station or the first base station set entity; otherwise, the terminal access is rejected.

[0181] In some embodiments, if the ARP value of the carried bearer belongs to emergency service and the terminal is RedCap (or eRedCap 1Rx), if the current cell is set to RedCap 1Rx (or eRedCap 1Rx) allowing access, and the indication of allowing RedCap (or eRedCap) terminal emergency service access is configured, the terminal handover can be normally admitted at the first base station or the first base station set entity; if the current cell is set to RedCap 1Rx (or eRedCap 1Rx) not allowing access, or the indication of allowing RedCap (or eRedCap) terminal emergency service access is configured, the terminal access is rejected; if the current cell is set to RedCap 1Rx (or eRedCap 1Rx) not allowing access, and the indication of allowing RedCap (or eRedCap) terminal emergency service access is configured, the terminal access is rejected.

[0182] 3) when the ARP value of the carried bearer in the handover request message belongs to the emergency service, and when the terminal is a RedCap or eRedCap 2Rx, the terminal is admitted at the first base station in the case that the current cell is set to RedCap 2Rx or eRedCap 2Rx to allow access, and the indication of whether to allow RedCap terminals or eRedCap terminals to access emergency services is set to yes, otherwise the terminal is not admitted, wherein the cause of the handover failure includes at least one of: RedCap terminal emergency service not allowed, eRedCap terminal emergency service not allowed, RedCap terminal not allowed to access, and eRedCap terminal not allowed to access.

[0183] Specifically, when the ARP value of the carried bearer belongs to the emergency service and the terminal is a RedCap or eRedCap 2Rx, if the current cell is forbidden to access, the terminal is rejected to access; otherwise, the terminal can be normally admitted at the first base station or in the first base station set.

[0184] In some embodiments, when the ARP value of the carried bearer belongs to the emergency service and the terminal is a RedCap (or eRedCap), if the current cell is set to RedCap 2Rx (or eRedCap 2Rx) to allow access, and the indication of whether to allow RedCap terminals (or eRedCap) to access emergency services is set to yes, the terminal can be normally admitted at the first base station or in the first base station set; if the current cell is set to RedCap 2Rx (or eRedCap 2Rx) to not allow access, or the indication of whether to allow RedCap terminals (or eRedCap) to access emergency services is set to no, the terminal is rejected to access; if the current cell is set to RedCap 2Rx (or eRedCap 2Rx) to not allow access, and the indication of whether to allow RedCap terminals (or eRedCap) to access emergency services is set to no, the terminal is rejected to access.

[0185] In some embodiments of the present application, the method further comprises the following steps: the second base station receives the handover request of the terminal sent by the first base station or the entity in the first base station set, wherein the handover request includes one or more radio access technologies for emergency service support restrictions, and the one or more radio access technologies for emergency service support restrictions are set in one or more public land mobile networks (PLMNs) or are set to be not associated with any PLMN.

[0186] It should be noted that the method embodiment in the present embodiment corresponds to the bearer service configuration method shown in FIG. 1, FIG. 2 and FIG. 3, and therefore the related explanations and descriptions of the above bearer service configuration method also apply to the present embodiment, which will not be repeated here.

[0187] According to the embodiment of the present application, an embodiment of a configuration system of a bearer service is further provided. Fig. 5 is a structural schematic diagram of a configuration system of a bearer service according to an embodiment of the present application. As shown in Fig. 5, the apparatus comprises a first base station 50 and a second base station 52, wherein the first base station 50 comprises a first base station centralized entity 500 and a first base station separated entity 502.

[0188] The first base station 50 or the first base station centralized entity 500 receives a first core network message sent by a core network or receives a first inter-station message sent by the second base station 52, wherein the first core network message or the first inter-station message comprises at least one of the following: a restriction of one or more radio access technologies on emergency service support, whether the cell allows IP multimedia subsystem (IMS) emergency bearer service for a reduced capability (RedCap) terminal, and whether the cell allows IMS emergency bearer service for an enhanced RedCap (eRedCap) terminal.

[0189] The first base station centralized entity 500 receives a first intra-station message sent by the first base station separated entity 502 or the first base station 50 receives a second inter-station message sent by the second base station 52, wherein the first intra-station message and the second inter-station message both carry first restriction information, and the first restriction information is used to indicate at least one of the following: whether the cell allows IMS emergency bearer service for a RedCap terminal, and whether the cell allows IMS emergency bearer service for an eRedCap terminal.

[0190] It should be noted that each module in the above configuration system of a bearer service can be a program module (for example, a program instruction set for implementing a certain specific function) or a hardware module. For the latter, it can be in the following forms, but is not limited to this: the forms of the above modules are all processors, or the functions of the above modules are implemented by a processor.

[0191] It should be noted that the configuration system of a bearer service provided in the embodiment can be used to execute the configuration method of a bearer service shown in Figs. 1, 2, 3 and 4, and thus the related explanations and descriptions of the above configuration method of a bearer service are also applicable to the present embodiment, which will not be repeated here.

[0192] The present application scheme will be further described below in combination with cases.

[0193] Case One

[0194] This case mainly describes that gNB1 (first base station) receives configuration information of emergency call for NR UE from core network AMF (Access and Mobility Management Function), wherein LTE (Long Term Evolution) is allowed to be added as a secondary node, so gNB1 adds LTE as a secondary node. When the terminal is ready to hand over to gNB2 (second base station), gNB1 sends relevant restriction information to gNB2, and the specific steps are as follows.

[0195] Step 1, gNB1 (first base station) or gNB1-DU (first base station separated entity) sends in the broadcast message: cell barred access indication is: NOT Barred (not barred), emergency service access indication is: supported (supported) or enabled;

[0196] Step 2, the terminal UE initiates emergency call service in gNB1, and the core network completes the authentication of the terminal;

[0197] Step 3, gNB1 receives the INITIAL CONTEXT SETUP REQUEST (initial context setup request) message, which includes: the ARP value in the emergency service bearer is 2, the 5G allowed emergency call is: PLMN1 and PLMN2, and the LTE allowed emergency call is: PLMN1;

[0198] Step 4, gNB1 determines that the terminal is an emergency call service according to the ARP value, and determines that the terminal can support emergency call service in a dual connection scenario according to the UE capability; wherein the PLMN where the UE currently resides is PLMN1;

[0199] Step 5, gNB1 adds LTE as a secondary cell of EN-DC for the UE;

[0200] Step 6, gNB1 receives the measurement report of the UE, and gNB1 sends a handover request message to gNB2, which carries information including: the ARP value in the emergency service bearer is 2, the 5G allowed emergency call is: PLMN1 and PLMN2, and the LTE allowed emergency call is: PLMN1.

[0201] Case two

[0202] This case mainly describes the process that gNB1 adds LTE as a secondary node from the configuration information of emergency call for NR UE received from core network gNB2. The specific steps are as follows.

[0203] Step 1, gNB1 or gNB1-DU sends in broadcast message: Cell Barred is not Barred, Emergency Services Access Indication is supported or enabled;

[0204] Step 2, UE initiates emergency call service in gNB1, and the core network completes the authentication of the terminal;

[0205] Step 3, gNB1 receives the Handover Request message sent by gNB2, which includes: the ARP value in the emergency service bearer is 2, the 5G allowed emergency call is: PLMN1 and PLMN2, and the LTE allowed emergency call is: PLMN1;

[0206] Step 4, gNB1 determines that the terminal is an emergency call service according to the ARP value, and determines that the terminal can support emergency call service in a dual connectivity scenario according to the UE capability; wherein the PLMN where the UE currently resides is PLMN1;

[0207] Step 5, gNB1 adds LTE as a secondary cell for EN-DC for the UE.

[0208] Case Three

[0209] This case mainly describes that the gNB1-CU (first base station centralized entity) receives the configuration information of the emergency call of the RedCap UE from the gNB1-DU (first base station separated entity). When the terminal is ready to hand over to gNB2, the gNB1-CU sends the related restriction information to gNB2. The establishment process of the F1 interface between the separated entity and the centralized entity (F1 Setup procedure: Successful Operation) is shown in FIG. 6, and the separated entity configuration update process (gNB-DU Configuration Update procedure: Successful Operation) is shown in FIG. 7. The specific steps are as follows.

[0210] Step 1, gNB1-DU sends in broadcast message: Cell Barred is Barred, whether RedCap terminal or eRedCap terminal emergency service access indication is supported or enabled;

[0211] Step 2, gNB1-CU receives the gNB1 internal message (i.e., the first intra-station message) from gNB1-DU, which carries the broadcast message including: Cell Barred is Barred, whether RedCap terminal or eRedCap terminal emergency service access indication is supported or enabled;

[0212] Step 3, the RedCap UE initiates an emergency call service in gNB1, and the core network completes the authentication of the terminal;

[0213] Step 4, gNB1 carries the following content in the Xn interface establishment process with gNB2: whether to allow the RedCap terminal or eRedCap terminal to access emergency services, indicated as: supported or enabled.

[0214] The scheme of the present application supports the configuration of dual connectivity function for non-RedCap terminals in emergency calls, so that the coverage quality of emergency call related services can be transmitted on the corresponding carrier; it is defined that 1Rx terminals can make emergency calls when the cell is prohibited, ensuring that wearable terminals such as electronic watches can still make emergency calls in special scenarios; it does not involve the impact on the terminal, and is a network side scheme, with good forward compatibility, easy network deployment and implementation.

[0215] The above embodiment numbers of the present application are only for description, not representing the pros and cons of the embodiments.

[0216] The structural diagram of one embodiment of the network device of the present disclosure is shown in FIG. 8. The network device includes a memory 801 and a processor 802. Among them: the memory 801 can be a disk, a flash memory or any other non-volatile storage medium. The memory is used to store the instructions in the corresponding embodiment of the above bearer service configuration method. The processor 802 is coupled to the memory 801 and can be implemented as one or more integrated circuits, such as a microprocessor or a microcontroller. The processor 802 is used to execute the instructions stored in the memory, which can achieve the purpose of supporting the emergency call of the RedCap terminal in the prohibited cell and the emergency call of the ordinary terminal in the dual connectivity scenario.

[0217] A communication system proposed by the present disclosure is shown in FIG. 9, including: a first base station 91 and a terminal 92, wherein the first base station can execute any one of the above bearer service configuration methods executed by the first base station, and the terminal can execute any one of the above bearer service configuration methods executed by the terminal.

[0218] In some embodiments, the first base station can be the first base station shown in FIG. 5, including a first base station centralized entity and a first base station separated entity.

[0219] In some embodiments, as shown in FIG. 9, the system further includes a second base station 93, which can execute any one of the above bearer service configuration methods executed by the second base station.

[0220] In the above-described embodiments of the present application, the description of each embodiment focuses on different aspects, and the parts not described in detail in a certain embodiment can be referred to the relevant description of other embodiments.

[0221] In several embodiments provided in the present application, it should be understood that the disclosed technical contents can be implemented by other ways. Among them, the above-described device embodiments are only schematic, for example, the division of the units can be a logical function division, and actual implementation can have another division way, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units or modules shown or discussed can be indirect coupling or communication connection through some interfaces, units or modules, which can be electrical or other forms.

[0222] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place or distributed to multiple units. Part or all of the units can be selected to achieve the purpose of the embodiment scheme according to actual needs.

[0223] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The above integrated unit can be realized in the form of hardware or in the form of software functional unit.

[0224] The integrated unit, if realized in the form of software functional unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or the part of the prior art that makes a contribution or the whole or part of the technical solutions can be embodied in the form of software product, which is stored in a storage medium and includes a plurality of instructions for making a computer device (which can be a personal computer, a server or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and various program code storage media.

[0225] The above is only the preferred embodiment of the present application, and it should be pointed out that for ordinary skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, which should be considered as the protection scope of the present application.

Claims

1. A method for configuring a bearer service, performed by a first base station, comprising: receiving a first inter-station message from a second base station, the first inter-station message including at least one of whether an IP Multimedia Subsystem, IMS, emergency bearer service is allowed for a reduced capability, RedCap, terminal in a cell, or whether the IMS emergency bearer service is allowed for an enhanced reduced capability, eRedCap, terminal in the cell; sending a second inter-station message including at least one of whether the IMS emergency bearer service is allowed for a RedCap terminal in the cell, or whether the IMS emergency bearer service is allowed for an eRedCap terminal in the cell. 2.The method of claim 1, further comprising: receiving a first core network message from a core network, the first core network message including at least one of whether the IMS emergency bearer service is allowed for a RedCap terminal in the cell, or whether the IMS emergency bearer service is allowed for an eRedCap terminal in the cell.

3. The method of configuring a bearer service according to claim 1 or 2, wherein, the receiving the first inter-station message from the second base station comprises: obtaining the first inter-station message by receiving a first broadcast message of the second base station, the first inter-station message being sent by the second base station through broadcasting.

4. The method of configuring a bearer service according to claim 1, 2 or 3, wherein, the second inter-station message is sent through a second broadcast message.

5. The method of claim 1-4, wherein, the whether the IMS emergency bearer service is allowed for a RedCap terminal in the cell in the first inter-station message is used to indicate whether the RedCap terminal supports initiation of an emergency service at the second base station; the whether the IMS emergency bearer service is allowed for a RedCap terminal in the cell in the first inter-station message is used to indicate whether the eRedCap terminal supports initiation of an emergency service at the second base station.

6. The method of configuring a bearer service according to any one of claims 1-4, wherein, the whether the IMS emergency bearer service is allowed for a RedCap terminal in the cell in the second inter-station message is used to indicate whether the RedCap terminal supports initiation of an emergency service at the first base station; the whether the IMS emergency bearer service is allowed for a RedCap terminal in the cell in the second inter-station message is used to indicate whether the eRedCap terminal supports initiation of an emergency service at the first base station.

7. The method of configuring a bearer service according to claim 1, wherein, the at least one of the first inter-station message or the second inter-station message further includes limitation information of one or more radio access technologies for emergency service support.

8. The method of configuring a bearer service according to claim 2, wherein, the first core network message further includes limitation information of one or more radio access technologies for emergency service support.

9. The method of configuring a bearer service according to claim 7 or 8, wherein, the limitation information of the one or more radio access technologies for emergency service support includes: support in one or more Public Land Mobile Network, PLMN, settings, or set to not associate any PLMN.

10. The method of configuring a bearer service according to claim 5 or 6, wherein, at least one of whether the RedCap terminal supports initiation of emergency services or whether the eRedCap terminal supports initiation of emergency services is set in one or more PLMNs or is set not to be associated with any PLMN, wherein, in the case of being set not to be associated with any PLMN, at least one of whether the RedCap terminal supports initiation of emergency services or whether the eRedCap terminal supports initiation of emergency services is applicable to all the PLMNs.

11. The method of claim 7 or 8, further comprising: determining whether to set dual connectivity for emergency services according to the restriction information of emergency service support of the one or more radio access technologies.

12. The method of claim 1-11, wherein at least one of the receiving the first inter-site message from the second base station or the sending the second inter-site message is performed by a centralized entity of the first base station; further comprising: the centralized entity of the first base station receives a first intra-site message sent by a split entity of the first base station, wherein the first intra-site message carries first restriction information, and the first restriction information is used to indicate whether the cell allows IMS emergency bearer service for RedCap terminals or at least one of whether the cell allows IMS emergency bearer service for eRedCap terminals.

13. A method of configuring a bearer service, performed by a terminal, comprising: obtaining a broadcast message from a first base station, wherein the broadcast message includes at least one of whether reduced capability RedCap terminals or enhanced reduced capability eRedCap terminals are allowed to access emergency services, whether the cell is barred, whether eRedCap 1Rx is allowed to access, whether eRedCap 2Rx is allowed to access, whether RedCap 1Rx is allowed to access, or whether RedCap 2Rx is allowed to access.

14. The method of claim 13, further comprising: according to the broadcast message, the terminal is allowed to select or reselect a cell of the first base station in one or more of the following cases when an emergency call occurs: eRedCap 1Rx is set to not allow access in the broadcast message, one eRedCap terminal only supports 1Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set to be barred in the MIB message, and the indication of whether eRedCap terminals are allowed to access emergency services is set to yes, and in the case of eRedCap only supporting half-duplex FDD operation, the broadcast message indicates that eRedCap half-duplex is allowed; The eRedCap 2Rx in the broadcast message is set to not allow access, an eRedCap terminal only supports a 2Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set to be forbidden to access in the MIB message, and the indication of whether to allow eRedCap terminal emergency service access is set to yes, and in the case of eRedCap only supporting half-duplex FDD operation, the indication of whether to allow eRedCap half-duplex in the broadcast message is yes; The RedCap 1Rx in the broadcast message is set to not allow access, a RedCap terminal only supports a 1Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set to be forbidden to access in the MIB message, and the indication of whether to allow RedCap terminal emergency service access is set to yes, and in the case of RedCap only supporting half-duplex FDD operation, the indication of whether to allow RedCap half-duplex in the broadcast message is yes; or The RedCap 2Rx in the broadcast message is set to not allow access, a RedCap terminal only supports a 2Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set to be forbidden to access in the MIB message, and the indication of whether to allow RedCap terminal emergency service access is set to yes, and in the case of RedCap only supporting half-duplex FDD operation, the indication of whether to allow RedCap half-duplex in the broadcast message is yes.

15. A method for configuring a bearer service, applied to a first base station, characterized in that, Comprise: The first base station receives a first core network message from a core network, or receives a first inter-station message from a second base station, wherein the first core network message or the first inter-station message contains at least one of: one or more radio access technologies for emergency service support restrictions, whether a cell allows IP multimedia subsystem (IMS) emergency bearer service for reduced capability (RedCap) terminals, and whether the cell allows IMS emergency bearer service for enhanced reduced capability (eRedCap) terminals.

16. The method of claim 15, further comprising: The first base station receives the first core network message sent by the core network, or receives the first inter-station message sent by the second base station; The first base station determines whether to set dual connectivity for emergency services according to the one or more radio access technology emergency service support restriction information. 17.The method of Claim 16, wherein in the dual connectivity, the first base station is configured to operate as a master node of the dual connectivity, and a third base station is configured to operate as a secondary node of the dual connectivity. Whether the third base station is allowed to be a secondary node of the dual connectivity is determined by the one or more radio access technology emergency service support restrictions in the first core network message or the first inter-station message.

18. The method of claim 17, wherein, in the case of allowing the third base station to be a secondary node of the dual connectivity, the wireless access technology adopted by the third base station is one indicated in the multiple restriction information in the one or more radio access technology emergency service support restrictions.

19. The method of claim 16-18, wherein the first core network message is used to establish or modify a context or bearer configuration information of a user.

20. The method of configuring a bearer service according to any of claims 15-19, wherein, The limitation of support for emergency services of the one or more radio access technologies is set for one or more public land mobile networks (PLMNs) or is set to be applicable for all PLMNs without association with any PLMN.

21. The method of configuring a bearer service according to any of claims 15-19, wherein, The method further comprises: The first base station sends an indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services in a broadcast message; The indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services is used to indicate whether RedCap terminals or eRedCap terminals support initiation of emergency services.

22. The method of configuring a bearer service according to claim 21, wherein, The indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services is set for one or more public land mobile networks (PLMNs) or is set to be applicable for all PLMNs without association with any PLMN.

23. The method of claim 22, further comprising: The first base station receives a second inter-station message sent by the second base station, wherein the second inter-station message includes the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services.

24. The method of configuring a bearer service according to claim 23, wherein, Further comprising: The first base station sends a third inter-station message to the second base station, wherein the third inter-station message includes the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services.

25. The method of configuring a bearer service according to claim 24, wherein, In a case where the first base station receives a handover request message for an Internet of Things terminal sent by the second base station, when an address resolution protocol (ARP) value of a bearer carried in the handover request message does not belong to emergency services, terminal handover is allowed to be admitted at the first base station.

26. The method of configuring a bearer service according to claim 25, wherein, In a case where the first base station receives a handover request message for an Internet of Things terminal sent by the second base station, when an ARP value of a bearer carried in the handover request message belongs to emergency services, and when the terminal is a RedCap terminal or an eRedCap 1Rx terminal, In a case where the current cell is set to allow access of RedCap 1Rx or eRedCap 1Rx, and the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services is set to yes, terminal handover is allowed to be admitted at the first base station, otherwise, admission is not allowed, and a handover failure cause is determined, the handover failure cause including at least one of: RedCap terminal emergency service not allowed, eRedCap terminal emergency service not allowed, RedCap terminal access not allowed, and eRedCap terminal access not allowed.

27. The method of configuring a bearer service according to claim 26, wherein, In a case where the first base station receives a handover request message for an Internet of Things terminal sent by the second base station, when an ARP value of a bearer carried in the handover request message belongs to emergency services, and when the terminal is a RedCap terminal or an eRedCap 2Rx terminal, In a case that the current cell is set to RedCap 2Rx or eRedCap 2Rx access is allowed, and the indication of whether RedCap terminal or eRedCap terminal emergency service access is allowed is set to yes, the terminal switching is allowed to be admitted at the first base station, otherwise, the admission is not allowed, and a handover failure cause is determined, the handover failure cause includes at least one of: RedCap terminal emergency service is not allowed, eRedCap terminal emergency service is not allowed, RedCap terminal access is not allowed, and eRedCap terminal access is not allowed.

28. The method of claim 27, further comprising: sending, by the first base station, a handover request of the terminal to the second base station, wherein the handover request includes one or more radio access technologies for emergency service support restrictions, and the one or more radio access technologies for emergency service support restrictions support one or more public land mobile networks (PLMNs) or are set to be not associated with any PLMN.

29. A method of configuring a bearer service, applied to a first base station centralized entity, comprising: receiving, by the first base station centralized entity, a first core network message from a core network or a first inter-station message from a second base station, wherein the first core network message or the first inter-station message includes at least one of: one or more radio access technologies for emergency service support restrictions, whether a cell allows IP multimedia subsystem (IMS) emergency bearer service for a reduced capability (RedCap) terminal, and whether the cell allows IMS emergency bearer service for an enhanced RedCap (eRedCap) terminal; receiving, by the first base station centralized entity, a first intra-station message sent by a first base station separated entity, wherein the first intra-station message carries first restriction information, and the first restriction information indicates at least one of whether the cell allows IMS emergency bearer service for a RedCap terminal and whether the cell allows IMS emergency bearer service for an eRedCap terminal.

30. The method of claim 29, further comprising: receiving, by the first base station centralized entity, a first core network message sent by a core network or a first inter-station message sent by a second base station; determining, by the first base station centralized entity, whether to set dual connectivity for emergency service according to the one or more radio access technologies for emergency service support restrictions.

31. The method of configuring a bearer service according to claim 30, wherein, In the dual connectivity, the first base station is used as a master node of the dual connectivity, and a third base station is used as a secondary node of the dual connectivity, wherein whether the third base station is allowed to be the secondary node of the dual connectivity is determined by the one or more radio access technologies for emergency service support restrictions in the first core network message or the first inter-station message.

32. The method of configuring a bearer service according to claim 31, wherein, In a case that the third base station is allowed to be the secondary node of the dual connectivity, a radio access technology used by the third base station is one indicated in the one or more radio access technologies for emergency service support restrictions.

33. The method of configuring a bearer service according to claim 30, wherein, The first core network message is used to establish or modify the context or bearer configuration information of a user.

34. The method of configuring a bearer service according to any of claims 29-33, wherein, The one or more radio access technologies support limitation of emergency service support in one or more public land mobile networks (PLMNs) or are set to be applicable to all PLMNs without association with any PLMN.

35. The method of claim 29-33, further comprising: The first base station centralized entity receives the first intra-station message from the first base station separated entity, wherein the first intra-station message carries an indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services in a broadcast message.

36. The method of configuring a bearer service according to claim 35, wherein, The first base station separated entity is configured to send an indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services in a broadcast message, wherein the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services is used to indicate whether RedCap or eRedCap terminals support initiation of emergency services.

37. The method of configuring a bearer service according to claim 36, wherein, The indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services supports configuration in one or more public land mobile networks (PLMNs) or is set to be applicable to all PLMNs without association with any PLMN.

38. The method of claim 37, further comprising: The first base station centralized entity receives a second inter-station message sent by a second base station, wherein the second inter-station message includes the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services.

39. The method of claim 38, further comprising: The first base station centralized entity sends a third inter-station message to the second base station, wherein the third inter-station message includes the indication of whether RedCap terminals or eRedCap terminals are allowed to access emergency services.

40. The method of configuring a bearer service according to claim 39, wherein, In a case where the first base station centralized entity receives a handover request message for an Internet of Things terminal sent by the second base station, when an address resolution protocol (ARP) value of a bearer carried in the handover request message does not belong to emergency services, terminal handover is allowed to be accepted at the first base station centralized entity.

41. The method of configuring a bearer service according to claim 40, wherein, In a case where the first base station centralized entity receives a handover request message for an Internet of Things terminal sent by the second base station, when an ARP value of a bearer carried in the handover request message belongs to emergency services, and when the terminal is a RedCap or eRedCap 1Rx, In a case that the current cell is set as RedCap 1Rx or eRedCap 1Rx allowed access, and the indication of whether RedCap terminal or eRedCap terminal emergency service access is allowed is set as yes, the terminal handover allows admission in the first base station set entity, otherwise, admission is not allowed, and a handover failure cause is determined, the handover failure cause includes at least one of: RedCap terminal emergency service not allowed, eRedCap terminal emergency service not allowed, RedCap terminal access not allowed, and eRedCap terminal access not allowed.

42. The method of configuring a bearer service according to claim 41, wherein, In a case that the first base station set entity receives a handover request message for an Internet of Things terminal sent by the second base station, when the ARP value of the carried bearer in the handover request message belongs to emergency service, and when the terminal is RedCap or eRedCap 2Rx, In a case that the current cell is set as RedCap 2Rx or eRedCap 2Rx allowed access, and the indication of whether RedCap terminal or eRedCap terminal emergency service access is allowed is set as yes, the terminal handover allows admission in the first base station set entity, otherwise, admission is not allowed, and a handover failure cause is determined, the handover failure cause includes at least one of: RedCap terminal emergency service not allowed, eRedCap terminal emergency service not allowed, RedCap terminal access not allowed, and eRedCap terminal access not allowed.

43. The method of claim 42, further comprising: The first base station set entity sends a handover request of the terminal to the second base station, wherein the handover request includes one or more radio access technologies for emergency service support restrictions, and the one or more radio access technologies for emergency service support restrictions support setting in one or more public land mobile networks (PLMNs) or setting as not associated with any PLMN.

44. A method of bearer service configuration, applied to a terminal, comprising: The terminal receives at least one of the following from the first base station broadcast message: an indication of whether RedCap terminal or eRedCap terminal emergency service access is allowed, whether a cell is prohibited from access, whether eRedCap 1Rx access is allowed, whether eRedCap 2Rx access is allowed, whether RedCap 1Rx access is allowed, and whether RedCap 2Rx access is allowed; The terminal does not allow selection or reselection of the current cell in a case including an emergency call, except for at least one of the first case, the second case, the third case, and the fourth case. The first case is that the eRedCap 1Rx in the broadcast message is set as not allowing access, an eRedCap terminal only supports a 1Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set as forbidden access in the MIB message, the indication of whether to allow eRedCap terminal emergency service access is set as yes, and in the case that eRedCap only supports half-duplex FDD operation, the indication of whether to allow eRedCap half-duplex in the broadcast message is set as yes. The second case is that the eRedCap 2Rx in the broadcast message is set as not allowing access, an eRedCap terminal only supports a 2Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set as forbidden access in the MIB message, the indication of whether to allow eRedCap terminal emergency service access is set as yes, and in the case that eRedCap only supports half-duplex FDD operation, the indication of whether to allow eRedCap half-duplex in the broadcast message is set as yes. The third case is that the RedCap 1Rx in the broadcast message is set as not allowing access, a RedCap terminal only supports a 1Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set as forbidden access in the MIB message, the indication of whether to allow RedCap terminal emergency service access is set as yes, and in the case that RedCap only supports half-duplex FDD operation, the indication of whether to allow RedCap half-duplex in the broadcast message is set as yes. The fourth case is that the RedCap 2Rx in the broadcast message is set as not allowing access, a RedCap terminal only supports a 2Rx channel, the current cell is an acceptable cell and the selection condition of the cell is met, the cell is not set as forbidden access in the MIB message, the indication of whether to allow RedCap terminal emergency service access is set as yes, and in the case that RedCap only supports half-duplex FDD operation, the indication of whether to allow RedCap half-duplex in the broadcast message is set as yes.

45. A method for configuring a bearer service, applied to a second base station, comprising: sending, by the second base station, a first inter-station message to a first base station or a first base station centralized entity, wherein the first inter-station message comprises at least one of: a restriction of support for emergency services of one or more radio access technologies, whether the cell allows IP multimedia subsystem (IMS) emergency bearer service for a reduced capability (RedCap) terminal, and whether the cell allows IMS emergency bearer service for an enhanced RedCap (eRedCap) terminal.

46. The method of configuring a bearer service according to claim 45, wherein, The restriction of support for emergency services of the one or more radio access technologies is set for one or more public land mobile networks (PLMNs) or is set as not associated with any PLMN.

47. The method for configuring a bearer service of claim 46, further comprising: The second base station sends a second inter-station message to the first base station or the first base station centralized entity, wherein the second inter-station message comprises an indication of whether a RedCap terminal or an enhanced RedCap (eRedCap) terminal is allowed to access emergency services. The indication of whether the RedCap terminal or the eRedCap terminal is allowed to access emergency services indicates whether the RedCap terminal or the eRedCap terminal supports initiation of emergency services.

48. The method of claim 47, further comprising: The second base station receives a third inter-station message sent by the first base station or the first base station centralized entity, wherein the third inter-station message comprises the indication of whether the RedCap terminal or the eRedCap terminal is allowed to access emergency services.

49. The method of claim 48, further comprising: The second base station sends a handover request message for an Internet of Things (IoT) terminal to the first base station or the first base station centralized entity.

50. The method of configuring a bearer service according to claim 49, wherein, When an address resolution protocol (ARP) value of a bearer carried in the handover request message does not belong to emergency services, terminal handover is allowed to be admitted at the first base station or the first base station centralized entity.

51. The method of configuring a bearer service according to claim 50, wherein, When the ARP value of the bearer carried in the handover request message belongs to emergency services, and when the terminal is a RedCap or an eRedCap 1Rx, In a case where a current cell is set to RedCap 1Rx or eRedCap 1Rx access is allowed, and the indication of whether the RedCap terminal or the eRedCap terminal is allowed to access emergency services is set to yes, terminal handover is allowed to be admitted at the first base station, otherwise, admission is not allowed, wherein a handover failure cause comprises at least one of RedCap terminal emergency services not allowed, eRedCap terminal emergency services not allowed, RedCap terminal access not allowed, and eRedCap terminal access not allowed.

52. The method of configuring a bearer service according to claim 51, wherein, When the ARP value of the bearer carried in the handover request message belongs to emergency services, and when the terminal is a RedCap or an eRedCap 2Rx, In a case where a current cell is set to RedCap 2Rx or eRedCap 2Rx access is allowed, and the indication of whether the RedCap terminal or the eRedCap terminal is allowed to access emergency services is set to yes, terminal handover is allowed to be admitted at the first base station, otherwise, admission is not allowed, wherein a handover failure cause comprises at least one of RedCap terminal emergency services not allowed, eRedCap terminal emergency services not allowed, RedCap terminal access not allowed, and eRedCap terminal access not allowed.

53. The method of claim 52, further comprising: The second base station receives a handover request of a terminal sent by the first base station or the first base station centralized entity, wherein the handover request comprises one or more radio access technologies for emergency service support restrictions, and the one or more radio access technologies for emergency service support restrictions support one or more public land mobile network (PLMN) settings or are set to be not associated with any PLMN. 54.A network device comprising: a memory; and a processor coupled to the memory, the processor configured to perform the method of any one of claims 1-53 based on instructions stored in the memory. 55.A computer-readable storage medium having computer instructions stored thereon, the instructions, when executed by a processor, implement the method of any one of claims 1-53. 56.A computer program product comprising computer programs or instructions, the computer programs or instructions, when executed by a processor, implement the method of any one of claims 1-53.

57. A configuration system for a bearer service, comprising: a first base station and a second base station, wherein the first base station comprises: a first base station centralized entity and a first base station separated entity, the first base station or the first base station centralized entity receives a first core network message sent by a core network or a first inter-station message sent by the second base station, wherein the first core network message or the first inter-station message comprises at least one of one or more radio access technologies for emergency service support restrictions, whether a cell allows IP multimedia subsystem (IMS) emergency bearer service for a reduced capability (RedCap) terminal, and whether the cell allows IMS emergency bearer service for an enhanced RedCap (eRedCap) terminal; the first base station centralized entity receives a first intra-station message sent by the first base station separated entity or the first base station receives a second inter-station message sent by the second base station, wherein the first intra-station message and the second inter-station message both carry first restriction information, and the first restriction information indicates at least one of whether the cell allows IMS emergency bearer service for a RedCap terminal and whether the cell allows IMS emergency bearer service for an eRedCap terminal. 58.A communication system comprising: a first base station configured to perform the bearer service configuration method of any one of claims 1-12 and 15-28; and a terminal configured to perform the bearer service configuration method of any one of claims 13, 14, and 44. 59.The communication system of claim 58, further comprising:

60. The communication system of claim 58 or 59, wherein, a second base station configured to perform the bearer service configuration method of any one of claims 45-53. the first base station comprises: a first base station centralized entity configured to perform the bearer service configuration method of any one of claims 29-43; and a first base station separated entity configured to perform the bearer service configuration method of any one of claims 29-43. A first base station separation entity configured to send, in a broadcast message, an indication of whether RedCap terminals or eRedCap terminals are allowed emergency services access, wherein the indication of whether RedCap terminals or eRedCap terminals are allowed emergency services access is used to indicate whether RedCap or eRedCap terminals support initiation of emergency services. A first base station separation entity configured to send, in a broadcast message, an indication of whether RedCap terminals or eRedCap terminals are allowed emergency services access, wherein the indication of whether RedCap terminals or eRedCap terminals are allowed emergency services access is used to indicate whether RedCap or eRedCap terminals support initiation of emergency services. A first base station separation entity configured to send, in a broadcast message, an indication of whether RedCap terminals or e

Images