Network configuration method and communication device

Abstract

A network configuration method and a communication device, the method comprising: if a terminal device has subscribed to NSA dual connectivity and first capability information indicates that the terminal device does not support first dual connectivity, sending a second message to a network device to indicate that second capability information of the terminal device is not queried and initial context information of the terminal device is established; receiving a third message from the network device, the third message comprising initial context information established by the network device; the initial context information comprising network configuration information corresponding to a second type of network device of the terminal device and not comprising network configuration information corresponding to a first type of network device of the terminal device. Wherein, the dual connectivity comprises the first dual connectivity and the second dual connectivity, the first dual connectivity being dual connectivity in which a primary base station and a secondary base station of the terminal device are both the first type of network device; the second dual connectivity being dual connectivity in which the primary base station of the terminal device is the second type of network device and the secondary base station is the first type of network device. By using the present application, the communication quality of the terminal device can be ensured.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a network configuration method and a communication device. Background Technology

[0002] Fifth-generation mobile communication (5G) supports both standalone (SA) and non-standalone (NSA) architectures. NSA refers to the architecture used for 5G network deployment within the existing infrastructure of fourth-generation mobile communication (4G).

[0003] According to the protocol requirements, a terminal device can only function normally under the NSA architecture and provide NSA services if the capability information it reports indicates support for both Dual Connectivity with New Radio (DCNR) and EUTRN-New Radio Dual Connectivity (ENDC). In abnormal situations such as terminal overheating protection, the terminal device may choose to report that it does not support DCNR. In this case, if the terminal device has already reported support for ENDC, it may cause service anomalies on 4G or 5G networks, such as dropped calls, thus affecting the communication quality of the terminal device. Summary of the Invention

[0004] This application provides a network configuration method and a communication device that can ensure the communication quality of terminal devices.

[0005] In a first aspect, embodiments of this application provide a network configuration method, which can be executed by a mobility management device or by a device compatible with the mobility management device, such as a processor, chip, or chip system. The method may include: upon receiving a first message from a network device, obtaining subscription service information of a terminal device from a home management device, the first message including first capability information of the terminal device; if the first capability information indicates that the terminal device does not support first dual connectivity, and the subscription service information indicates that the terminal device has subscribed to NSA dual connectivity, sending a second message to the network device, the second message being used to request the network device to establish initial context information for the terminal device, and the second message indicating that the network device does not query the second capability information of the terminal device; wherein the second capability information is used to indicate whether the terminal device supports or does not support second dual connectivity; receiving a third message from the network device, the third message including initial context information, the initial context information including network configuration information of the terminal device corresponding to a second type of network device, but not including network configuration information of the terminal device corresponding to a first type of network device. The dual connectivity includes a first dual connectivity and a second dual connectivity. The first dual connectivity is a dual connectivity in which both the main base station and the auxiliary base station of the terminal device are Class I network devices. The second dual connectivity is a dual connectivity in which the main base station of the terminal device is a Class II network device and the auxiliary base station of the terminal device is a Class I network device.

[0006] As can be seen, when a terminal device has subscribed to NSA dual connectivity and the reported first capability information indicates that the terminal device does not support the first type of dual connectivity, the mobility management device can proactively instruct the network device not to query whether the terminal device supports the second type of dual connectivity. This ensures that the initial context information established by the network device includes the network configuration information of the terminal device corresponding to the second type of network device, but does not include the network configuration information of the terminal device corresponding to the first type of network device. In other words, the terminal device is not configured with the network configuration information required for dual connectivity. Based on this, the terminal device can communicate more securely and stably with the mobility management device through the second type of network device, ensuring the communication quality of the terminal device, and avoiding NSA dual connectivity, thereby preventing call drops in NSA dual connectivity scenarios.

[0007] In one possible implementation, the above method may further include: communicating with the terminal device based on the established initial context information.

[0008] It is evident that the mobile management device and the terminal device communicate based on the established initial context information, which can ensure the communication quality of the terminal device.

[0009] In one possible implementation, the first message may further include the identity information of the terminal device; the method may further include: sending authentication request information to the home management device, the authentication request information including the identity information of the terminal device; receiving authentication response information from the home management device, the authentication response information being used to instruct the terminal device to pass identity authentication.

[0010] As can be seen, the home management device can authenticate the terminal device based on the terminal device's identity information, thereby facilitating the mobile management device to obtain the terminal device's subscription service information from the home management device.

[0011] In one possible implementation, the method for obtaining subscription service information of a terminal device from a home management device may specifically include: sending subscription query information to the home management device, the subscription query information including the identity information of the terminal device; and receiving subscription query response information from the home management device, the subscription query response information including the subscription service information of the terminal device.

[0012] As can be seen, the mobile management device obtains the terminal device's subscription service information from the home management device, thereby determining that the terminal device has subscribed to NSA dual connectivity.

[0013] Secondly, embodiments of this application provide a network configuration method, which can be executed by a network device or by a device matched with the network device, such as a processor, chip, or chip system. The method may include: receiving a second message from a mobility management device, the second message corresponding to first capability information, the second message being used to request the establishment of initial context information for a terminal device, and the second message instructing the network device not to query the second capability information of the terminal device; obtaining radio capability information of the terminal device from the terminal device according to the second message, the radio capability information not including the second capability information; generating initial context information of the terminal device according to the radio capability information; and sending a third message to the mobility management device, the third message including the initial context information of the terminal device. The second capability information is used to indicate whether the terminal device supports or does not support second dual connectivity, where the second dual connectivity is a dual connectivity where the terminal device's primary base station is a second type of network device and the terminal device's secondary base station is a first type of network device; the initial context information includes network configuration information of the terminal device corresponding to the second type of network device, but does not include network configuration information of the terminal device corresponding to the first type of network device.

[0014] As can be seen, the network device, based on the received second message, can establish initial context information for the terminal device without querying whether the terminal device supports second dual connectivity, and based on the queried wireless capability information of the terminal device. This initial context information includes the network configuration information of the terminal device corresponding to the second type of network device, but not the network configuration information of the terminal device corresponding to the first type of network device. In other words, the network device does not need to configure the network configuration information required for NSA dual connectivity for the terminal device. Based on this, it helps the terminal device and the mobility management device to conduct more secure and stable communication through the second type of network device, ensuring the communication quality of the terminal device, and the terminal device will not perform NSA dual connectivity, thus avoiding call drops in NSA dual connectivity scenarios.

[0015] In one possible implementation, a fourth message is sent to the terminal device, which instructs the terminal device to report radio capability information, which does not include the second capability information; and the terminal device receives radio capability information.

[0016] It is evident that network devices can obtain wireless capability information from terminal devices through the fourth message. In other words, network devices can instruct terminal devices not to report the second capability information through the fourth message.

[0017] In one possible implementation, the method may further include: sending Radio Resource Control (RRC) connection reconfiguration information to the terminal device, the RRC connection reconfiguration information including initial context information. The method for sending a third message to the mobility management device may further include: sending a third message to the mobility management device upon receiving RRC connection reconfiguration completion information from the terminal device.

[0018] It is evident that network devices can establish initial context information through the RRC connection reconfiguration process of terminal devices.

[0019] In one possible implementation, the method may further include: receiving attachment request information from a terminal device, the attachment request information including first capability information of the terminal device; and sending a first message to a mobility management device, the first message including the first capability information.

[0020] It is evident that the network device can obtain the terminal device's first capability information through the terminal device's attach request information, and forward the first capability information to the mobility management device through the first message.

[0021] Thirdly, embodiments of this application provide a communication device that includes modules / units for performing any of the methods described in the first aspect and its possible implementations.

[0022] Fourthly, embodiments of this application provide a communication device comprising a module / unit for performing any of the methods described in the second aspect and its possible implementations.

[0023] Fifthly, embodiments of this application provide a communication device. This device can be a mobility management device, a chip, chip system, or processor that supports the mobility management device in implementing the above-described methods, or a logic node, logic module, or software capable of implementing all or part of the terminal functions. The communication device can also be a chip system. This communication device can execute the methods described in the first aspect. The functions of the communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above-described functions. These units can be software and / or hardware. The operations performed by the communication device and its beneficial effects can be found in the methods described in the first aspect and their beneficial effects described above; repeated descriptions will not be repeated.

[0024] Sixthly, embodiments of this application provide a communication device. This device can be a network device, a chip, chip system, or processor that supports the network device in implementing the above-described methods, or a logical node, logical module, or software capable of implementing all or part of the network device's functions. The communication device can also be a chip system. This communication device can execute the methods described in the second aspect. The functions of the communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above-described functions. These units can be software and / or hardware. The operations performed by the communication device and its beneficial effects can be found in the methods described in the second aspect above, and repeated descriptions will not be repeated here.

[0025] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program, the computer program including program instructions that, when executed on a communication device, cause the method executed by the mobility management device as described in the first aspect to be implemented; or cause the method executed by the network device as described in the second aspect to be implemented.

[0026] Eighthly, embodiments of this application provide a computer program product that, when executed, causes the method executed by the mobility management device as described in the first aspect to be implemented; or causes the method executed by the network device as described in the second aspect to be implemented.

[0027] Ninthly, embodiments of this application provide a communication system, including a communication device (such as a mobility management device) for performing the method described in the first aspect and a communication device (such as a network device) for performing the method described in the second aspect. Attached Figure Description

[0028] Figure 1 This is a schematic diagram of the structure of a communication system provided in an embodiment of this application;

[0029] Figure 2 These are schematic diagrams illustrating two NSA dual-connection schemes provided in the embodiments of this application;

[0030] Figure 3 This is a schematic diagram of a process for adding a secondary base station according to an embodiment of this application;

[0031] Figure 4 This is a flowchart illustrating a network configuration method provided in an embodiment of this application;

[0032] Figure 5 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0033] Figure 6 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0034] The embodiments of this application will now be described with reference to the accompanying drawings.

[0035] The terms "first," "second," "third," and "fourth," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such processes, methods, products, or apparatus.

[0036] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0037] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0038] To better understand the embodiments of this application, the system architecture involved in the embodiments of this application will be described first below:

[0039] This application's embodiments can be applied to long-term evolution (LTE) systems, 4th generation mobile communication (4G) systems, 5th generation mobile communication (5G) systems, 6th generation mobile communication (6G) systems, and other communication systems evolving after 5G, as well as satellite communication and short-range wireless communication systems. The wireless communication systems mentioned in this application's embodiments include, but are not limited to, the three major application scenarios of 5G / 6G mobile communication systems: enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), and massive machine-type communication (mMTC), long-range (LoRa) systems, or vehicle-to-everything (V2X) systems. The wireless communication system may include one or more network devices and one or more terminal devices.

[0040] The following is based on Figure 1 The system architecture shown is illustrated as an example. The communication system 1000 includes a radio access network (RAN) 100 and a core network (CN) 200. The RAN 100 includes at least one network device (such as...). Figure 1 110a and 110b (collectively referred to as 110) and at least one terminal device (such as Figure 1 RAN 100, denoted as RAN 120a-120j, is collectively referred to as RAN 120. RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment. Figure 1(Not shown in the image). Terminal device 120 is connected to network device 110 wirelessly. Network device 110 is connected to core network 200 wirelessly or via wired connection. The core network device in core network 200 and network device 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0041] The core network 200 is primarily responsible for providing device connectivity, managing the devices, and carrying services, as well as providing an interface to external networks as the bearer network. The core network 200 can be an LTE core network, a 4G core network, a 5G core network, or a 6G core network, etc., and this application does not limit this. The core network 200 may include one or more core network devices. Figure 1 As shown, the core network 200 may include a mobility management device 201 and a home management device 202. The mobility management device 201 is mainly used for access control and mobility management of terminal devices. The home management device 202 is mainly used for authentication and authorization of terminal devices, subscription management, etc.

[0042] For example, if the core network 200 is a 4G core network or an LTE core network, then the mobility management device 201 can be a mobility management entity (MME) device, or an MME network element; the home management device 202 can be a home subscriber server (HSS), or an HSS network element. The MME is primarily responsible for mobility management, bearer management, user authentication, and the selection of the serving gateway (SGW) and packet network gateway (PGW). The HSS is primarily responsible for managing user subscription data and mobile user location information. If the core network 200 is a 5G core network, then the mobility management device 201 can be an access and mobility management function (AMF) network element, and the home management device 202 can be a unified data management (UDM) network element.

[0043] It should be noted that RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, or evolutionary systems beyond 5G (e.g., 6G mobile communication systems). RAN 100 can also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (CRAN), etc. RAN 100 can also be a communication system that integrates two or more of the above systems. It should be stated that... Figure 1 The number of network devices, terminal devices, and core network devices shown is merely illustrative and should not be considered a specific limitation of this application. The terminal devices and network devices involved in the system architecture will be described in detail below.

[0044] I. Terminal Equipment

[0045] Terminal equipment, also known as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., is a device used to provide voice or data connectivity to users, and can also be an Internet of Things (IoT) device. For example, terminal equipment includes handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, terminal devices can include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), in-vehicle equipment (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), satellite terminals, virtual reality (VR) devices, augmented reality (AR) devices, smart point-of-sale (POS) machines, customer-premises equipment (CPE), wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, and flying equipment (such as intelligent robots, hot air balloons, drones, airplanes), etc. Terminal devices can also be other devices with terminal functions; for example, a terminal device can also be a device that performs terminal functions in D2D communication.

[0046] The embodiments of this application do not limit the device form of the terminal. The device used to implement the functions of the terminal device can be the terminal device itself; it can also be a device that supports the terminal device in implementing the functions, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete components.

[0047] II. Network Equipment

[0048] Network devices are nodes in a radio access network (RAN), also known as access network devices or RAN nodes (or devices). Network devices help terminal devices achieve wireless access. Multiple network devices 110 in the communication system 1000 can be nodes of the same type or different types. In some scenarios, the roles of network devices 110 and terminal devices 120 are relative, for example... Figure 1 Network element 120i can be a helicopter or a drone, and it can be configured as a mobile base station. For terminal devices 120j that access RAN 100 through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal device. Network device 110 and terminal device 120 are sometimes referred to as communication devices, for example... Figure 1 Network elements 110a and 110b can be understood as communication devices with base station functions, while network elements 120a-120j can be understood as communication devices with terminal functions.

[0049] In one possible scenario, network equipment can be a base station, an evolved NodeB (eNodeB), a transmitting and receiving point (TRP), a transmitting point (TP), a next-generation NodeB (gNB), a next-generation base station in a 6th-generation (6G) mobile communication system, a base station in a future mobile communication system, a satellite, an integrated access and backhaul (IAB) node, or access network equipment in a mobile switching center non-terrestrial network (NTN) communication system. This means it can be deployed on high-altitude platforms or satellites. Access network equipment can be a macro base station (such as...). Figure 1 110a), micro base stations or indoor stations (such as Figure 1Access network equipment can be 110b), relay nodes or donor nodes, or wireless controllers in CRAN scenarios. It can also function as a base station in device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, drone communication, or machine-to-machine (M2M) communication. Optionally, access network equipment can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in vehicle-to-everything (V2X) technology, the access network equipment can be a roadside unit (RSU).

[0050] All or part of the functions of the network device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform). The network device in this application can also be a logical node, logical module, or software capable of implementing all or part of the functions of an access network device.

[0051] In another possible scenario, multiple network devices collaborate to assist terminal devices in achieving wireless access, with each network device performing a portion of the base station's functions. For example, network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs). CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). It is understood that network devices can be CU nodes, DU nodes, or devices comprising both CU and DU nodes. Furthermore, CUs can be classified as network devices in the access network (RAN) or the core network (CN), without limitation.

[0052] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0053] In this embodiment, the form of the network device is not limited. The device used to implement the function of the network device can be the network device itself, or it can be a device that supports the network device in implementing the function, such as a chip system. The device can be installed in the network device or used in conjunction with the network device.

[0054] To facilitate understanding of this solution, some terms used in the embodiments of this application will be explained below, so that those skilled in the art can understand them. This part is only for ease of understanding and should not be regarded as a specific limitation of this application.

[0055] 1. Non-standalone (NSA) networking

[0056] Non-Standalone (NSA) networking refers to the deployment of 5G networks using existing 4G infrastructure. 5G carriers based on the NSA architecture only carry user data; control signaling is still transmitted through the 4G network.

[0057] NSA terminal refers to a terminal device that supports NSA. In other words, an NSA terminal refers to a terminal device that has subscribed to NSA dual connectivity, supports non-standalone (NSA) networking architecture, and supports dual connectivity under NSA networking architecture.

[0058] 2. Dual-connectivity (DC)

[0059] Dual connectivity refers to a terminal device maintaining a connection with two base stations simultaneously. Dual connectivity technology between LTE and 5G networks (or between 4G and 5G networks) can be called LTE / 5G dual connectivity. LTE / 5G dual connectivity technology can be used to achieve interconnection between LTE and 5G systems, thereby improving the radio resource utilization of the entire mobile network system, reducing system handover latency, and improving user and system performance. Specifically, through LTE / 5G dual connectivity technology, in the early stages of 5G development, rapid 5G deployment can be achieved based on the existing LTE core network; in the later stages, comprehensive network coverage can be achieved through joint LTE and 5G networking, improving the radio resource utilization of the entire network system, reducing system handover latency, and improving system performance.

[0060] NSA dual connectivity refers to dual connectivity in a non-standalone (NSA) network architecture. NSA dual connectivity can include Evolved UTRA NR dual-connectivity (ENDC) and dual connectivity with new radio (DCNR).

[0061] (1)ENDC

[0062] ENDC indicates dual connectivity to both 4G and 5G networks. For an example, please refer to [link to example]. Figure 2 In (a) of the diagram, the primary base station of the terminal device is a 4G base station, and the secondary base station is a 5G base station. Both the primary and secondary base stations are connected to the 4G core network. The primary base station can also be referred to as a master node (MN) or a main evolved node base station (MeNB). The secondary base station can also be referred to as a secondary node (SN) or a secondary next-generation node base station (SgNB).

[0063] The ENDC capability of a terminal device can be used to indicate whether the terminal device supports ENDC. The network device can query the ENDC capability of the terminal device. Correspondingly, the terminal device can report its ENDC capability to the network device. For example, the network device can send air interface capability query information to the terminal device to query its ENDC capability; upon receiving the air interface capability query information, the terminal device can send wireless capability information to the network device, which may include the ENDC capability. For example, the wireless capability information may include an ENDC field, which can be used to indicate the terminal device's ENDC capability. For instance, a value of 0 for the ENDC field indicates that the terminal device does not support ENDC; a value of 1 for the ENDC field indicates that the terminal device supports ENDC.

[0064] (2) DCNR

[0065] DCNR represents dual connectivity between two 5G networks on different frequency bands. Both the primary and secondary base stations of the terminal device are 5G base stations, and both are connected to the 5G core network. For an example, please refer to [link to example]. Figure 2 In (b), the main base station of the terminal equipment can be a 5G base station using a frequency band below 6GHz (450MHz to 6GHz) (which can be called a 5G Sub6G base station), and the auxiliary base station can be a 5G millimeter wave base station.

[0066] The DCNR capability of a terminal device can be used to indicate whether the terminal device supports DCNR. After the terminal device accesses the 4G network, it can report its DCNR capability to the mobility management device through the network device. For example, the terminal device can report network capability information to the network device, which may include the DCNR capability. The network device can forward this network capability information to the mobility management device. Upon receiving the network capability information, the mobility management device can determine whether the terminal device supports DCNR based on the DCNR capability. For example, the network capability information may include a DCNR field, the value of which indicates the terminal device's DCNR capability; for example, a DCNR field value of 1 indicates that the terminal device supports DCNR; a DCNR field value of 0 indicates that the terminal device supports DCNR.

[0067] According to the agreement, terminal devices need to report support for DCNR to the core network's mobility management device and support for ENDC to the network device in order to function properly under the NSA architecture. Under certain abnormal circumstances (such as terminal overheat protection), terminal devices may choose to report no support for DCNR. In this case, the terminal device cannot function properly under the NSA architecture, such as being unable to perform NSA dual connectivity.

[0068] 3. Non-access stratum (NAS)

[0069] The NAS layer, acting as a functional layer between terminal devices and core network equipment (such as the MME), supports signaling and data transmission between these devices. The main functions of the NAS layer include mobility management, call control, session management, and identity management. For example, it handles Evolved Packet System (EPS) bearer management, authentication, and mobility management in the idle state (ECM-IDLE state) of EPS connection management mode. It's important to note that signaling and data transmission between terminal devices and network equipment, or between network equipment and core network equipment, cannot occur through the NAS layer.

[0070] Data and signaling transmitted at the NAS layer are referred to as NAS messages; that is, the signaling and data transmitted between terminal devices and mobility management devices are called NAS messages. NAS messages can be divided into EPS mobility management (EMM) messages and EPS session management (ESM) messages. EMM includes modules such as attach and detach. ESM includes modules such as network-side activation, deactivation, modification of EPS bearer context, and terminal device resource requests.

[0071] 4. Evolved Radio Access Bearer (E-RAB)

[0072] E-RAB refers to the user plane bearer, used for transmitting voice, data, and multimedia services between terminal equipment and the core network. E-RAB establishment is initiated by the core network. Once E-RAB is successfully established, a basic service is established, and the terminal equipment can begin using the service.

[0073] The LTE E-RAB starts from the Serving Gateway (SGW) and ends at the terminal equipment. It consists of the S1-U bearer and the data radio bearer (DRB) connected in series. Service data entering the LTE system is mainly transmitted through the E-RAB.

[0074] When a terminal device is in a connected state, i.e., after its context has been established in the network device, E-RAB can establish, modify, and release Radio Access Network (E-UTRAN) resources for user plane transmissions. In LTE, resource allocation, modification, and release are all controlled by the network, as is the Quality of Service (QoS) corresponding to the bearer. Therefore, the establishment and modification of E-UTRAN resources are initiated by the MME, which also provides the corresponding QoS information to the network device. Although the network device can initiate an E-UTRAN resource release request, the release process is controlled by the MME; conversely, the MME can also initiate the release of E-UTRAN resources.

[0075] 5. Attach

[0076] The attach process refers to the registration process when a terminal device first connects to an LTE network. This process involves authentication and key negotiation, with the primary purpose of enabling the LTE network to recognize and identify the terminal device for subsequent communication. The terminal device can initiate the attach process by sending an attach request to the network device. For example, this process may include: the terminal device registering in the public land mobile network (PLMN) and camping on a cell; the network device and mobility management device establishing default bearers for the terminal device, including the signaling radio bearer (SRB) and data radio bearer (DRB). After completing the attach process, the terminal device can begin data transmission and communication via the LTE network.

[0077] The attach request information from the terminal device is sent to the mobility management device via the network device, requesting the mobility management device to accept the attach request. The attach request information is transmitted at the non-access stratum; the mobility management device can parse the attach request information, while the network device cannot.

[0078] For example, please refer to Figure 3 , Figure 3 This is a schematic diagram illustrating the process of adding a secondary base station according to an embodiment of this application. After the terminal device successfully accesses the 4G network, the following can be performed: Figure 3 The illustrated secondary base station addition procedure can also be called the secondary node (SgNB) addition procedure, thereby achieving ENDC. The terminal device is an NSA terminal, i.e., a terminal device that has subscribed to NSA dual connectivity. The 4G core network may include a Mobility Management Equipment (MME) and a Serving Gateway (SGW).

[0079] like Figure 3 As shown, the process of adding a secondary base station may include, but is not limited to, the following:

[0080] S301, 5G measurement process.

[0081] The 5G measurement process may include: the MeNB sending RRC connection reconfiguration information to the terminal device; upon receiving the RRC connection reconfiguration information, the terminal device performing 5G measurements; and after completing the 5G measurements, the terminal device sending a measurement report to the MeNB. The measurement report may include information such as the reference signal receiving power (RSRP) and signal-to-interference-plus-noise ratio (SINR) of one or more 5G cells, as well as the absolute radio-frequency channel number (ARFCN) of the 5G network.

[0082] S302, Secondary Base Station Configuration (SgNB addition) process.

[0083] Upon receiving the measurement report, the MeNB can trigger the secondary base station configuration process. For example, the secondary base station configuration process may include the following steps:

[0084] (1) The MeNB sends a secondary base station addition request message to the SgNB. This message includes a measurement report to request the addition of a secondary base station. This measurement report can be the measurement report in S301, or a portion of the measurement report in S301. Upon receiving the secondary base station addition request message, the SgNB can select a 5G cell that meets the criteria based on the measurement report (e.g., select the 5G cell with the strongest RSRP) and determine the configuration information of that 5G cell. After determining the configuration information, the SgNB sends a secondary base station addition request acknowledgement message to the MeNB to indicate that it has agreed to add the secondary base station. The configuration information may include 5G random access channel (RACH) configuration information, cell-radio network temporary identifier (C-RNTI), channel quality indication (CQI), and sounding reference signal (SRS), etc.

[0085] (2) After receiving the secondary base station addition request confirmation information, the MeNB sends RRC connection reconfiguration information to the terminal device to configure the terminal device's signaling radio bearer (SRB) SRB3 and DRB. The RRC connection reconfiguration information may include the configuration information of SRB3 and DRB. Optionally, the RRC connection reconfiguration information may also include 5G RACH configuration information, the physical cell identifier (PCI), C-RNTI, and frequency point information of the terminal device's secondary cell.

[0086] The terminal device performs RRC connection reconfiguration by receiving RRC connection reconfiguration information. After RRC connection reconfiguration, the terminal device sends an RRC connection reconfiguration complete message to the SgNB through the MeNB, so that the SgNB can confirm that the RRC connection reconfiguration has been completed.

[0087] S303, Data copying (eNodeB starts copying data to the gNodeB).

[0088] It is understandable that the data copying process is the process of the primary base station copying data to the secondary base station in ENDC. The specific implementation details of this process can be found in the relevant protocol descriptions, and will not be elaborated upon here.

[0089] S304, the path update procedure.

[0090] During this process, the MeNB sends an E-RAB modification indication to the MME to notify the MME that the user plane data bearer is being switched from the 4G network to the 5G network.

[0091] When the MME receives an E-RAB modification instruction, it can determine whether the terminal device supports DCNR by checking the DCNR field reported by the terminal device. If the DCNR field indicates that the terminal device reports support for DCNR, the MME sends a modify bearer request to the SGW to request the SGW to update the user plane data bearer (i.e., user plane data path) of the terminal device. After receiving the modify bearer request, the SGW can switch the user plane data path of the terminal device from the MeNB to the SgNB. After updating the user plane data bearer of the terminal device, the SGW can send a modify bearer response to the MME. Then, the MME sends an E-RAB modification confirmation to the MeNB to indicate that the user plane data bearer of the terminal device has been updated.

[0092] S305, terminal devices access 5G networks.

[0093] After the data path update is complete, the terminal device can synchronize signals with the SgNB. The terminal device can obtain the 5G primary synchronization signal from the SgNB for downlink frame boundary synchronization; and obtain the 5G secondary synchronization signal from the SgNB for downlink subframe boundary synchronization. After the terminal device and SgNB achieve downlink synchronization, the terminal device can trigger a random access procedure to the SgNB. After completing random access to the SgNB, the SgNB can begin data transmission with the terminal device. Data from the terminal device can be directly routed from the 4G SGW to the 5G SGW, thus achieving ENDC.

[0094] In step S304 above, if the DCNR field reported by the terminal device indicates that the terminal device does not support DCNR, the MME will not respond to the MeNB's E-RAB modification indication information, nor will it request the SGW to update the user plane data bearer of the terminal device. Because no E-RAB modification confirmation information is received from the MME, the MeNB will send the E-RAB modification indication information multiple times, causing the timer to time out, the terminal device to be abnormally released, and ultimately resulting in a dropped call for the terminal device.

[0095] In the above process, the NSA dual connectivity capability of the terminal device can include DCNR capability and ENDC capability. According to the protocol requirements, the terminal device needs to report the DCNR capability to the MME and the ENDC capability to the MeNB. Only under these conditions can the terminal device work normally under the NSA architecture, such as performing NSA dual connectivity.

[0096] It should be noted that the DCNR capability of the terminal device is transmitted in the form of NSA messages. The MeNB cannot parse NAS messages, therefore the MeNB cannot determine whether the terminal device supports DCNR through NAS messages. The MME, on the other hand, can parse NAS messages, so the MME usually determines whether the terminal supports DCNR through the DCNR field in the NAS message. When the MeNB queries the terminal device for air interface capability information, the terminal device can report the ENDC capability to the MeNB according to the MeNB's requirements.

[0097] In some cases, a terminal device may report to the MME that it does not support DCNR, but report to the MeNB that it supports ENDC. For example:

[0098] (1) In non-standalone (NSA) networking, the power consumption of terminal devices performing NSA dual connectivity is relatively high, which is more likely to cause overheating compared to independent access to the 4G (or LTE) network in standalone (SA) networking. In this case, terminal devices can implement overheat protection. Overheat protection refers to the mechanism of taking corresponding measures to reduce the temperature of the terminal device. For example, NSA dual connectivity can be disabled, and only 4G network access can be used. This reduces the power consumption required for the terminal device to maintain network connection, thereby reducing the overheating of the terminal device.

[0099] (2) A default anomaly protection mechanism can be configured in the terminal device. This mechanism can be used to control the terminal device from reporting NSA dual connectivity capabilities within a preset time period, thereby preventing NSA dual connectivity. For example, if the terminal device has experienced abnormal call drops within a certain period (such as within the first ten minutes of the current time), such as when a user enters an elevator or other location with weak or no 5G signal, causing the terminal device to be unable to receive the 5G signal and resulting in a call drop, the terminal device can choose not to report DCNR capabilities within a preset time period to reduce abnormal call drops under the 5G network. After the preset time period has elapsed, the terminal device can re-report DCNR capabilities to request NSA dual connectivity.

[0100] like Figure 3As shown, during the process of accessing the core network, the terminal device first needs to interact with the MeNB. The MeNB checks the air interface capabilities of the terminal device to determine if it supports ENDC, and then sends a secondary base station addition request to the SgNB to add a secondary base station for the terminal device. After the secondary base station is added, the MeNB sends an E-RAB modification indication to the MME, requesting to switch the user plane data path of the terminal device from the MeNB to the SgNB. After receiving this request, the MME checks the DCNR field to determine whether the terminal device supports DCNR. If the terminal device supports DCNR, the MME will send an E-RAB modification confirmation to the MeNB. If the terminal device does not support DCNR, the MME will not respond to the MeNB's E-RAB modification indication, i.e., it will not send an E-RAB modification confirmation to the MeNB. Since the MeNB does not receive the E-RAB modification confirmation, it will continue to send E-RAB modification request information until the timer expires, ultimately causing the terminal device to be released by the MME, which may result in a dropped call for the terminal device in the 5G network.

[0101] It is understood that the NSA dual connectivity scenario described in the embodiments of this application is for the purpose of more clearly illustrating the technical solution of the embodiments of this application, and does not constitute a limitation on the technical solution and application scenario provided in the embodiments of this application. Those skilled in the art will know that with the evolution of system architecture and the emergence of new business scenarios, the technical solution provided in the embodiments of this application is also applicable to similar technical problems, such as the service call drop problem of terminal devices in the dual connectivity scenario of 5G network and 6G network.

[0102] To address the aforementioned issues, this application provides a network configuration method that can guarantee the communication quality of terminal devices.

[0103] Please see Figure 4 , Figure 4 This is a flowchart illustrating a network configuration method provided in an embodiment of this application. The method may include, but is not limited to, the following steps:

[0104] Optionally, in S401, the terminal device sends first capability information to the network device. Correspondingly, the network device receives the first capability information from the terminal device.

[0105] The first capability information indicates whether the terminal device supports first dual connectivity. First dual connectivity refers to dual connectivity where both the primary and secondary base stations of the terminal device are Class I network devices. Class I network devices include 5G base stations such as 5G millimeter-wave base stations and 5G Sub-6G base stations. For example, first dual connectivity can refer to... Figure 2The DCNR shown in (b) indicates that the first dual connectivity can be DCNR. Therefore, it can also be described as the first capability information used to indicate whether the terminal device supports DCNR. Optionally, the first capability information may include a DCNR field, where a value of 0 indicates that the terminal device does not support the first dual connectivity; and a value of 1 indicates that the terminal device supports the first dual connectivity.

[0106] It should be noted that the first capability information is typically carried in the NAS message, and network devices cannot parse NAS messages. Therefore, the specific content indicated by the first capability information is unknown to the terminal device. The network device is mainly responsible for forwarding the first capability information to the mobility management device, which can determine whether the terminal device supports the first dual connectivity through the first capability information. Optionally, in this embodiment, the network device can be a 4G base station, and the mobility management device can be an MME.

[0107] Optionally, the first capability information can be carried within the network capability information. That is, the network capability information may include the first capability information. Optionally, the network capability information may also include one or more of the following: encryption and integrity algorithms supported by the terminal device, proximity service (ProSe) capability information, vehicle-to-everything (V2X) capability information, etc. Among these, the encryption and integrity algorithms supported by the terminal device are used to establish a NAS security mode between the terminal device and the mobility management device; the proximity service capability information is used to indicate whether the terminal device supports direct communication using cellular radio resources (without cellular network relay); and the vehicle-to-everything (V2X) capability information is used to indicate whether the terminal device supports V2X services.

[0108] In one possible implementation, the aforementioned network capability information may be carried in the attach request information; in other words, the attach request information may include the first capability information. The attach request information is used to request the attachment process of the terminal device. Optionally, upon completion of RRC connection establishment, the terminal device may send RRC connection setup complete information to the network device, and carry the attach request information within the RRC connection setup complete information to request the attachment process. That is, the RRC connection setup complete information may include the first capability information.

[0109] S402, the network device sends a first message to the mobility management device. Correspondingly, the mobility management device receives the first message from the network device. The first message includes the terminal device's first capability information.

[0110] The first capability information is used to indicate whether the terminal device supports or does not support the first dual connectivity. Alternatively, the first capability information can be used to indicate whether the terminal device supports or does not support DCNR.

[0111] In one possible implementation, the first message may be an initial user equipment message, which includes the terminal device's initial capability information. Optionally, the first message may include attach request information. Optionally, the first message may also include other network capability information, besides the initial capability information, reported by the terminal device to the network device, such as the encryption and integrity algorithms supported by the terminal device.

[0112] S403, the mobile management device obtains the terminal device's subscription service information from the home management device.

[0113] The subscription service information indicates whether the terminal device has subscribed to NSA dual connectivity. Alternatively, it can be described as indicating whether the terminal device has subscribed to the NSA dual connectivity service. NSA dual connectivity includes a first dual connectivity and a second dual connectivity. The second dual connectivity refers to a dual connectivity where the terminal device's primary base station is a type II network device and the secondary base station is a type I network device. The type I network device can be a 5G base station, and the type II network device can be a 4G base station. For example, the second dual connectivity can refer to... Figure 2 In the ENDC shown in (a), the primary base station of the terminal device is a 4G base station, and the secondary base station is a 5G base station. Both the primary and secondary base stations are connected to the 4G core network. In other words, the second dual connectivity can be an ENDC. Optionally, the network device in this embodiment can be a second type of network device.

[0114] If the subscription service information indicates that the terminal device has subscribed to NSA dual connectivity, then the terminal device can be called an NSA terminal. According to the protocol requirements, an NSA terminal must report support for ENDC to the network device and send support for DCNR to the mobility management device through the network device in order to establish dual connectivity.

[0115] Optionally, obtaining the terminal device's subscription service information from the home management device may include: the mobility management device sending subscription query information to the home management device to request the terminal device's subscription service information. Optionally, the subscription query information may include the terminal device's identification information. Upon receiving the subscription query information, the home management device may obtain the subscription service information based on the terminal device's identification information and send subscription query response information, including the subscription service information, to the mobility management device. Therefore, after receiving the subscription query response information, the mobility management device may determine whether the terminal device has subscribed to NSA dual connectivity based on the subscription service information.

[0116] In one possible implementation, the first message may further include the terminal device's identity information. Before obtaining subscription service information, the mobility management device may send an authentication request to the home management device, requesting authentication of the terminal device. Upon receiving the authentication request, the home management device may authenticate the terminal device based on its identity information and send an authentication response to the mobility management device, indicating whether the terminal device has passed authentication. Optionally, the terminal device's identity information may include information such as the International Mobile Equipment Identity (IMSI) and network ID. If the authentication response indicates that the terminal device has passed authentication, the mobility management device may obtain the terminal device's subscription service information from the home management device.

[0117] S404, if the first capability information indicates that the terminal device does not support the first dual connectivity, and the subscription service information indicates that the terminal device has subscribed to NSA dual connectivity, the mobility management device sends a second message to the network device. Correspondingly, the network device receives the second message from the mobility management device. The second message indicates that the network device does not query the terminal device's second capability information. The second capability information is used to indicate whether the terminal device supports or does not support the second dual connectivity.

[0118] The second dual-connection can be ENDC; in other words, the second capability information is used to indicate whether the terminal device supports or does not support ENDC. Typically, the network device can query the terminal device's second capability information to determine whether the terminal device supports ENDC. If the network device has determined that the terminal device supports ENDC, the network device will initiate a process such as... Figure 3 The procedure for adding a secondary base station is shown below. Otherwise, the network device will not initiate the process of adding a secondary base station.

[0119] In one possible implementation, the second message may include a Restricted in EPSasSecondaryRAT, which is used to instruct the network device not to query the terminal device's second capability information.

[0120] In one possible implementation, the second message can be an initial context setup request message, used to request the network device to establish the initial context information of the terminal device. That is, the second message not only instructs the network device not to query the terminal device's second capability information, but also requests the network device to establish the terminal device's initial context information. Establishing the initial context information of the terminal device is for the purpose of establishing the terminal device's default bearers, including the terminal device's radio signaling bearer (SRB) and data radio bearer (DRB).

[0121] S405, the network device obtains the terminal device's radio capability information from the terminal device. The radio capability information does not include the terminal device's secondary capability information.

[0122] For example, the wireless capability information of a terminal device may include a list of frequencies supported by the terminal device, supported carrier aggregation (CA) band combinations, UE Category, PDCP parameters, radio link control (RLC) parameters, physical layer parameters, and radio frequency (RF) parameters. The UE Category indicates information such as the maximum download and upload speeds achievable by the terminal device, and network devices can determine the transmission capabilities of the terminal device through the UE Category. RF parameters may indicate information such as the frequency bands and duplex modes supported by the terminal device.

[0123] In one possible implementation, the network device obtaining the terminal device's radio capability information from the terminal device may include: the network device sending a fourth message to the terminal device, instructing the terminal device to report radio capability information, which does not include the second capability information; and the terminal device reporting the radio capability information to the network device upon receiving the fourth message. Optionally, the fourth message may be air interface capability query information, used to instruct the terminal device to report radio capability information.

[0124] In one possible implementation, the network device can send the acquired wireless capability information of the terminal device to the mobility management device, thereby allowing the mobility management device to update the stored capability information of the terminal device.

[0125] In this application, the mobility management device can determine whether a terminal device does not support the first dual connectivity through the first capability information, while the network device cannot determine whether the terminal device supports the first dual connectivity because it cannot parse the first capability information. Typically, the terminal device determines whether it supports the second dual connectivity by sending an air interface capability query message. Under normal circumstances, a terminal device that has subscribed to NSA dual connectivity will report support for the second dual connectivity to the network device.

[0126] For example, such as Figure 3 As shown in steps S301 to S305, when the network device determines that the terminal device supports the second dual connectivity, after the terminal device generates a measurement report, the network device sends a secondary base station addition request to the SgNB to add a secondary base station for the terminal device. After completing the secondary base station addition with the SgNB, the network device (i.e., as shown in steps S301 to S305)... Figure 3The MeNB (Medium-Level Network Node) shown in the diagram sends an E-RAB modification instruction to the Mobility Management Device (MMDD), requesting a switch of the terminal device's user plane data path from the network device to the SgNB. Upon receiving this instruction, the MMDD determines whether the terminal device supports the first dual connectivity based on its first capability information. If the terminal device does not support the first dual connectivity, the MMDD will not respond to the network device's E-RAB modification instruction, i.e., it will not send an E-RAB modification confirmation message. Since the network device does not receive this confirmation message, it will continue to send E-RAB modification instruction messages until the timer expires, ultimately leading to the abnormal release of the terminal device by the MMDD, which may cause a dropped call on the 5G network.

[0127] Therefore, if the network device does not query the terminal device's second capability information, the network device will not initiate such a process. Figure 3 The auxiliary base station addition process shown in the diagram eliminates the need for NSA dual connectivity for the terminal device, further preventing dropped calls in the aforementioned situations.

[0128] Optional, S406, RRC connection reconfiguration.

[0129] During this process, the network device can send RRC connection reconfiguration information to the terminal device. This RRC connection reconfiguration information includes the terminal device's initial context information. The terminal device can perform RRC connection reconfiguration by receiving this information; that is, the terminal device can receive the initial context information configured for it by the network device through RRC connection reconfiguration. Once the terminal device completes the RRC connection reconfiguration, it can send RRC connection reconfiguration completion information to the network device. Based on this, upon receiving the RRC connection reconfiguration completion information from the terminal device, the network device will execute step S407 as described below.

[0130] The initial context information includes network configuration information of the terminal device corresponding to the second type of network device, but excludes network configuration information of the terminal device corresponding to the first type of network device. Optionally, the network device can determine the initial context information of the terminal device by establishing a request information and radio capability information of the terminal device based on the initial context. The network configuration information may include the configuration information of the terminal device's default bearers, such as the configuration information of radio signaling bearers (SRB) and radio data bearers (DRB). Optionally, the first type of network device can be a 5G base station, and the second type of network device can be a 4G base station. In this case, the network configuration information may include the network configuration information of the terminal device corresponding to the 4G base station. For example, the network configuration information may include the configuration information of radio signaling bearers SRB1 and SRB2, and radio data bearers DRB. SRB2 is used to transmit NAS messages and some RRC information, such as uplink information transfer (UL information transfer) information and downlink information transfer (DL information transfer) information. The network device is only responsible for forwarding the above two RRC messages without processing them.

[0131] Optionally, since the initial context information does not include the network configuration information of the terminal device corresponding to the first type of network device, such as the network configuration information of the terminal device corresponding to the 5G base station, the terminal device will not access the 5G network, and thus the terminal device does not need to perform dual connectivity.

[0132] In one possible implementation, RRC connection reconfiguration information can also be used to notify the terminal device that its attach request information has been accepted by the mobility management device.

[0133] S407, the network device sends a third message to the mobility management device. Correspondingly, the mobility management device receives the third message from the network device. The third message includes initial context information of the terminal device. The initial context information includes network configuration information of the terminal device corresponding to a second-type network device, but does not include network configuration information of the terminal device corresponding to a first-type network device.

[0134] Through the third message, the mobility management device can determine that the network device has completed the establishment of initial context information. Optionally, after receiving the RRC connection reconfiguration completion information from the terminal device, the network device can send a third message to the mobility management device. Once the initial context information of the terminal device is established, the terminal device has successfully accessed the core network connected to the second type of network device, such as a 4G core network (or LTE core network). Based on this, service communication can be carried out between the terminal device and the mobility management device, and the terminal device can obtain relatively stable communication quality through the core network.

[0135] In one possible implementation, after the initial context information of the terminal device is established, the terminal device can send UL information transfer information to the mobility management device through the network device. This information may include attach complete information and activate default EPS bearer context accept information. Based on this information, the mobility management device can determine that the terminal device has completed the attach process, thereby enabling the mobility management device to conduct service communication with the terminal device.

[0136] As can be seen, by implementing the embodiments of this application, when a terminal device has subscribed to NSA dual connectivity but reports that it does not support the first dual connectivity, the mobility management device can instruct the network device not to query whether the terminal device supports the second dual connectivity. This ensures that the initial context information of the established terminal device does not include the network configuration information of the terminal device corresponding to the first type of network device. In other words, it does not include the network configuration information required for NSA dual connectivity. Furthermore, the network device will not execute the auxiliary base station addition process in the process of configuring NSA dual connectivity for the terminal device. This allows the terminal device to access the network independently without performing NSA dual connectivity, such as accessing only the 4G network, thereby avoiding the risk of dropped calls for the terminal device in the NSA dual connectivity scenario.

[0137] This application provides a communication device that can be used to implement the functions of the aforementioned mobility management device or network device. The communication device can be a mobility management device or network device. The communication device includes modules or units corresponding to the methods / operations / steps / actions performed by the mobility management device or network device in the above method embodiments. These units can be hardware circuits, software, or a combination of hardware circuits and software. Please refer to... Figure 5 , Figure 5 A schematic diagram of a communication device 500 according to an embodiment of this application is shown. The communication device 500 may include an interface module 510, which is used to receive and send data. Optionally, the communication device may also include a processing module 520. Specifically, the processing module 520 is used to process signaling and / or data, which may be data received by the interface module 510, and the processed signaling and / or data may also be sent by the interface module 510.

[0138] In one embodiment, when the communication device 500 is a mobility management device, wherein:

[0139] Interface module 510 is configured to, upon receiving a first message from a network device, obtain subscription service information of the terminal device from the home management device, the first message including first capability information of the terminal device; if the first capability information indicates that the terminal device does not support the first dual connection, and the subscription service information indicates that the terminal device has subscribed to NSA dual connection, send a second message to the network device, the second message being used to request the network device to establish initial context information of the terminal device, and the second message indicating that the network device does not query the second capability information of the terminal device; wherein, the second capability information is used to indicate whether the terminal device supports or does not support the second dual connection; and receive a third message from the network device, the third message including initial context information of the terminal device, the initial context information including network configuration information of the terminal device corresponding to the second type of network device, but not including network configuration information of the terminal device corresponding to the first type of network device.

[0140] The dual connectivity includes a first dual connectivity and a second dual connectivity. The first dual connectivity is a dual connectivity in which both the main base station and the auxiliary base station of the terminal device are Class I network devices. The second dual connectivity is a dual connectivity in which the main base station of the terminal device is a Class II network device and the auxiliary base station of the terminal device is a Class I network device.

[0141] In one possible implementation, interface module 510 is used to communicate with the terminal device based on established initial context information.

[0142] In one possible implementation, the first message includes the identity information of the terminal device; the processing module 520 is used to send authentication request information to the home management device, the authentication request information including the identity information; and to receive authentication response information from the home management device, the authentication response information being used to instruct the terminal device to pass the identity authentication.

[0143] In one possible implementation, interface module 510 is used to send subscription query information to the home management device to request subscription service information from the terminal device; and to receive subscription query response information from the home management device, wherein the subscription query response information includes the subscription service information of the terminal device.

[0144] For specific implementation details of the interface module 510 and processing module 520 mentioned above, please refer to [link to relevant documentation]. Figure 4 The specific implementation steps for China Mobile's management equipment will not be elaborated here.

[0145] In one embodiment, when the communication device 500 is a network device, wherein:

[0146] Interface module 510 is configured to, upon receiving first capability information from a terminal device, send a first message to a mobility management device, the first message including the first capability information of the terminal device; receive a second message from the mobility management device, the second message corresponding to the first capability information, the second message being used to request the establishment of initial context information of the terminal device, and the second message instructing the network device not to query the second capability information of the terminal device; obtain radio capability information of the terminal device from the terminal device according to the second message, the radio capability information not including the second capability information; processing module 520 is configured to generate initial context information of the terminal device according to the radio capability information; and interface module 510 is configured to send a third message to the mobility management device, the third message including the initial context information of the terminal device.

[0147] The second capability information is used to indicate whether the terminal device supports or does not support the second dual connectivity, where the primary base station of the terminal device is a second type of network device and the secondary base station of the terminal device is a first type of network device. The initial context information includes the network configuration information of the terminal device corresponding to the second type of network device, but does not include the network configuration information of the terminal device corresponding to the first type of network device.

[0148] In one possible implementation, the interface module 510 is configured to receive attach request information from the terminal device, the attach request information including first capability information of the terminal device; and send a first message to the mobility management device, the first message including the first capability information.

[0149] In one possible implementation, interface module 510 is used to send a fourth message to the terminal device, the fourth message being used to instruct the terminal device to report wireless capability information, the wireless capability information not including the second capability information; and to receive wireless capability information from the terminal device.

[0150] In one possible implementation, interface module 510 is used to send RRC connection reconfiguration information to the terminal device, the RRC connection reconfiguration information including initial context information. Interface module 510 is also used to send a third message to the mobility management device upon receiving RRC connection reconfiguration completion information from the terminal device.

[0151] For specific implementation details of the interface module 510 and processing module 520 mentioned above, please refer to [link to relevant documentation]. Figure 4 The specific implementation steps for network equipment will not be elaborated here.

[0152] Please see Figure 6 ,like Figure 6The illustration shows a communication device 600 provided in an embodiment of this application, used to implement the functions of the aforementioned mobility management device or network device. This device can be a communication device or a device used within a communication device. The communication device can be a mobility management device or a network device. The device used within the communication device can be a chip system or a chip within the communication device. The chip system can be composed of chips, or it can include chips and other discrete components.

[0153] The communication device 600 includes at least one processor 610 for implementing the processing functions of the device (e.g., a mobility management device or a network device) in the methods provided in this application embodiment. The communication device 600 may also include a communication interface 620 for implementing the transmit and receive operations of the device (e.g., a mobility management device or a network device) in the methods provided in this application embodiment. In this application embodiment, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface for communicating with other devices via a transmission medium. For example, the communication interface 620 is used for communication between the device in the communication device 600 and other devices. The processor 610 uses the communication interface 620 to transmit and receive data and is used to implement the methods described in the above method embodiments.

[0154] The communication device 600 may further include at least one memory 630 for storing program instructions and / or data. The memory 630 is coupled to the processor 610. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and may be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. The processor 610 may operate in conjunction with the memory 630. The processor 610 may execute program instructions stored in the memory 630. At least one of the at least one memory may be included in the processor.

[0155] This application embodiment does not limit the specific connection medium between the communication interface 620, processor 610, and memory 630. This application embodiment... Figure 6 The memory 630, processor 610, and communication interface 620 are connected via a bus, and the bus is in... Figure 6 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 6 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0156] When the communication device 600 is specifically a device used for equipment (such as a mobility management device or a network device), for example, when the communication device 600 is specifically a chip or chip system, the communication interface 620 may output or receive baseband signals. When the communication device 600 is specifically a device (such as a mobility management device or a network device), the communication interface 620 may output or receive radio frequency signals. In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, which can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0157] It should be noted that the aforementioned communication interface 620 can be used to perform the functions of the aforementioned interface module 510, and the aforementioned processor 610 can be used to perform the functions of the aforementioned processing module 520, which will not be elaborated further here.

[0158] When the aforementioned communication device is a chip used in a mobility management device, the network device chip implements the functions of the mobility management device in the above method embodiments. The mobility management device chip receives information from other network elements; or, the mobility management device chip sends information to other network elements.

[0159] When the aforementioned communication device is a chip used in a network device, the network device chip implements the functions of the network device in the above method embodiments. The network device chip receives information from other network elements; or, the network device chip sends information to other network elements.

[0160] It is understood that the processor in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0161] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Additionally, the ASIC can reside in a network device or a terminal device. Alternatively, the processor and storage medium can exist as discrete components in the terminal device or network device.

[0162] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program or instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a DVD; or it can be a semiconductor medium, such as a solid-state disk (SSD).

[0163] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0164] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0165] This application also provides a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are executed, the method executed by the terminal device or network device in the above method embodiments is implemented.

[0166] This application also provides a computer program product, which includes a computer program that, when executed, causes the method executed by the terminal device or network device in the above method embodiments to be implemented.

[0167] This application also provides a communication system, which includes a terminal device or a network device. The terminal device is used to execute the method described in the above method embodiments. The network device is used to execute the method described in the above method embodiments.

[0168] In the above embodiments, the descriptions of each embodiment have their own emphasis. Parts not described in detail in a particular embodiment can be referred to in the relevant descriptions of other embodiments. For ease of description and brevity, the functions and execution steps of the various devices and equipment provided in the embodiments of this application can be referred to in the relevant descriptions of the method embodiments of this application. The method embodiments and device embodiments can also be referenced, combined, or cited from each other.

[0169] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0170] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A network configuration method, characterized in that, The method includes: Upon receiving a first message from a network device, the subscription service information of the terminal device is obtained from the home management device; the first message includes the first capability information of the terminal device. If the first capability information indicates that the terminal device does not support the first dual connection, and the subscription service information indicates that the terminal device has subscribed to non-standalone (NSA) dual connection, a second message is sent to the network device. The second message is used to request the network device to establish the initial context information of the terminal device. The second message indicates that the second capability information of the terminal device is not queried. The second capability information is used to indicate whether the terminal device supports or does not support the second dual connection. The dual connection includes the first dual connection and the second dual connection. The first dual connection is a dual connection in which both the primary base station and the secondary base station of the terminal device are first-type network devices. The second dual connection is a dual connection in which the primary base station of the terminal device is a second-type network device, and the secondary base station of the terminal device is a first-type network device. A third message is received from the network device, the third message including the initial context information, the initial context information including network configuration information of the terminal device corresponding to the second type of network device, but not including network configuration information of the terminal device corresponding to the first type of network device.

2. The method according to claim 1, characterized in that, The method further includes: Based on the initial context information, communication is conducted with the terminal device.

3. The method according to claim 1, characterized in that, The first message also includes the identity information of the terminal device; the method further includes: Send authentication request information to the home management device, the authentication request information including the identity information of the terminal device; The terminal device receives authentication response information from the home management device, which instructs the terminal device to authenticate its identity.

4. The method according to claim 3, characterized in that, The step of obtaining the subscription service information of the terminal device from the home management device includes: Send subscription query information to the home management device, wherein the subscription query information is used to request subscription service information from the terminal device; Receive subscription query response information from the home management device, the subscription query response information including the subscription service information.

5. A network configuration method, characterized in that, The method includes: A second message is received from the mobility management device. The second message is used to request the establishment of initial context information of the terminal device. The second message indicates that the second capability information of the terminal device is not queried. The second capability information is used to indicate whether the terminal device supports or does not support the second dual connectivity. The second dual connectivity is a dual connectivity in which the primary base station of the terminal device is a second type of network device and the secondary base station of the terminal device is a first type of network device. According to the second message, the wireless capability information of the terminal device is obtained from the terminal device, wherein the wireless capability information does not include the second capability information; Based on the wireless capability information, initial context information of the terminal device is generated. The initial context information includes network configuration information of the terminal device corresponding to the second type of network device, but does not include network configuration information of the terminal device corresponding to the first type of network device. A third message is sent to the mobility management device, the third message including the initial context information of the terminal device.

6. The method according to claim 5, characterized in that, The step of obtaining the wireless capability information of the terminal device from the terminal device includes: Send a fourth message to the terminal device, the fourth message being used to instruct the reporting of wireless capability information; Receive the wireless capability information from the terminal device.

7. The method according to claim 5, characterized in that, The method further includes: Send Radio Resource Control (RRC) connection reconfiguration information to the terminal device, wherein the RRC connection reconfiguration information includes the initial context information; Sending a third message to the mobility management device includes: Upon receiving RRC connection reconfiguration completion information from the terminal device, a third message is sent to the mobility management device.

8. The method according to claim 5, characterized in that, The method further includes: Receive attachment request information from the terminal device, the attachment request information including first capability information of the terminal device; A first message is sent to the mobility management device, the first message including the first capability information.

9. A communication device, characterized in that, The communication device includes a transceiver module and a processing module, which are used to implement the method as described in any one of claims 1-4, or the method as described in any one of claims 5-8.

10. A communication device, characterized in that, include: A processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the communication device to perform the method as described in any one of claims 1-4, or the method as described in any one of claims 5-8.

11. A computer-readable storage medium, characterized in that, The computer storage medium stores a computer program or instructions that, when executed, implement the method as described in any one of claims 1-4, or the method as described in any one of claims 5-8.

12. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1-4, or the method as described in any one of claims 5-8.

Images