WO2021072629A1

WO2021072629A1 - Method and device for establishing radio resource control connection

Info

Publication number: WO2021072629A1
Application number: PCT/CN2019/111225
Authority: WO
Inventors: 胡星星; 曾清海; 张宏平
Original assignee: 华为技术有限公司
Priority date: 2019-10-15
Filing date: 2019-10-15
Publication date: 2021-04-22
Also published as: CN114586469B; CN114586469A

Abstract

Provided are a method and device for establishing an RRC connection. The method comprises: a terminal device being able to use a second user identity to establish an RRC connection of the second user identity according to configuration information comprised in a first RRC message of a first user identity. A terminal device needing to use a second user identity to re-initiate random access and to independently re-establish an RRC connection is prevented, and the situation whereby the terminal device fails as a result of initiating random access by means of the second user identify can also be prevented, thereby facilitating improving the success rate of random access, and even leading to the terminal device not needing to use the second user identity to initiate random access and instead directly inheriting an RRC connection of a first user identity, so that the resource overhead caused by random access can also be avoided, thereby facilitating improving the transmission performance.

Description

Method and device for establishing wireless resource control connection

Technical field

This application relates to the communication field, and more specifically, to a method and apparatus for establishing a radio resource control connection in the communication field.

Background technique

With the development of communication technology, many terminal devices (such as mobile phones) have the function of supporting multiple subscriber identification module (SIM) cards, for example, supporting two SIM cards. The process for the terminal device to establish a radio resource control (RRC) connection includes initiating a random access process and after the random access is completed, the terminal device and the network device exchange messages to establish an RRC connection, and so on. Random access includes random access based on contention or non-competition. For random access based on contention, terminal equipment needs to compete for random access resources for multiple SIM cards due to limited resources, which will increase the delay of random access and even cause random access. Circumstances such as access failure, resulting in a decrease in transmission performance; for non-competitive random access, multiple SIM cards of the terminal device need to occupy more random access resources, which will increase the resource overhead of random access. In addition, the process of initiating random access when each SIM card of the terminal device establishes an RRC connection results in a relatively long RRC establishment delay and a decrease in transmission performance. Therefore, there is an urgent need for a method for improving the transmission performance of a terminal device supporting multiple SIM cards in establishing an RRC connection.

Summary of the invention

The present application provides a method and device for establishing an RRC connection, which can reduce the signaling overhead of establishing an RRC connection, and also reduces the delay of random access, which is beneficial to improving transmission performance.

In the first aspect, a method for establishing an RRC connection is provided, the method is applicable to a terminal device, and the terminal device supports a first user identity and a second user identity, and the method includes:

The terminal device receives the first RRC message of the first user identity from the network device as the first user identity, the first RRC message includes configuration information, and the configuration information is used by the terminal device as the second user identity Establish an RRC connection; the terminal device establishes an RRC connection according to the configuration information as the second user.

Therefore, in the method for establishing an RRC connection in the embodiment of the present application, the terminal device can establish the RRC connection of the second user identity according to the configuration information included in the first RRC message of the first user identity as the second user identity, avoiding the need for the terminal device to Re-initiating random access as the second user and re-establishing an RRC connection independently can also avoid the failure of the terminal device to initiate random access as the second user, which is beneficial to improve the success rate of random access, even if the terminal device does not use The random access initiated by the second user identity directly inherits the RRC connection of the first user identity, which can also avoid the resource overhead caused by the random access, thereby helping to improve the transmission performance.

Optionally, the establishment of the RRC connection by the terminal device as the second user identity according to the configuration information can be understood as: the terminal device inherits the RRC connection established by the first user identity as the second user identity, and the terminal device does not need to initiate a random connection as the second user identity. In, there is no need to establish an RRC connection as the second user. In this case, the configuration information is used to instruct the terminal device as the second user to use the RRC connection established by the terminal device as the first user.

Optionally, the terminal device establishing an RRC connection according to the configuration information as the second user can be understood as: the terminal device uses both the first user identity and the second user identity to use the terminal device to establish the RRC connection with the first user identity at the same time, then the terminal device The second user identity is not used to initiate random access, and the RRC connection does not need to be established again as the second user identity.

Optionally, the establishment of the RRC connection by the terminal device as the second user identity according to the configuration information can be understood as: the terminal device uses the first user identity and the second user identity in a time-division multiplexing manner to use the terminal device as the first user identity. RRC connection established.

Optionally, the terminal device establishing an RRC connection as the second user according to the configuration information can be understood as: the terminal device uses the configuration information to initiate random access as the second user, and the configuration information may include random access channel resources (random access channel, RACH), without the need to use competition to obtain resources for initiating random access, which can improve the success rate of random access and reduce the delay of random access.

Optionally, the establishment of the RRC connection by the terminal device as the second user identity according to the configuration information may be understood as: the terminal device uses the configuration information to establish the RRC connection as the second user identity. For example, the configuration information may include 2. The uplink authorization information for establishing the RRC connection with the user identity and the temporary radio network identifier C-RNTI of the cell used for the terminal device to establish the RRC connection as the second user identity, so that the terminal device does not need to initiate random access as the second user identity Directly send the RRC connection establishment request or the RRC reestablishment request or the RRC recovery request of the second user identity to the network device according to the resources indicated by the uplink authorization information, and the terminal device can use the C-RNTI to communicate with the network device as the second user identity.

In some possible implementations, the establishment of the RRC connection by the terminal device as the second user identity according to the configuration information includes: the terminal device uses the terminal device as the second user identity according to the configuration information to For the RRC connection established with the identity of the first user, the terminal device can use the RRC connection established with the identity of the first user by the terminal device as the first user. That is, the terminal device can use the RRC connection established by the terminal device with the first user identity in a simultaneous use of the first user identity and the second user identity or in a time division multiplexing manner.

In some possible implementation manners, the first RRC message includes a second RRC message of the second user identity of the terminal device, the second RRC message includes the configuration information, and the method further includes: The terminal device determines, according to the second RRC message included in the first RRC message, that the terminal device can use the RRC connection established with the first user identity by the terminal device as the second user identity. The RRC connection established as the first user using the terminal device as the second user can be determined through the nesting of RRC messages.

In some possible implementation manners, the first RRC message includes first indication information, and the first indication information is used to indicate that the configuration information included in the first RRC message is used by the terminal device in the Establishing an RRC connection with a second user identity, and the method further includes: the terminal device determines, according to the first indication information, that the terminal device can use the terminal device as the second user to establish an RRC connection with the first user identity. RRC connection. That is, the RRC connection established as the first user using the terminal device as the second user can be determined through an explicit indication in the first RRC message.

In some possible implementation manners, the method further includes: the terminal device determines that the terminal device can use the terminal device as the second user according to the position of the cell where the configuration information is located in the first RRC message. For the RRC connection established by the terminal device with the identity of the first user, the information elements where the configuration information of the different user identities of the terminal device are located are in different positions of the first RRC message. The protocol may stipulate that the information elements in which the network equipment configures the configuration information of different user identities of the terminal equipment are located in different positions of the first RRC message.

In some possible implementation manners, the first RRC message includes a correspondence, the correspondence is used to indicate that different bearers correspond to different user identities, or the correspondence is used to indicate different logical channels of the same bearer Corresponding to different user identities, or the corresponding relationship is used to indicate that different keys correspond to different user identities, or the corresponding relationship is used to indicate that different C-RNTIs correspond to different user identities, or the corresponding The relationship is used to indicate that different bandwidth parts BWP correspond to different user identities, or the corresponding relationship is used to indicate that different subcarrier intervals correspond to different user identities, and the corresponding relationship is used for the terminal device to determine the first User identity or said second user identity.

In this way, after the terminal device subsequently receives the data packet (the data packet includes the RRC message transmitted through the SRB and/or the data transmitted through the DRB), since the terminal device supports the first user identity and the second user identity at the same time, the terminal device can follow the corresponding The relationship determines whether the data packet belongs to the first user identity or the second user identity.

In some possible implementation manners, the configuration information further includes at least one of a protocol stack parameter of the second user identity and key information of the second user identity.

Optionally, the key information may include the key of the second user identity (for example, the network device may derive the key of the second user identity according to the key of the first user identity) or include the key used to generate the second user identity. Key information or parameters, etc.

In this way, the terminal device can modify the protocol stack parameters of the first user identity to the protocol stack parameters of the second user identity included in the configuration information, so that the protocol stack parameters of the second user identity can be obtained.

In some possible implementation manners, the method further includes: the terminal device receives a third RRC message from the network device as the first user identity, the third RRC message includes first paging information, and the first user A paging message carries the identity of the second user of the terminal device. When the terminal device has not determined whether the second user identity can use the RRC connection of the first user identity, or the terminal device has not completed the random access process as the second user identity, the network device may page the second user identity The paging information of the terminal device is carried in the third RRC message of the first user identity, so as to prevent the network device from being unable to page the terminal device of the second user identity.

In some possible implementation manners, before the terminal device establishes an RRC connection according to the configuration information as the second user identity, the method further includes: The network device sends a fourth RRC message, where the fourth RRC message includes minimizing drive test MDT information or radio link failure information or access failure information of the second user identity of the terminal device. In this way, the MDT information or the wireless link failure information or the access failure information of the second user identity can be prevented from being outdated or deleted.

In some possible implementation manners, the first RRC message is an RRC release message or an RRC reconfiguration message, and the RRC release message is used to instruct to release the RRC connection of the first user identity of the terminal device or to Instruct the RRC connection of the first user identity of the terminal device to enter an inactive state.

In some possible implementations, the first RRC message may include the NAS message of the first user identity, may also include the NAS message of the first user identity and the NAS message of the second user identity, and may also include the NAS message of the second user identity. Message, the terminal device needs to determine whether the NAS message in the first RRC message belongs to the first user identity or the second user identity.

In some possible implementations, if the first RRC message includes the fifth RRC message of the second user identity of the terminal device, and the fifth RRC message includes the NAS message, the terminal device can determine according to the fifth RRC message included in the first RRC message. The NAS message is the NAS message of the second user identity. That is, the user identity of the NAS message can be determined through the nesting of the RRC message.

In some possible implementation manners, the first RRC message includes second indication information, and the second indication information is used to indicate that the NAS message included in the first RRC message is a NAS message with a second user identity, so that the terminal The device can determine that the NAS message is of the second user identity according to the second indication information included in the first RRC message. That is, the explicit indication in the first RRC message can be used to determine whether the NAS message belongs to the first user identity or the second user identity.

In some possible implementations, the information elements of the NAS messages of different user identities of the terminal equipment are located in different positions of the first RRC message, and the terminal equipment is based on the information element of the NAS message located in the first RRC message. The location determines whether the NAS message is the identity of the first user or the identity of the second user. The protocol may stipulate that the network device configures the cell in which the NAS message of different user identities of the terminal device is located in different positions of the first RRC message.

In a second aspect, a method for establishing a radio resource control RRC connection is provided, which is characterized by comprising: a network device acquiring configuration information, where the configuration information is used by a terminal device to establish a radio resource control RRC connection as a second user;

The network device sends a first RRC message to a terminal device with a first user identity, where the first RRC message includes the configuration information.

In some possible implementation manners, before the network device sends the first RRC message to the terminal device of the first user identity, the method further includes:

The network device determines that the terminal device supports the first user identity and the second user identity.

In some possible implementation manners, the configuration information includes a random access channel RACH resource for the terminal device to establish an RRC connection with the second user identity, and a random access channel RACH resource for the terminal device to use the second user identity. At least one of uplink authorization information for establishing an RRC connection and a temporary radio network identifier C-RNTI of a cell used for the terminal device to establish an RRC connection as the second user identity.

In some possible implementation manners, the configuration information is used to instruct the terminal device as the second user to use the RRC connection established by the terminal device as the first user.

In some possible implementation manners, the first RRC message includes a second RRC message of the second user identity of the terminal device, and the second RRC message includes the configuration information.

In some possible implementation manners, the first RRC message includes first indication information, and the first indication information is used to indicate that the configuration information included in the first RRC message is used for the terminal device to use the second indication information. The user identity establishes an RRC connection.

In some possible implementation manners, the first RRC message includes a correspondence, the correspondence is used to indicate that different bearers correspond to different user identities, or the correspondence is used to indicate different logical channels of the same bearer Corresponding to different user identities, or the corresponding relationship is used to indicate that different keys correspond to different user identities, or the first corresponding relationship is used to indicate that different C-RNTIs correspond to different user identities, or The correspondence relationship is used to indicate that different bandwidth parts BWP correspond to different user identities, or the correspondence relationship is used to indicate that different subcarrier intervals correspond to different user identities, and the correspondence relationship is used by the terminal device to determine the first A user identity or the second user identity.

In some possible implementations, if the configuration information includes the protocol stack parameters of the second user identity, the protocol stack parameters of the second user identity are radio link control RLC layer parameters, media access control MAC layer When at least one of parameters or physical PHY layer parameters, the network device acquiring configuration information includes:

The network device sends a request message to the distribution unit DU, where the request message is used to request the protocol stack parameters of the second user identity.

In some possible implementation manners, the method further includes:

The network device sends a third RRC message to the terminal device of the first user identity, where the third RRC message includes first paging information, and the first paging information carries the second paging information of the terminal device. The identity of the user.

In some possible implementation manners, the method further includes:

Receiving, by the network device, a fourth RRC message sent by the terminal device of the first user identity, where the fourth RRC message includes the minimized drive test MDT information of the second user identity of the terminal device;

The network device determines the MDT information of the second user identity according to the fourth RRC message.

In some possible implementation manners, the first RRC message is an RRC release message or an RRC reconfiguration message, and the RRC release message is used to instruct to release the RRC connection of the first user identity of the terminal device or to Instruct the first user identity of the terminal device to enter the RRC inactive state.

In a third aspect, the present application provides an apparatus for establishing an RRC connection, including a transceiver unit and an establishment unit, where the transceiver unit is configured to receive the first radio resource control RRC of the first user identity from a network device as the first user identity Message, the first RRC message includes configuration information, and the configuration information is used by the device to establish an RRC connection as the second user; an establishment unit is used to establish an RRC connection as the second user according to the configuration information RRC connection.

In some possible implementations, the configuration information includes a random access channel RACH resource for the establishment unit to establish an RRC connection with the identity of the second user, and a resource for the establishment unit to establish an RRC connection with the identity of the second user. At least one of the uplink authorization information and the temporary radio network identifier C-RNTI of the cell used for the establishment unit to establish the RRC connection with the identity of the second user.

In some possible implementation manners, the configuration information is used to instruct the apparatus to use the RRC connection established by the apparatus as the first user as the second user;

The establishing unit is specifically configured to: use the apparatus to establish an RRC connection with the identity of the first user using the identity of the second user according to the configuration information.

In some possible implementation manners, the establishing unit is specifically configured to: use the device as the second user to establish the RRC connection as the first user according to the configuration information, and the device can use the RRC connection as the first user as the first user. The RRC connection established by the device as the first user.

In some possible implementation manners, the first RRC message includes a second RRC message of the second user identity of the apparatus, the second RRC message includes the configuration information, and the apparatus further includes:

The determining unit is configured to determine, according to the second RRC message included in the first RRC message, that the device can use the device as the second user identity to establish the RRC connection established with the first user identity.

In some possible implementation manners, the first RRC message includes first indication information, and the first indication information is used to indicate that the configuration information included in the first RRC message is used by the device to communicate with the second user. The identity establishes an RRC connection, and the determining unit is further configured to determine, according to the first indication information, that the device can use the device as the second user to establish the RRC connection with the first user.

In some possible implementation manners, the determining unit is further configured to determine, according to the position of the cell where the configuration information is located in the first RRC message, that the device can use the device as the second user For the RRC connection established by the first user identity, the information elements where the configuration information of the different user identities of the device are located are in different positions of the first RRC message.

In some possible implementation manners, the first RRC message includes a correspondence, the correspondence is used to indicate that different bearers correspond to different user identities, or the correspondence is used to indicate different logical channels of the same bearer Corresponding to different user identities, or the corresponding relationship is used to indicate that different keys correspond to different user identities, or the corresponding relationship is used to indicate that different C-RNTIs correspond to different user identities, or the corresponding The relationship is used to indicate that different bandwidth parts BWP correspond to different user identities, or the corresponding relationship is used to indicate that different subcarrier intervals correspond to different user identities, and the corresponding relationship is used by the device to determine the first user identity or The identity of the second user.

In some possible implementation manners, the transceiving unit is further configured to receive a third RRC message from the network device as the first user, where the third RRC message includes first paging information, and the first paging The information carries the identifier of the second user identity of the device.

In some possible implementation manners, the transceiving unit is further configured to send a fourth user identity to the network device as the first user before establishing an RRC connection according to the configuration information as the second user identity. An RRC message, where the fourth RRC message includes minimized drive test MDT information of the second user identity of the device.

In some possible implementations, the first RRC message is an RRC release message or an RRC reconfiguration message, and the RRC release message is used to instruct to release the RRC connection of the first user identity of the device or to indicate The RRC connection of the first user identity of the device enters an inactive state.

In a fourth aspect, the present application provides an apparatus for establishing an RRC connection, including: an obtaining unit, configured to obtain configuration information, where the configuration information is used by a terminal device to establish a radio resource control RRC connection as a second user; Sending a first RRC message to a terminal device with a first user identity, where the first RRC message includes the configuration information.

In some possible implementation manners, the apparatus further includes a determining unit configured to determine that the terminal device supports the first user identity and the first user identity before the first RRC message is sent to the first user identity terminal device. The second user identity.

In some possible implementations, if the configuration information includes the protocol stack parameters of the second user identity, the protocol stack parameters of the second user identity are radio link control RLC layer parameters, media access control MAC layer When at least one of parameters or physical PHY layer parameters, the acquiring unit is further configured to send a request message to the distribution unit DU, where the request message is used to request the protocol stack parameter of the second user identity.

In some possible implementation manners, the transceiving unit is further configured to send a third RRC message to the terminal device of the first user identity, where the third RRC message includes first paging information, and the first paging The information carries the identifier of the second user identity of the terminal device.

In some possible implementation manners, the transceiving unit is further configured to receive a fourth RRC message sent by the terminal device of the first user identity, where the fourth RRC message includes the second user identity of the terminal device Minimize drive test MDT information;

The determining unit is further configured to determine the MDT information of the second user identity according to the fourth RRC message.

In a fifth aspect, the present application provides a device for establishing an RRC connection. The device includes a processor, configured to implement the method described in the first aspect and/or any possible implementation manner thereof. The apparatus may further include a memory, which is coupled with the processor, and the processor is configured to implement the method described in the first aspect and/or any possible implementation manner thereof. Optionally, the processor is configured to store instructions, and when the processor executes the instructions stored in the memory, the method described in the first aspect and/or any possible implementation manner thereof can be implemented. The device may also include a communication interface for the device to communicate with other devices. Exemplarily, the communication interface may be a transceiver, a circuit, a bus, a module, a pin, or other types of communication interfaces.

In a sixth aspect, the present application provides a device for establishing an RRC connection. The device includes a processor, configured to implement the method described in the second aspect and/or any possible implementation manner thereof. The device may further include a memory, the memory is coupled with the processor, and the processor is configured to implement the method described in the above second aspect and/or any possible implementation manner thereof. Optionally, the processor is configured to store instructions, and when the processor executes the instructions stored in the memory, the method described in the second aspect and/or any possible implementation manner thereof can be implemented. The device may also include a communication interface, and the communication interface is used for the device to communicate with other devices.

In a seventh aspect, this application provides a system for establishing an RRC connection, the system including the device provided in the fourth aspect and the device provided in the fifth aspect; or

The system includes the device provided in the fifth aspect and the device provided in the sixth aspect.

In an eighth aspect, this application provides a computer-readable storage medium in which computer instructions are stored. When the computer instructions are run on the computer, the computer can execute the methods in the first aspect and any possible designs thereof. .

In the ninth aspect, the present application provides a computer-readable storage medium in which computer instructions are stored. When the computer instructions are executed on the computer, the computer executes the method in the second aspect and any possible designs thereof .

In a tenth aspect, this application provides a chip including a processor. The processor is used to execute the method in the first aspect and any possible implementation manners thereof.

Optionally, the chip further includes a memory, and the memory is coupled with the processor.

Further optionally, the chip further includes a communication interface.

In an eleventh aspect, the present application provides a chip including a processor. The processor is used to execute the method in the second aspect and any possible implementation manners thereof.

In the twelfth aspect, the present application provides a computer program product, the computer program product includes computer program code, when the computer program code is run on a computer, the computer executes the first aspect and any of its possible designs method.

In a thirteenth aspect, the present application provides a computer program product, the computer program product includes computer program code, when the computer program code runs on a computer, the computer executes the second aspect and any possible implementation manners thereof Methods.

Description of the drawings

Fig. 1 is an architecture diagram of a communication system according to an embodiment of the present application.

Figure 2 is a schematic diagram of an application scenario provided by an embodiment of the present application.

Fig. 3 is a schematic diagram of another application scenario provided by an embodiment of the present application.

Fig. 4 is a schematic diagram of a method for establishing an RRC connection provided by an embodiment of the present application.

Fig. 5 is a schematic diagram of another method for establishing an RRC connection provided by an embodiment of the present application.

Fig. 6 is a schematic diagram of another method for establishing an RRC connection provided by an embodiment of the present application.

Fig. 7 is a schematic diagram of another method for establishing an RRC connection provided by an embodiment of the present application.

Fig. 8 is a schematic diagram of another method for establishing an RRC connection provided by an embodiment of the present application.

Fig. 9 is a schematic diagram of another method for establishing an RRC connection provided by an embodiment of the present application.

Fig. 10 is a schematic diagram of a protocol stack provided by an embodiment of the present application.

Fig. 11 is a schematic diagram of another protocol stack provided by an embodiment of the present application.

Fig. 12 is a schematic diagram of another protocol stack provided by an embodiment of the present application.

FIG. 13 is a schematic diagram of another protocol stack provided by an embodiment of the present application.

FIG. 14 is a schematic diagram of a method for transmitting MDT information provided by an embodiment of the present application.

FIG. 15 is a schematic diagram of a method for reporting a measurement configuration provided by an embodiment of the present application.

FIG. 16 is a schematic block diagram of a device for establishing an RRC connection provided by an embodiment of the present application.

FIG. 17 is a schematic block diagram of another apparatus for establishing an RRC connection provided by an embodiment of the present application.

FIG. 18 is a schematic block diagram of another apparatus for establishing an RRC connection provided by an embodiment of the present application.

Detailed ways

The technical solution in this application will be described below in conjunction with the accompanying drawings.

The technical solutions of the embodiments of this application can be applied to various communication systems, for example: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, broadband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE Time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, the future fifth generation (5th generation, 5G) system or new radio (NR), etc.

The terminal equipment in the embodiments of this application may refer to user equipment, access terminals, user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, or User device. The terminal device can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), with wireless communication Functional handheld devices, computing devices, or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in the future 5G network, or future evolution of the public land mobile network (PLMN) Terminal equipment, etc., which are not limited in the embodiment of the present application.

The network device in the embodiment of the present application may be any device with a wireless transceiver function. This equipment includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC) , Base transceiver station (base transceiver station, BTS), home base station (home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), wireless fidelity (wireless fidelity, WIFI) system access Point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission point, TP) or transmission and reception point (transmission and reception point, TRP), etc., can also be the fifth generation (the fifth generation) , 5G) system, for example, the gNB or transmission point (TRP or TP) in the new radio (NR), one or a group (including multiple antenna panels) antenna panels of the base station in the 5G system, or, It may be a network node that constitutes a gNB or a transmission point, such as a baseband unit (BBU) or a distributed unit (DU).

In some deployments, the gNB may include a centralized unit (CU) and a distributed unit (DU). The gNB may also include an active antenna unit (AAU). The CU implements some of the functions of the gNB, and the DU implements some of the functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implements radio resource control (radio resource control, RRC) and packet data convergence protocol (packet data convergence protocol, PDCP) layer functions. The DU is responsible for processing physical layer protocols and real-time services, and realizes the functions of the radio link control (RLC) layer, media access control (MAC) layer, and physical (PHY) layer. AAU realizes some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU , Or, sent by DU+AAU. It is understandable that the network device may be a device including one or more of CU nodes, DU nodes, and AAU nodes. In addition, the CU can be divided into network equipment in an access network (radio access network, RAN), and the CU can also be divided into network equipment in a core network (core network, CN), which is not limited in this application.

Referring to FIG. 1, FIG. 1 is an architecture diagram of a communication system applicable to an embodiment of the present application. As shown in FIG. 1, the wireless communication system may include at least one network device 101, and the network device 101 communicates with one or more terminal devices (for example, the terminal device 102 and the terminal device 103 shown in FIG. 1). When a network device sends a signal, the network device is the transmitter and the terminal device is the receiver. Conversely, when a terminal device sends a signal, the terminal device is the transmitter and the network device is the receiver.

Figure 2 shows a schematic diagram of an application scenario of an embodiment of the present application. Figure 2 shows that the terminal device supports dual SIM dual standby (dual SIM dual standby, DSDS). In the DSDS scenario, two SIM cards share a single transceiver, and the two SIM cards can be in idle mode at the same time, but when one of the SIM cards receives wireless signals, the other SIM card cannot receive wireless signals. In the idle mode, the two SIM cards keep the signal monitoring of the two cards in a time-division manner. When one of the cards initiates a call, the other card cannot monitor the signal (also cannot initiate a call or be called), and the registration of the second card is maintained.

Figure 3 shows a schematic diagram of another application scenario of the present application. Figure 3 shows that the terminal device supports dual SIM dual active (DSDA). Each SIM card has a separate transceiver and does not depend on each other. The two SIM cards can be in idle mode or connected mode at the same time. model).

It should be noted that the two SIM cards in FIG. 2 and FIG. 3 may belong to the same operator or may belong to different operators, which is not limited in the embodiment of the present application.

In order to facilitate the understanding of the scenario where only two SIM cards are shown in Figure 2 and Figure 3, one terminal device can support multiple SIM cards in practical applications. Therefore, the two SIM cards in Figure 2 and Figure 3 should not cause any damage to the cost. Any limitations of the application examples.

In the embodiment of the present application, "user identity" (for example, the first user identity or the second user identity, etc.) is a logical concept. For example, "user identity" can correspond to SIM card or subscriber information or virtual SIM card or user identity (such as international mobile subscriber identity (IMSI) or temporary mobile subscriber identity (TMSI), etc.) . From the perspective of the network side, different "user identities" logically correspond to different communication entities served by the network side. For example, a terminal device that supports two user identities can be regarded as two communication entities on the network side. Or as two UEs. For another example, when the "user identity" corresponds to the SIM card or subscriber information, the network device will recognize two terminal devices that support different SIM cards or different subscriber information as two different communication entities, and will also support multiple different communication entities. The same terminal device with SIM card or multiple subscriber information is identified as multiple different communication entities, even in reality, the terminal device supporting multiple different SIM cards or multiple subscriber information is just one physical entity. In the embodiments of the present application, description will be made mainly by taking the "user identity" corresponding to the SIM card as an example.

Exemplarily, the SIM card can be understood as the key for the terminal device to access the mobile network. For ease of description, the SIM card and its evolution are collectively referred to as the SIM card in the embodiments of the present application. For example, the SIM card can be an identification card for a user of a global system for mobile communications (GSM) digital mobile phone, which is used to store the user's identification code and key, and supports the authentication of the user by the GSM system; and For example, the SIM card may also be a universal subscriber identity module (USIM), which may also be referred to as an upgraded SIM card.

In the following, the terminal device is installed with a SIM card, which is considered to be that the terminal device supports one user identity. For example, a terminal device with two SIM cards installed can support two user identities. It can be understood that the SIM card and the user identity are one. One corresponding relationship. This article mainly takes the terminal device supporting two user identities as an example. The two user identities are called the first user identity and the second user identity respectively. Among them, the first user identity can be understood as the user identity that the terminal device has after the SIM card 1 is installed, and the second user identity can be understood as the user identity that the terminal device has after the SIM card 2 is installed. In other possible embodiments, if more than two SIM cards are installed in the terminal device, the terminal device also supports more than two user identities. For example, the terminal device supports three user identities, four user identities, or more. User identity can be registered in one or more networks, and each user identity can be registered in one network. The embodiments of this application will mainly be described based on the terminal device supporting two user identities. When the terminal device supports more than two user identities, the specific implementation can refer to the related description of the terminal device supporting two user identities, and some simple things may be required. However, it is also within the protection scope of the embodiments of this application.

Among them, when the user identity of the terminal device is the first user identity, from the perspective of the network device, the terminal device can be understood as a user (from the perspective of the protocol, it is a terminal device, for example, called the first user ); When the user identity of the terminal device is the second user identity, from the perspective of the network device, the terminal device can be understood as another user (for example, referred to as the second user). The terminal device can be registered in the first network as the first user and registered in the second network as the second user. In the embodiment of the present application, the terminal device supports one user identity, which can also be described as the terminal device having one user identity. In the same way, the terminal device supports two user identities, which can also be described as the terminal device having two user identities.

In addition, it should be noted that in the various embodiments of the present application, the "terminal device with the first user identity" can be understood as "the first user identity of the terminal device", as indicated by these two descriptions. The content is the same, and the two descriptions can be interchanged. In the same way, "the terminal device of the second user identity" can be understood as "the second user identity of the terminal device". The content indicated by the two description methods is the same, and the two description methods can be interchanged.

In the scenarios shown in Figure 2 and Figure 3, when the two user identities supported by the terminal device need to initiate a call actively, the RRC connection of the two user identities must be established first, and then the established RRC connection is used to transmit data; the two user identities supported by the terminal device When the user identity is called, the network device will send one or two user identity paging information to the terminal device. After the terminal device receives the paging information, the terminal device establishes one or two user identity RRC connections, and then uses the established RRC connection transmits data.

The following describes the process in which the UE initiates the establishment of an RRC connection in the idle (RRC_IDLE) state with reference to Figure 4 (the random access process in this process is a contention-based random access process.), Figure 4 uses the terminal device as the UE and the network device as the base station To describe, the process of establishing an RRC connection includes the following steps:

S410: The UE sends a random access preamble (preamble) to the base station according to a random access channel (RACH) resource.

For example, the RACH resource may include a random access preamble index (a random access preamble index is used to indicate a random access preamble) and/or a mask index corresponding to the random access resource, and the mask index is used to indicate transmission Random access preamble time-frequency resources.

S420. The base station sends a random access response (RAR) to the UE. The RAR carries uplink authorization information, a temporary cell radio network temporary identifier (T-CRNTI), and a timing advance (T-CRNTI). At least one of TA).

Among them, the uplink authorization information is used to indicate the resources for sending the RRC connection establishment request. For example, the uplink authorization information includes the frequency domain resources, time domain resources, and modulation and coding scheme (MCS) used by the UE to send the RRC connection establishment request. And other information. TA is used for UE to learn uplink timing.

S430: The UE sends an RRC connection establishment request (RRC connection request or RRC set up request) message to the base station on the resource indicated by the uplink authorization information.

Among them, the RRC connection establishment request is transmitted through signaling radio bearer 0 (SRB0). SRB0 uses a common control channel (CCCH) logical channel to transmit RRC messages.

S440: After receiving the RRC connection establishment request, the base station sends an RRC connection setup (RRC connection setup or RRC setup) message to the UE, where the RRC connection setup message includes the configuration information of the UE.

The configuration information includes protocol stack parameters corresponding to Signaling Radio Bearer 1 (Signalling Radio Bearer 1, SRB1), and the configuration information is used to exchange subsequent RRC messages between the UE and the base station. The RRC connection establishment message is used to establish SRB1. SRB1 uses a dedicated control channel (dedicated control channel, DCCH) to transmit RRC messages. The protocol stack parameters include at least one of packet data convergence protocol control (PDCP) layer parameters, RLC layer parameters, MAC layer parameters, and PHY layer parameters.

Optionally, before S440, the base station may first send a contention conflict resolution identification information to the UE. This information carries the bit information of the RRC establishment request message sent by the UE before (for example, the RRC establishment request message sent before exceeds 48 bits, and the contention conflict resolution identification information only carries the first 48 bits, or the RRC connection sent before. The request message does not exceed 48 bits, then the contention conflict resolution identification information carries all the RRC establishment request messages), so that after receiving the information, the UE can compare with the information of the RRC establishment request message sent by itself before, if the contention conflict resolution flag is If the information belongs to the content of the RRC establishment request message sent by itself, it is considered that the base station has received the RRC establishment request message of the UE, and the random access process is successfully completed.

S450: After configuring the protocol stack parameters according to the configuration information, the UE sends an RRC connection setup complete (RRC connection setup complete) message to the base station to indicate that the RRC connection has been established.

Further, the RRC connection establishment complete message may include a non-access stratum (non-access, NAS) message, and the base station transparently transmits the NAS message to the core network.

The main purpose of the RRC connection establishment process is to establish SRB1 and send the NAS message on the UE side to the network side. After S450. The base station can configure the configuration information corresponding to the data radio bearer (DRB) for the UE according to the service requirements of the UE. DRB is used to define the processing strategy of data packets in the wireless interface Uu. DRB is used to transmit data packets. The configuration information corresponding to the DRB includes protocol stack parameters corresponding to the DRB. The protocol stack parameters corresponding to DRB include service data adaptation protocol (SDAP) layer parameters, packet data convergence protocol control (PDCP) layer parameters, RLC layer parameters, MAC layer parameters, and PHY layer parameters. At least one of the parameters.

After the RRC connection establishment process, security activation of the access layer will be performed between the base station and the UE, that is, an interactive security mode command process. The base station sends a safety mode command message to the UE, and the UE sends a safety mode complete message to the base station. The security mode command message carries an encryption algorithm and an integrity protection algorithm. After receiving the security mode command message, the UE derives the key K _gNB or K _eNB . The UE then derives the security key for integrity protection of RRC signaling based on the key K _gNB or K _eNB , the security key for encryption of RRC signaling, the security key for integrity protection of user data, and the encryption of user data. Security key. The specific derivation algorithm can refer to the protocol 3GPP 33.501 or 33.401.

Normally, in addition to initiating the random access process in the idle (RRC_IDLE) state of Figure 4, the random access process also needs to be initiated in the following five situations:

Case 1, RRC Connection Re-establishment procedure, so that the UE reestablishes the wireless connection after the radio link failure. Or the UE initiates an RRC Resume procedure from the RRC_INACTIVE state, so that the UE sends some information to the base station (for example, data transmission when the UE enters the RRC_CONNECTED state). The two scenarios are similar to the process of the UE establishing RRC in the RRC_IDLE state. The UE sends a random access preamble and receives a random access response sent by the base station. The uplink grant information carried in the random access response indicates that the UE sends an RRC reestablishment request (RRCConnectionReestablishmentRequest or RRCReestablishmentRequest) message or an RRC recovery request (RRCConnectionResumeRequest or RRCResumeRequest) message Resources. After that, the UE sends an RRC reestablishment request or an RRC resume request message and receives an RRC reestablishment message (RRCConnectionReestablishment or RRCReestablishment) or an RRC resume message (RRCConnectionResume or RRCResume) sent by the base station. Finally, the UE sends an RRC reestablishment complete message (RRCConnectionReestablishmentComplete or RRCReestablishmentComplete) or an RRC reestablishment complete message (RRCConnectionResumeComplete or RRCResumeComplete). These procedures are for the UE to establish SRB or/and DRB.

The second situation is a handover process. After the handover, the UE needs to establish uplink synchronization with a new cell.

Case 3: In the RRC connection (RRC_CONNECTED) state, when the downlink data arrives (the ACK/NACK needs to be replied at this time), the uplink is in the "unsynchronized" state.

Case 4: In the RRC connection state, when the uplink data arrives (for example, it needs to report a measurement report or send user data), and the UE needs to report a buffer status report (buffer status report, BSR), if there is no uplink resource available for uplink data transmission Or when the uplink resources currently available for uplink data transmission are not satisfied, a scheduling request (scheduling request, SR) is triggered. SR is used to request uplink resources. If there is no PUCCH resource available for the scheduling request in the uplink, the UE initiates a random access procedure to request the base station to schedule the UE for uplink data.

Case 5: In the RRC connected state, the UE performs beam management. When the UE detects that the beam signal quality is below a certain threshold, the UE will select other beams for random access and notify the base station to change the corresponding beam.

When the UE is already in the RRC_CONNECTED state and needs to initiate a competing random access process (such as the above cases two, three, four, and five), the above S410 and S420 need to be performed, and then the UE sends a cell radio network temporary identification (cell Radio network temporary identifier (C-RNTI) MAC control element. After that, if the UE receives the PDCCH scrambled with the C-RNTI, it is considered that the current random access procedure is successful.

For the RRC reconstruction process in the above case 1, the base station will carry the parameter for updating the key in the RRC reconstruction message.

In addition, the random access process mentioned above is generally called a 4-step random access process. At present, a 2-step random access procedure is also proposed. The 2-step random access process means that after the UE sends the random access preamble, it does not need to wait for the base station to send the random access response before sending the RRC connection establishment request message or the RRC reestablishment request message or the RRC recovery request message or carrying C- The MAC control element of RNTI (that is, the above information can be sent before the random access response is received), and then the base station will send response information to the UE. The response information can indicate that the UE has succeeded in random access or that the UE has returned to normal Random access (that is, the UE directly sends an RRC connection establishment request message or an RRC reestablishment request message or an RRC recovery request message or a MAC control element carrying C-RNTI) or instructs the UE to postpone a period of time before performing 2-step random access.

The terminal device supports multiple user identities (it can also be understood that the terminal device supports multiple SIMs). The terminal device needs to initiate competitive or non-competitive random access during the establishment of an RRC connection. For competing random access, due to limited resources, the terminal Devices need to compete for resources for multiple user identities, which will increase the delay of random access, and even cause random access failures, resulting in a decrease in transmission performance; for non-competitive random access, multiple user identities are required for terminal equipment Occupying more random access resources will increase the resource overhead of random access. In addition, whether it is competitive random access or non-competitive random access, the process of random access will also increase the delay in establishing the RRC connection. Taking Figure 4 as an example, for competing random access, the terminal device needs to compete for random access resources (such as RACH resources) for two user identities (both user identities are in the RRC_IDLE state), which results in high signaling overhead and delay Longer. Specifically, before S410, the terminal device needs to preempt RACH resources for two user identities and use the RACH resource to send the preamble. It is very likely that the terminal device cannot preempt resources for a certain user identity, resulting in random access failure; Or a user identity of the terminal device and user identities of other terminal devices may use the same RACH resource for access, so the base station cannot distinguish which user identities need to be accessed, which may cause the base station to fail to detect the random access preamble, so the same The two user identities of the RACH resource need to re-send the random access preamble, which leads to an increase in the random access delay. Or the base station detects the same random access preamble on the same RACH resource, but the base station will only send one random access response, so that both user identities will send the RRC establishment request message according to the uplink authorization information in the random access response. However, the base station will only send the contention conflict resolution identification information to one user identity (that is, carry the bit information of the RRC establishment request message sent by one user identity), and the other user identity will consider that the conflict resolution has failed, and then resend random access. Preamble, so that the access delay of the user identity will increase.

The method for establishing an RRC connection provided by an embodiment of the present application will be described below in conjunction with FIG. 5 to FIG. 15.

FIG. 5 shows a method 500 for establishing an RRC connection provided by an embodiment of the present application. The method 500 includes:

S510: The network device obtains configuration information, and the configuration information is used to assist the terminal device in establishing an RRC connection as the second user.

The network device can generate configuration information for the second user identity of the terminal device,

The network device can also obtain configuration information from other network devices. For example, the configuration information is obtained from other network devices through the Xn or X2 interface between the network devices. For example, the network device corresponding to the first user identity sends a request message to the network device corresponding to the second user identity, and then the network device corresponding to the second user identity sends the configuration information to the network device corresponding to the first user identity.

For example, under the CU-DU architecture, the first user identity and the second user identity can belong to the same CU but belong to different DUs. The network device can be a CU. If the configuration information includes the second user identity, the protocol stack parameter is wireless At least one of radio link control (RLC) layer parameters, media access control (MAC) layer parameters, or physical (PHY) layer parameters, due to the RLC layer parameters of the second user identity The MAC layer parameters and PHY layer parameters are allocated by the DU. Therefore, the CU needs to send a request message to the DU. The request message is used to request the RLC layer parameters, MAC layer parameters and PHY layer parameters of the second user identity. The DU of the second user identity returns to the CU at least one parameter of the RLC layer parameter, the MAC layer parameter, and the PHY layer parameter of the second user identity. For example, the CU may send the request message to the DU of the second user identity through a non-UE-level interface. For another example, the request message may be an F1 interface establishment message, and the F1 interface establishment message is for the user to establish an F1 interface between the CU and the DU of the second user identity. Or when the DU corresponding to the first user identity and the second user identity are the same, the DU is requested to allocate the corresponding configuration information through the F1 interface message corresponding to the first user identity between the CU and the DU (optionally, the interface message also includes It carries the cell identifier, which is used to indicate which cell in the DU is requested to allocate the corresponding configuration information).

It should be noted that in the embodiment of the present application, the first user identity and the second user identity may have the same service network element or different service network elements. For example, the network device in S510 may be a base station. The base station may be a serving base station sharing the first user identity and the second user identity, the base station may also be a serving base station of the first user identity, and the base station may obtain configuration information of the second user identity from the serving base station of the second user identity.

S520: The network device sends a first RRC message of the first user identity to the terminal device, and the terminal device receives the first RRC message sent by the network device, where the first RRC message includes configuration information.

Optionally, the first RRC message may be an RRC release message or an RRC reconfiguration (RRC reconfiguration) message. For example, the RRC release message is used to instruct the terminal device to release the RRC connection of the first user identity, and accordingly, the network device can release the service data connection and the RRC connection of the first user identity. Optionally, the RRC release message is used to instruct the terminal device to suspend the RRC connection of the first user identity or to indicate that the service data connection of the first user identity of the terminal device enters an inactive state. Accordingly, the network device can suspend the first user identity. The service data connection and RRC connection of the user identity. Optionally, the RRC reconfiguration message is used to indicate that the terminal device can maintain the service data connection and the RRC connection of the first user identity, and accordingly, the network device can maintain the service data connection and the RRC connection of the first user identity.

Optionally, before S520, the network device determines that the terminal device supports the first user identity and the second user identity. Only when the network device determines that the terminal device supports the first user identity and the second user identity, can it send the configuration information for assisting the terminal device to establish an RRC connection with the second user identity through the first RRC message of the first user identity .

Specifically, the network device may determine that the terminal device supports the first user identity and the second user identity through at least one of the following methods:

Manner 1: The network device receives the paging information of the terminal device paging the second user identity from the core network device. The paging information carries the interface identity of the first user identity. For example, the interface identity includes that the first user identity is on the NG port. Or the control plane interface identification of the S1 port. Among them, the NG port is the interface between the base station and the 5G core network 5GC, and the S1 is the interface between the base station and the 4G core network EPC. The network device may determine that the terminal device supports both the first user identity and the second user identity according to the interface identity of the first user identity carried in the paging information of the terminal device paging the second user identity.

Manner 2: The network device receives a message (for example, an NG port message or an S1 port message) sent by the core network device through the interface of the first user identity and carries the paging information for paging the terminal device of the second user identity, and the network device It may be determined that the terminal device supports the first user identity and the second user identity at the same time according to the message sent through the interface of the first user identity that carries the terminal device that pages the second user identity.

Manner 3: The terminal device may actively send to the network device indication information indicating that the terminal device supports both the first user identity and the second user identity, and the network device may determine that the terminal device supports both the first user identity and the second user identity according to the indication information. Optionally, the indication information may also carry the identity of the cell corresponding to the second user identity (physical cell identity or global cell identity). For example, the network device sends paging information for paging the second user identity to the terminal device, and after the terminal device receives the paging information for paging the second user identity, the terminal device actively sends indication information to the network device. Or when the terminal device actively initiates the establishment of the RRC connection with the second user identity, the terminal device actively sends the indication information to the network device.

S530: The terminal device uses the identity of the second user to establish an RRC connection according to the configuration information.

It should be noted that S530 can be understood in at least one of the following ways:

a) The establishment of an RRC connection by the terminal device as the second user based on the configuration information can be understood as: the terminal device inherits the RRC connection established by the first user as the second user according to the configuration information, and the configuration information is used to instruct the terminal device to The second user identity uses the RRC connection established by the terminal device as the first user identity, so that the terminal device does not need to initiate random access as the second user identity, nor does it need to send the RRC establishment request message as the second user identity to establish the RRC connection. In this way, the signaling overhead caused by the terminal device needing to perform steps S410-S450 in FIG. 4 for the second user identity can be avoided, and the random access delay for the terminal device to initiate the second user identity can also be reduced.

Specifically, the configuration information is used to instruct the terminal device to use the terminal device as the second user. The RRC connection established as the first user may specifically be: the configuration information is used to instruct the terminal device to use the first user of the terminal device as the second user. At least one of the SRB1, SRB2, and key of the identity.

Further, in a), the configuration information may include wireless configuration information of the second user identity. The wireless configuration information includes protocol stack parameters (such as the protocol stack parameters of SRB1) and/or the key information of the second user identity (the key information may include the key of the second user identity (for example, the network device can be based on the first user identity). The key derives the key of the second user identity), or the information used to generate the second user identity key), the terminal device can be based on the current wireless configuration information of the first user identity, and then according to the second user The wireless configuration information of the identity is modified to obtain the protocol stack parameters corresponding to the RRC connection corresponding to the second user identity (for example, the protocol stack parameters of SRB1).

Optionally, in a), after the RRC connection of the first user identity is used by the second user identity of the terminal device, the RRC connection can no longer be used by the first user identity of the terminal device.

b) The terminal device establishes an RRC connection with the second user identity according to the configuration information. It can be understood that the terminal device uses the configuration information to initiate random access with the second user identity, and the configuration information may include random access channels (random access). channel, RACH) resources. In this way, the terminal device does not need to use competing random access resources for random access in a competitive manner as the second user, but directly uses random access channel resources included in the configuration information to perform random access in a non-competitive manner, which can improve random access. The success rate can also reduce the delay of random access.

For example, the RACH resource may include a random access preamble index (the random access preamble index is used to indicate the random access preamble) and/or the mask index corresponding to the random access resource, and the mask index is used to indicate the sending of the random access preamble. Time-frequency resources.

Optionally, the random access of the second user identity may be to establish an RRC connection, and an RRC connection may be established for the first time in an idle state, or an RRC connection may be established during an RRC reestablishment process, or an RRC connection may be established during an RRC recovery process.

Optionally, the second user identity can use the random access channel resource to perform 4-step random access or perform 2-step random access. When performing 2-step random access, the configuration information may also carry the uplink authorization information for establishing the RRC connection with the second user identity. The uplink grant information is used to indicate the resource for sending the RRC setup request message or the RRC reestablishment request message or the RRC recovery request message or the MAC control element carrying the C-RNTI. For example, the uplink authorization information includes the uplink scheduling interval of the second user identity, the uplink starting subframe number of the second user identity, and the uplink authorization of the second user identity. The uplink authorization includes information such as frequency domain resources, time domain resources, and MCS used to send uplink information.

c) The establishment of an RRC connection by the terminal device as the second user identity according to the configuration information can be understood as: the terminal device uses the configuration information to establish the RRC connection as the second user identity. For example, the configuration information may include At least one of the uplink authorization information for establishing the RRC connection with the user identity and the identity of the second user in the cell where the terminal device establishes the RRC connection with the second user identity (for example, the cell radio network temporary identity C-RNTI) In one type, the uplink grant information is used to indicate the resource for sending the RRC establishment request message or the RRC reconstruction request message or the RRC recovery request message. In this way, it can be avoided that the terminal device needs to send the random access preamble as the second user identity, and needs to obtain the uplink authorization information of the second user identity and the delay caused by the C-RNTI in the random access response sent by the network device. And overhead. For example, in method 400, it can be avoided that the terminal device needs to perform steps S410-S420 for the second user identity. The terminal device directly sends the second user identity RRC connection establishment request to the network device on the resource indicated by the uplink authorization information. Message, the second user identity can use the identity of the second user identity to communicate with the network side.

For example, the uplink authorization information includes the uplink scheduling interval of the second user identity, the uplink starting subframe number of the second user identity, and the uplink authorization of the second user identity. The uplink authorization includes information such as frequency domain resources, time domain resources, and MCS used to send uplink information.

d), the terminal device establishes an RRC connection according to the configuration information as the second user identity, which can be understood as: the terminal device uses the first user identity and the second user identity at the same time the terminal device uses the RRC connection established as the first user identity, then the terminal device does not Random access is initiated as the second user, and there is no need to establish an RRC connection as the second user. This can avoid the delay and overhead caused by the terminal device needing to initiate the RRC connection as the second user. For example, in the method In 400, the signaling overhead caused by the terminal device needing to perform steps S410-S450 in FIG. 4 for the second user identity can be avoided, and the random access delay for the terminal device to initiate the second user identity can also be reduced. In addition, the RRC connection established by the first user identity can continue to be used by the first user identity of the terminal device, which can improve the utilization rate of the RRC connection of the first user identity.

Further, in d), the configuration information may include wireless configuration information of the second user identity. The wireless configuration information includes protocol stack parameters and/or key information of the second user identity (the key information may include the key of the second user identity (for example, the network device can derive the second user identity from the key of the first user identity) Key), or information used to generate the key of the second user identity), the terminal device can be based on the current wireless configuration information of the first user identity, and then according to the second user identity included in the configuration information The wireless configuration information is modified to obtain the protocol stack parameters corresponding to the RRC connection corresponding to the second user identity (for example, the protocol stack parameters of SRB1).

Further, in d), the configuration information may also include the configuration information of the DRB of the second user identity, and the terminal device may use the second user identity to perform user data transmission of the second user identity according to the configuration information of the DRB.

In d), the first user identity and the second user identity may have different RRC layers, and the different RRC layers may serve terminal devices with different user identities at the same time.

Specifically, in d), if the terminal device uses the RRC connection established by the terminal device as the first user identity at the same time as the first user identity and the second user identity, the terminal device retains the protocol stack parameters of the first user identity and the first user identity at the same time. Two protocol stack parameters of the user identity, and/or, the terminal device can retain the key of the first user identity and the key of the second user identity at the same time.

e) The establishment of the RRC connection by the terminal device as the second user identity according to the configuration information can be understood as: the terminal device uses the first user identity and the second user identity in a time-division multiplexing manner to establish the RRC connection as the first user identity RRC connection. This can avoid the time delay and overhead caused by the terminal device needing to initiate the RRC connection as the second user. For example, in the method 400, it can avoid the terminal device needing to perform steps S410-S450 in FIG. 4 again for the second user identity. The resulting signaling overhead can also reduce the random access delay for the terminal device to initiate the second user identity. In addition, the RRC connection established by the first user identity can continue to be used by the first user identity of the terminal device, which can improve the utilization rate of the RRC connection of the first user identity.

Further, in e), the configuration information may include wireless configuration information of the second user identity. The wireless configuration information includes protocol stack parameters and/or key information of the second user identity. The terminal device can modify the wireless configuration information of the second user identity on the basis of the current wireless configuration information of the first user identity, In this way, the protocol stack parameters corresponding to the RRC connection corresponding to the second user identity (such as the protocol stack parameters of SRB1) are obtained.

In e), the first user identity and the second user identity can have the same RRC layer (RRC entity), and the same RRC layer can serve terminal devices with different user identities at different times, and only Can serve a user identity. That is, the first user identity and the second user identity use the RRC layer in a time division manner.

Specifically, in e), if at a certain moment, the RRC connection established by the terminal device as the first user identity can only be used by the second user identity of the terminal device, so that the terminal device can use the protocol stack parameters corresponding to the second user identity , At the next moment, the terminal device as the first user identity can continue to use the RRC connection established by the terminal device as the first user identity, and the terminal device uses the protocol stack parameters corresponding to the first user identity; or, in e), at a certain moment The RRC connection established by the terminal device as the first user identity can only be used by the second user identity of the terminal device, so that the terminal device can modify the key of the first user identity to the key of the second user identity. At the next moment, the terminal The device as the first user identity can continue to use the RRC connection established by the terminal device as the first user identity, and the terminal device can modify the key of the second user identity to the key of the first user identity.

Optionally, the first user identity and the second user identity may have different RRC layers (RRC entities), and RRC entities corresponding to different user identities may be used to serve the terminal device at different times. At a certain moment, the RRC connection established by the terminal device as the first user identity can only be used by the second user identity of the terminal device, so that the terminal device uses the RRC entity of the second user identity to provide services for the second user identity. At the next moment, the terminal device as the first user identity can continue to use the RRC connection established by the terminal device as the first user identity, and the terminal device uses the RRC entity of the first user identity to provide services for the first user identity. Or, the RRC connection established by the terminal device as the first user at a certain moment can only be used by the second user identity of the terminal device, so that the terminal device can use the key of the second user identity. At the next moment, the terminal device uses the first user identity. The user identity can continue to use the RRC connection established by the terminal device as the first user identity, and the terminal device can use the key of the first user identity.

Further, in e), the configuration information may also include configuration information of the DRB of the second user identity, and the second user identity may use the second user identity to perform user data transmission corresponding to the second user identity according to the configuration information of the DRB.

In the above d) and e), after the terminal device receives the first RRC message, it is possible that the first RRC message includes information about the identity of the first user, or it may include information about the identity of the second user in the first RRC message, or It is possible that the first RRC message includes the identity information of the first user and the identity information of the second user. The terminal device needs to determine whether the RRC connection of the first user identity can be used by the second user identity. In other words, the terminal device needs to determine whether the second user identity information is included in the first RRC message. For example, the information may be the aforementioned configuration information. Whether the RRC connection of the first user identity can be used by the second user identity can be determined by at least one of the following methods.

Manner 1: If the first RRC message includes the second RRC message of the second user identity of the terminal device, and the second RRC message includes configuration information, the terminal device can determine that the terminal device can use the first RRC message according to the second RRC message included in the first RRC message. Second, the user identity uses the RRC connection established by the terminal device as the first user identity. That is, in the first way, the RRC connection established as the first user using the terminal device as the second user can be determined through the nesting of RRC messages.

In the first manner, if the first RRC message includes other information of the first user identity in addition to the second RRC message, the first RRC message is shared by the first user identity and the second user identity. That is, the first RRC message carries information about the identity of the first user and the identity of the second user at the same time.

If the first RRC message includes other information of the first user identity in addition to the second RRC message, the first RRC message is shared by the first user identity and the second user identity, and the first user identity and the second user identity of the terminal device are shared. The two user identities can use the RRC connection established by the terminal device as the first user at the same time; if the first RRC message does not include any other information of the first user identity except the second RRC message, the first RRC message is the second In the RRC message of the user identity, the terminal device uses the RRC connection established with the first user identity by the terminal device as the second user identity.

Optionally, the network device may send indication information for using the RRC connection to the terminal device, and the specific indication information for using the RRC connection is used to indicate: if the first RRC message includes the first user identity in addition to the second RRC message For other information, the first RRC message is shared by the first user identity and the second user identity, and the first user identity and the second user identity of the terminal device can use the RRC connection established by the terminal device as the first user identity at the same time; If an RRC message does not include any other information about the identity of the first user except the second RRC message, the first RRC message is an RRC message with the identity of the second user, and the terminal device uses the terminal device as the second user as the first user. The RRC connection established by the identity.

Manner 2: The first RRC message includes first indication information, and the first indication information is used to indicate that the configuration information included in the first RRC message is used for the terminal device to establish as the second user identity RRC connection, so that the terminal device can determine, according to the first indication information included in the first RRC message, that the terminal device can use the RRC connection established by the terminal device as the first user as the second user. That is, in the second manner, an explicit indication in the first RRC message can be used to determine the RRC connection established as the first user using the terminal device as the second user. For example, the radio bearer configuration in the first RRC message may carry the first indication information.

In the second method, if the first RRC message includes other information of the first user identity in addition to the first indication information and configuration information, the first RRC message is shared by the first user identity and the second user identity, and the terminal The first user identity and the second user identity of the device can simultaneously use the RRC connection established by the terminal device as the first user identity; if the first RRC message does not include any information about the first user identity except for the first indication information and configuration information For other information, the first RRC message is an RRC message of the second user identity, and the terminal device uses the RRC connection established with the first user identity by the terminal device as the second user identity.

Optionally, the network device may send indication information for using the RRC connection to the terminal device. The specific indication information for using the RRC connection is used to indicate: if the first RRC message includes the first indication information and configuration information, it also includes the first indication information and configuration information. For other information of the user identity, the first RRC message is shared by the first user identity and the second user identity, and the first user identity and the second user identity of the terminal device can use the RRC connection established by the terminal device as the first user identity at the same time ; If the first RRC message does not include any other information about the identity of the first user except for the first indication information and configuration information, the first RRC message is an RRC message with the identity of the second user, and the terminal device uses the identity of the second user The RRC connection established by the terminal device as the first user.

Manner 3: The cell where the configuration information of the different user identities of the terminal device is located is in different positions of the first RRC message, and the terminal equipment can determine whether the cell where the configuration information of the second user identity is located is present. The middle terminal device may use the RRC connection established by the terminal device in the identity of the first user as the second user. The protocol may stipulate that the information elements in which the network equipment configures the configuration information of different user identities of the terminal equipment are located in different positions of the first RRC message.

For example, the information element where the configuration information is located at position 1 of the RRC message indicates that the configuration information is the first user identity of the terminal device, and the information element where the configuration information is located at position 2 of the RRC message indicates that the configuration information is that of the terminal device. The identity of the second user. In this way, the terminal device receives the first RRC message, and the cell containing the configuration information in the first RRC message is in position 2 of the first RRC message, and the terminal device can determine that the configuration information is the identity of the second user, so that the terminal device can determine Use the terminal device as the second user to establish an RRC connection with the identity of the first user; or the terminal device receives the first RRC message, and the first RRC message has configuration information in position 1 and configuration information in position 2, and the terminal device can determine The first RRC message is shared by the first user identity and the second user identity, and the terminal device can use the first user identity and the second user identity to jointly use the RRC connection established by the terminal device with the first user identity.

In the above d) and e), after the terminal device receives the first RRC message, the first RRC message may include the non-access stratum (non-access, NAS) message of the first user identity, and may also include the first user identity The NAS message and the NAS message of the second user identity may also include the NAS message of the second user identity. If the first RRC message includes a NAS message, the terminal device needs to determine that the NAS message is the NAS message of the first user identity It is also the NAS message of the second user identity. It may be determined whether the NAS message included in the first RRC message belongs to the first user identity or the second user identity through at least one of the following methods.

Manner 1: If the first RRC message includes the fifth RRC message of the second user identity of the terminal device, and the fifth RRC message includes the NAS message, the terminal device can determine that the NAS message is the first RRC message according to the fifth RRC message included in the first RRC message. 2. NAS message of user identity. That is to say, in mode one, the user identity of the NAS message can be determined through the nesting of the RRC message.

It is understandable that if the terminal device determines that the NAS message is the second user identity according to the fifth RRC message, it can also be considered that the terminal device can use the RRC connection established by the terminal device as the first user identity as the second user identity.

Optionally, the fifth RRC message may be the aforementioned second RRC message, that is, the first RRC message of the first user identity includes a second RRC message, and the second RRC message includes configuration information and a NAS message. The terminal device may determine the If the configuration information and the NAS message are the identity of the second user, it can also be understood that the terminal device can use the identity of the second user to use the terminal device to establish an RRC connection with the identity of the first user.

Manner 2: The first RRC message includes second indication information, and the second indication information is used to indicate that the NAS message included in the first RRC message is a NAS message with a second user identity, so that the terminal device can follow the first The second indication information included in the RRC message determines that the NAS message is the second user identity. That is, in the second mode, it can be determined whether the NAS message belongs to the first user identity or the second user identity through an explicit indication in the first RRC message.

It is understandable that if the terminal device determines that the NAS message is the second user identity according to the second indication information, it can also be considered that the terminal device can use the RRC connection established by the terminal device as the first user identity as the second user identity.

Optionally, the first RRC message may include a NAS message, configuration information, first indication information, and second indication information. The first indication information is used to indicate that the configuration information is the identity of the second user, and the second indication information is used to indicate the NAS If the message is the second user identity, the terminal device can determine that the NAS message and configuration information are both the second user identity according to the first indication information and the second indication information, and it can also be understood that the terminal device can use the terminal as the second user identity The RRC connection established by the device as the first user.

Manner 3: The cell of the NAS message with different user identities of the terminal device is located at a different position of the first RRC message, and the terminal device determines that the NAS message is based on the position of the cell containing the NAS message in the first RRC message The identity of the first user is still the identity of the second user. The protocol may stipulate that the network device configures the cell in which the NAS message of different user identities of the terminal device is located in different positions of the first RRC message.

For example, the cell where the NAS message is located at position 3 of the RRC message indicates that the NAS message is the first user identity of the terminal device, and the cell where the NAS message is located is at position 4 of the RRC message, which indicates that the NAS message is for the terminal device. The identity of the second user. In this way, the terminal device receives the first RRC message, and the cell where the NAS message in the first RRC message is located is at position 4 of the first RRC message, and the terminal device can determine that the NAS message is of the second user identity; or the terminal device receives the first RRC message. For an RRC message, the location 3 of the first RRC message has a NAS message, and the location 4 also has a NAS message, the terminal device can determine that the NAS message of location 3 is the identity of the first user, and the NAS message of location 4 is the identity of the second user.

It is understandable that if the terminal device determines that the NAS message is the second user identity according to the cell where the NAS message is located, it can also be considered that the terminal device can use the terminal device as the second user identity to establish the RRC connection with the first user identity.

Optionally, in combination with the above example, position 1 of the first RRC message includes configuration information, and position 3 includes a NAS message. The terminal device can determine that the configuration information of position 1 and the NAS message of position 3 are the identity of the second user, or It is understood that the terminal device can use the RRC connection established by the terminal device as the first user as the second user.

The foregoing manners of determining the configuration information and the NAS message as the identity of the second user can be combined. The following examples can illustrate:

Example 1: The first RRC message includes the second RRC message of the second user identity, the NAS message, and the second indication information, the second RRC message includes configuration information, and the terminal device determines that the NAS message is second according to the second indication information. For the user identity, the terminal device may determine that the configuration information is the second user identity according to the second RRC message.

Example 2: The first RRC message includes configuration information, a NAS message, and second indication information. The cell where the configuration information is located is at the position of the first RRC message 2. The terminal device determines that the NAS message is the second user according to the second indication information. For the identity, the terminal device may determine that the configuration information is also the identity of the second user according to the location of the cell where the configuration information is located.

Example 3: The first RRC message includes the fifth RRC message, configuration information, and first indication information. The fifth RRC message includes the NAS message. If the terminal device can determine that the configuration information is the second user identity according to the first indication information, the terminal device may It is determined according to the fifth RRC message that the NAS message is the identity of the second user.

Example 4: The first RRC message includes the first indication information, the second indication information, the configuration information, and the NAS message. If the terminal device can determine that the configuration information is the second user identity according to the first indication information, the terminal device can according to the second indication information It is determined that the NAS message is the identity of the second user.

It is understandable that if the terminal device determines that the configuration information and/or the NAS message included in the first RRC message is the second user identity, it can be understood that the terminal device can use the terminal device to establish the identity of the first user as the second user. RRC connection.

It should be noted that the above is for the convenience of description, and only illustrates that the configuration information and/or NAS message included in the first RRC message are determined as the second user identity, and the first RRC message may also include the configuration information of the first user identity and/or Or NAS message, the configuration information of the first user identity and/or the NAS message is similar to the configuration information and/or NAS message of the second user identity, for example, the first RRC message includes first indication information, third indication information, and configuration information 1 and configuration information 2. The first indication information is used to indicate that the configuration information 1 is the identity of the second user, and the third indication information is used to indicate that the configuration information 2 is the identity of the first user. In order to avoid repetition, it will not be described in detail here.

Optionally, the first RRC message may include a correspondence, the correspondence is used to indicate that different bearers correspond to different user identities, or the correspondence is used to indicate that different logical channels of the same bearer correspond to different user identities, or The correspondence relationship is used to indicate that different keys correspond to different user identities, or the correspondence relationship is used to indicate that different C-RNTIs correspond to different user identities, or the correspondence relationship is used to indicate different bandwidths. Part of the BWP corresponds to different user identities, or the correspondence relationship is used to indicate that different subcarrier intervals correspond to different user identities, and the correspondence relationship is used by the terminal device to determine the first user identity or the second user identity. user ID.

Specifically, after the terminal device subsequently receives the data packet (the data packet includes the RRC message transmitted via SRB and/or the data transmitted via DRB), since the terminal device supports both the first user identity and the second user identity, the terminal device needs It is determined whether the data packet belongs to the first user identity or the second user identity. For example, the corresponding relationship is used to indicate that bearer 1 corresponds to the first user identity, and bearer identity 2 corresponds to the second user identity. If the bearer corresponding to the data packet received by the terminal device is bearer 1 (for example, the logical channel identity carried by the MAC layer knows this The data packet corresponds to bearer 1), then the data packet is sent by the network device to the terminal device with the first user identity. If the terminal device receives the data packet as bearer 2 (for example, the data is learned through the logical channel identifier carried by the MAC layer) The packet corresponds to bearer 2), and the data packet is sent by the network device to the terminal device of the second user identity. For another example, the bearer identifiers of the data packets of the two user identities of the terminal device may be the same, and the corresponding relationship may indicate that the logical channel 1 of bearer 1 corresponds to the first user identity, and the logical channel 2 of bearer 1 corresponds to the second user identity. The bearer of the received data packet is bearer 1 and the logical channel of bearer 1 is logical channel 1 (for example, the logical channel identifier carried by the MAC layer knows that the data packet corresponds to logical channel 1), then the data packet is sent by the network device to the first A terminal device with a user identity; if the bearer of the data packet received by the terminal device is bearer 1 and the logical channel of bearer 1 is logical channel 2 (for example, the logical channel identifier carried by the MAC layer knows that the data packet corresponds to logical channel 2) , The data packet is sent by the network device to the terminal device of the second user identity. For another example, the correspondence relationship may indicate that key 1 corresponds to the first user identity, and key 2 corresponds to the second user identity. After the terminal device receives the data packet, the terminal device tries to use the key 1 and key 2 to decrypt the data packet. If the device can correctly decode the data packet using key 1, the data packet is sent by the network device to the terminal device of the first user identity; if the terminal device can correctly decode the data packet using key 2, the data packet is sent by the network device To the terminal device of the second user identity. For another example, the correspondence relationship may indicate that C-RNTI1 corresponds to the first user identity, and C-RNTI2 corresponds to the second user identity. If the terminal device uses C-RNTI 1 to receive the physical downlink control channel (PDCCH) (for example, through C-RNTI 1 successfully descrambles the PDCCH), the scheduling data indicated in the PDCCH is the first user identity, that is, the data carried in the physical downlink shared channel (PDSCH) indicated in the PDCCH is The identity of the first user. If the terminal device uses the C-RNTI 2 to receive the physical downlink control channel (PDCCH) (for example, the PDCCH is successfully descrambled through the C-RNTI 2), the scheduling data indicated in the PDCCH is the second user identity Yes, that is, the data carried in the physical downlink shared channel (PDSCH) indicated in the PDCCH is the identity of the second user. For another example, the correspondence relationship may indicate that the bandwidth part (BWP) 1 corresponds to the first user identity, and BWP2 corresponds to the second user identity. If the terminal device receives a data packet from BWP1, the terminal device can determine that the data packet is sent by the network device. For the terminal device of the first user identity, if the terminal device receives a data packet from the BWP2, the terminal device can determine that the data packet is sent by the network device to the terminal device of the second user identity. For another example, the correspondence relationship may indicate that subcarrier interval 1 corresponds to the first user identity, and subcarrier interval 2 corresponds to the second user identity. If the terminal device receives a data packet from the physical channel corresponding to subcarrier interval 1, the terminal device can determine the The data packet is sent by the network device to the terminal device of the first user. If the terminal device receives the data packet from the physical channel corresponding to the subcarrier interval 2, the terminal device can determine that the data packet is sent by the network device to the second user The identity of the terminal equipment.

Correspondingly, in combination with the above example, after the network device subsequently receives the data packet (here including the RRC message transmitted via SRB and/or the data transmitted via DRB), since the terminal device supports both the first user identity and the second user identity, the network The device needs to determine whether the data packet belongs to the first user identity or the second user identity. For example, the corresponding relationship is used to indicate that the bearer 1 corresponds to the first user identity, and the bearer identity 2 corresponds to the second user identity. If the bearer corresponding to the data packet received by the network device is bearer 1 (for example, the logical channel identity carried by the MAC layer knows this The data packet corresponds to bearer 1), then the data packet is sent by the terminal device to the network device as the first user. If the bearer of the data packet received by the network device is bearer 2 (for example, the logical channel identifier carried by the MAC layer knows the data packet The data packet corresponds to bearer 2), and the data packet is sent by the terminal device to the network device as the second user. For another example, the bearer identifiers of the data packets of the two user identities of the terminal device may be the same, and the corresponding relationship may indicate that the logical channel 1 of bearer 1 corresponds to the first user identity, and the logical channel 2 of bearer 1 corresponds to the second user identity. The bearer of the received data packet is bearer 1 and the logical channel of bearer 1 is logical channel 1 (for example, the logical channel identifier carried by the MAC layer knows that the data packet corresponds to logical channel 1), then the data packet is a terminal device. A user identity is sent to the network device; if the bearer of the data packet received by the network device is bearer 1 and the logical channel of the bearer 1 is logical channel 2 (for example, the logical channel identifier carried by the MAC layer is used to learn the logical channel corresponding to the data packet 2), the data packet is sent by the terminal device to the network device as the second user. For another example, the corresponding relationship may indicate that key 1 corresponds to the first user identity, and key 2 corresponds to the second user identity. After the network device receives the data packet, the network device tries to use the key 1 and key 2 to decrypt the data packet. The device can correctly decode the data packet using key 1, then the data packet is sent to the network device as the first user by the terminal device; if the network device can correctly decode the data packet using key 2, the data packet is a terminal device It is sent to the network device as the second user. For another example, the correspondence relationship may indicate that C-RNTI1 corresponds to the first user identity, and C-RNTI2 corresponds to the second user identity. If the network device uses C-RNTI 1 to send the PDCCH so that the terminal device can send uplink information, the scheduling data indicated in the PDCCH It is the identity of the first user, for example, the data carried in the PUSCH indicated in the PDCCH is the identity of the first user. If the network device uses C-RNTI 2 to send the PDCCH so that the terminal device sends uplink information, the scheduling data indicated in the PDCCH is the second user identity, for example, the data carried in the PYSCH indicated in the PDCCH is the second user identity of. For another example, the correspondence relationship may indicate that BWP1 corresponds to the first user identity, and BWP2 corresponds to the second user identity. If the network device receives a data packet from BWP1, the network device may determine that the data packet is a terminal device and sent to the network as the first user. For the device, if the network device receives a data packet from BWP2, the network device can determine that the data packet is sent by the terminal device to the network device as the second user. For another example, the correspondence relationship may indicate that subcarrier interval 1 corresponds to the first user identity, and subcarrier interval 2 corresponds to the second user identity. If the network device receives a data packet from the physical channel corresponding to subcarrier interval 1, the network device can determine the The data packet is sent by the terminal device to the network device as the first user. If the network device receives the data packet from the physical channel corresponding to the subcarrier interval 2, the network device can determine that the data packet is the terminal device as the second user. Sent to the network device.

As an optional embodiment, after the terminal device receives the first RRC message, the terminal device needs to feed back an eighth RRC message to the network device, and the eighth RRC message carries the RRC response information and/or the NAS message. The network device also needs to distinguish the RRC response information and/or NAS message of the first user identity and the second user identity. The specific method can be the same as the above method one (that is, the eighth RRC message sent by the terminal device as the first user to the network device carries the RRC message of the second user identity), and the second method (that is, the terminal device sends the RRC message to the network device as the first user). The eighth RRC message sent by the device carries indication information, indicating which user identity the corresponding RRC response information and/or NAS message belongs to), mode three (the RRC response information and/or NAS messages of different user identities are in the eighth RRC Different positions of the message).

It should be noted that after the terminal device establishes an RRC connection according to the configuration information as the second user. The RRC information and NAS message interaction between the terminal equipment and the network equipment (including the network equipment sending to the terminal equipment and the terminal equipment sending to the network equipment) can also be determined according to the above method 1, method 2, and method 3. Which user identity the RRC information and NAS information belong to.

As an optional embodiment, in the method 500, when the network device is paging the terminal device of the second user identity, the network device may send a third RRC message to the terminal device of the first user identity, and the terminal device receives it as the first user identity. The third RRC message sent by the network device includes the first paging information used to page the terminal device of the second user identity. For example, the first paging information may carry the identity of the second user identity. When the terminal device has not determined whether the second user identity can use the RRC connection of the first user identity, or the terminal device has not completed the random access process as the second user identity, the network device may page the second user identity The paging information of the terminal device is carried in the third RRC message of the first user identity, so as to prevent the network device from being unable to page the terminal device of the second user identity.

It should be noted that the third RRC message may be the aforementioned first RRC message, that is, the third RRC message and the first RRC message are the same RRC message; or the third RRC message is different from the aforementioned first RRC message, For example, the third RRC message may be sent by the network device to the terminal device before sending the first RRC message to the terminal device.

As an optional embodiment, when the terminal device has not established the RRC connection of the second user identity or has not completed the random access process of the second user identity, the terminal device cannot report the record type of the second user identity to the network device. Minimize drive test (minimization of drive test, MDT) (ie logged MDT) information or wireless link failure information or access failure information. Therefore, the terminal device can send the fourth RRC message to the network device as the first user. 4. The RRC message includes the logged MDT information or radio link failure information or access failure information of the second user identity of the terminal device (different information can be carried in different cell positions), so that logging of the second user identity can be avoided MDT information or wireless link failure information or access failure information is out of date and invalid or deleted. Optionally, before the terminal device sends the fourth RRC message, the terminal device first sends a sixth RRC message to the network device as the first user, which carries sixth indication information, and the sixth indication information is used to indicate that the terminal device has a second RRC message. The logged MDT or wireless link failure information or access failure information of the user identity (different information can correspond to different indication information). Further, after the network device receives the sixth RRC message, the network device may send a logged MDT request message or a radio link failure request message or an access failure request message, a logged MDT request message or a radio link to the first user identity of the terminal device The path failure request message or the access failure request message is used to instruct the terminal device to report the logged MDT or wireless link failure information or access failure information of the second user identity (different information can correspond to different indication information), and the terminal device can report according to The sixth indication information sends a fourth RRC message to the network device as the first user identity, and the fourth RRC message includes logged MDT information or radio link failure information or access failure information of the second user identity of the terminal device.

As an optional embodiment, the network device may configure logged MDT measurement for both the first user identity and the second user identity. It is possible that one user identity is in the RRC_CONNECTE state, and the other user identity is in the IDLE or RRC_INACTIVE state, and logged MDT only records For the signal quality recorded under idle and RRC_INACTIVE, in order to obtain more MDT measurement results, the measurement result of the cell obtained by one user identity can also be used as the measurement result of another user identity. Further, the terminal device may also only record a piece of logged MDT measurement results, and when a certain user identity needs to report the logged MDT measurement, the corresponding recorded measurement result is reported to the network device.

Optionally, if the first user identity and the second user identity supported by the terminal device belong to the same network device, the service network device of the terminal device needs to change due to changes in the location of the terminal device or network congestion, that is, the terminal device When the serving network device needs to switch from the source network device to the target network device, the source network device needs to send the first information, the second information, and the fourth instruction information to the target network device. The fourth instruction information is used to indicate that the first information is the first information. For a user identity, the second information is the second user identity, and the target network device may determine, according to the fourth indication information, that the first information is the first user identity and the second information is the second user identity. Optionally, the source network device may carry the first information, the second information, and the fourth indication information in the same message and send it to the target network device. For example, the first information may be the context of the first user identity, and the second information may be the context of the second user identity; for another example, the first information may be the first user identity protocol data unit (PDU) session resource establishment Request, the second information is a request for establishing a PDU session with the second user identity; for another example, the first information is a PDU session with the first user identity, and the second information is a PDU session with the second user identity; for another example, the first information is The data radio bearer (DRB) of the first user identity, and the second information is the DRB of the second user identity.

Optionally, in a handover scenario, the source network device sends a message 1 to the target network device, and the message 1 includes third information and fourth information, and the information elements of different user identities are located in different positions of the message 1, for example, The cell where the third information of the first user identity is located is at position 1 of message 1, and the cell where the fourth information of the second user identity is located is at position 2 of message 1. The target network device may determine that the third message is the identity of the first user and the fourth information is the identity of the second user according to the positions of the third information and the fourth information in the message 1. For example, the third information may be the context of the identity of the first user, and the fourth information may be the context of the identity of the second user; for another example, the third information is a session resource establishment request of the identity of the first user, and the fourth information is the second user. Identity PDU session establishment request; for another example, the third information is the PDU session of the first user identity, and the fourth information is the PDU session of the second user identity; for another example, the third information is the DRB of the first user identity, and the fourth information is the DRB of the first user identity. The information is the DRB of the second user's identity.

Optionally, in a handover scenario, when the target network device sends a response message 1 to the source network device, the response message may include first response information, second response information, and fifth indication information, where the fifth indication information is used to indicate The first response information is the response information of the first user identity, and the second response information is the response information of the second user identity. For example, the first response information may be a PDU session resource admission response of the first user identity, and the second response information may be a PDU session resource admission response of the second user identity; for another example, the first response information may be the first user identity The PDU session resource rejection response of the PDU, and the second response information may be the PDU session resource rejection response of the second user identity.

Optionally, in a handover scenario, when the target network device sends a response message 1 to the source network device, the response message 1 may include the first response information and the second response information, and the information element containing the information of different user identities is in the response message Different positions of 1, for example, the cell where the first response information of the first user identity is located is at position 1 of the response message 1, and the cell where the second response information of the second user identity is located at position 2 of the response message 1. The target network device may determine that the first response information is the identity of the first user, and the second response information is the identity of the second user according to the positions of the first response information and the second response information in the response message 1. For example, the first response information may be a PDU session resource admission response of the first user identity, and the second response information may be a PDU session resource admission response of the second user identity; for another example, the first response information may be the first user identity The PDU session resource rejection response of the PDU, and the second response information may be the PDU session resource rejection response of the second user identity.

Optionally, the PDU session resource admission response of the first user identity may carry the data transfer address of the first user identity, and the PDU session resource admission response of the second user identity may carry the data transfer address of the second user identity. The first user identity and the second user identity correspond to different data transfer addresses. The data transfer address includes the transport layer address and the general packet radio service tunneling protocol (GPRS tunnelling protocol, GTP) tunnel port identifier.

Therefore, in the method for establishing an RRC connection in the embodiment of the present application, the terminal device can establish the RRC connection of the second user identity according to the configuration information included in the first RRC message of the first user identity as the second user identity, avoiding the need for the terminal device to Re-initiating random access as the second user and re-establishing an RRC connection independently can also avoid the failure of the terminal device to initiate random access as the second user, which is beneficial to improve the success rate of random access, even if the terminal device does not use The random access initiated by the second user identity directly inherits the random access of the first user identity, which can also avoid the resource overhead caused by the random access, thereby helping to improve the transmission performance.

The method for establishing an RRC connection provided by an embodiment of the present application will be described below with reference to FIGS. 6-9. The following method is described with the network device as the base station, the first user identity of the terminal device is SIMA/USIMA, and the second user identity of the terminal device is SIMB/USIMB.

It should be understood that two SIMs may belong to one UE or two UEs, which is not limited in the embodiment of the present application.

FIG. 6 shows a method 600 for establishing an RRC connection provided by an embodiment of the present application. The method 600 corresponds to the aforementioned situation a), and the method 600 includes:

S610: The base station determines that the terminal device supports SIMA and SIMB, or SIMA and SIMB belong to the same terminal device.

Specifically, in S610 that the base station determines that the terminal device supports SIMA and SIMB, refer to the description of the manner in which the network device determines that the terminal device supports the first user identity and the second user identity in the aforementioned method 500, which will not be described in detail here to avoid repetition.

S620: The base station sends the first RRC message of the SIMA to the terminal device, and the terminal device receives the first RRC message sent by the base station. The first RRC message includes configuration information, and the configuration information is used to instruct the SIMB to use the RRC connection of the SIMA.

It should be noted that the RRC connection of the SIMA of the terminal device is established by default before S620, and the base station can send any RRC message of the SIMA to the terminal device on the RRC connection of the SIMA of the terminal device, such as the first RRC message.

Optionally, the first RRC message in S620 may be an RRC connection release message of SIMA.

S630: The terminal device determines that the SIMB can use the RRC connection of the SIMA according to the configuration information. It can also be understood that the terminal device determines that the SIMB can inherit the RRC connection of the SIMA according to the configuration information.

S640: The configuration information may include SIMB protocol stack parameters and/or key information, and the terminal device modifies the SIMA RRC connection according to the SIMB protocol stack parameters and/or key information to obtain its own RRC connection.

For example, the SIMB protocol stack parameters include service data adaptation protocol (SDAP) layer parameters, packet data convergence protocol control (PDCP) layer parameters, RLC layer parameters, MAC layer parameters, and PHY layer parameters At least one of the parameters.

In the method 600, the SIMB can use the RRC connection of the SIMA, that is, the RRC connection of the SIMA can only be used by one SIM of the terminal device at the same time. Of course, after the SIMB inherits the SIMA, the RRC connection can be referred to as the RRC connection of the SIMB, and the SIMA can again inherit the RRC connection of the SIMB.

FIG. 7 shows a method 700 for establishing an RRC connection provided by an embodiment of the present application. The method 700 corresponds to the aforementioned situation b). The method 700 includes:

S710: The base station determines that the terminal device supports SIMA and SIMB, or SIMA and SIMB belong to the same terminal device.

Specifically, in S710 that the base station determines that the terminal device supports SIMA and SIMB, refer to the description of the manner in which the network device determines that the terminal device supports the first user identity and the second user identity in the foregoing method 500, which will not be described in detail here to avoid repetition.

S720: The base station sends a first RRC message to the SIMA of the terminal device, and the SIMA of the terminal device receives the first RRC message sent by the base station. The first RRC message includes configuration information, and the configuration information includes RACH resources.

It should be noted that before S720, the RRC connection of the SIMA of the terminal device is established by default, and the base station can send any SIMA RRC message, such as the first RRC message, to the terminal device on the RRC connection of the SIMA of the terminal device.

Optionally, the first RRC message in S720 may be an RRC connection release message of SIMA, or an RRC reconfiguration message of SIMA.

S730: The SIMB of the terminal device sends a random access preamble to the base station according to the RACH resource included in the configuration information. For example, the RACH resource may include a random access preamble index (the random access preamble index is used to indicate the random access preamble) and a mask index corresponding to the random access resource, and the mask index is used to indicate when the random access preamble is sent. Frequency resources, the SIMB of the terminal device sends the random access preamble indicated by the random access preamble index to the base station on the time-frequency resource indicated by the mask index.

S740: After receiving the random access preamble sent by the SIMB of the terminal equipment, the base station sends an RAR to the SIMB of the terminal equipment, where the RAR carries at least one of T-CRNTI, uplink authorization information, and TA. Among them, the uplink grant information is used to indicate information such as frequency domain resources, time domain resources, and MCS used to send an RRC connection request message or send an RRC reestablishment request message or send an RRC recovery request message.

S750: The SIMB of the terminal device sends an RRC connection establishment request message or an RRC reestablishment request message or an RRC recovery resource to the base station on the resource indicated by the uplink authorization information. Request message.

S760: After receiving the RRC connection establishment request or the RRC reestablishment request message or the RRC recovery request message, the base station sends an RRC connection setup (RRC connection setup) message or sends an RRC reestablishment message or sends an RRC recovery message to the SIMB of the terminal device. These RRC messages The main purpose is to send the wireless configuration information of the SIMB to the terminal device. For example, the RRC connection establishment message includes wireless configuration information configured by the base station for the SIMB of the terminal device, and the wireless configuration information includes protocol stack parameters of SRB1. The RRC reconstruction message and the RRC recovery message are used to indicate the configuration information before recovery (such as the protocol stack parameters of SRB1).

S770: After configuring the protocol stack parameters of SRB1 according to the wireless configuration information, the terminal device sends an RRC connection setup complete message or sends an RRC reestablishment complete message or sends an RRC recovery complete message to the base station to indicate that the RRC establishment has been completed. connection.

In the method 700, the base station may send the RACH resource of the SIMB of the terminal device through the first RRC message of the SIMA of the terminal device, so as to prevent the terminal device from needing to perform random access in a competitive manner, and reduce the delay of the random access of the SIMB. It can also improve the success rate of SIMB random access, which is beneficial to improving transmission performance.

FIG. 8 shows a method 800 for establishing an RRC connection provided by an embodiment of the present application. The method 800 corresponds to the aforementioned situation c), and the method 800 includes:

S810: The base station determines that the terminal device supports SIMA and SIMB, or SIMA and SIMB belong to the same terminal device.

Specifically, in S810 that the base station determines that the terminal device supports SIMA and SIMB, refer to the description of the manner in which the network device determines that the terminal device supports the first user identity and the second user identity in the aforementioned method 500, which will not be described in detail here to avoid repetition.

S820: The base station sends a first RRC message to the SIMA of the terminal device, and the SIMA of the terminal device receives the first RRC message sent by the base station. The first RRC message includes configuration information. The configuration information includes establishment of the SIMB uplink authorization information of the terminal device and establishment of the terminal. The C-RNTI of the RRC connection of the SIMB of the device, of course, the configuration information may also include the TA.

Among them, the uplink grant information is used to indicate the frequency domain resources, time domain resources, and MCS information for sending the RRC connection request message or sending the RRC reestablishment request message or sending the RRC recovery request message.

It should be noted that before S820, the RRC connection of the SIMA of the terminal device is established by default, and the base station can send any SIMA RRC message, such as the first RRC message, to the terminal device on the RRC connection of the SIMA of the terminal device.

Optionally, the first RRC message in S820 may be an RRC connection release message of SIMA, or an RRC reconfiguration message of SIMA.

S830: The SIMB of the terminal device sends an RRC connection establishment request message or an RRC reestablishment request message or an RRC restoration request message to the base station on the resource indicated by the uplink authorization information for sending an RRC connection request message or sending an RRC reestablishment request message or sending an RRC restoration request message. Request message.

Optionally, if the configuration information includes TA, the SIMB of the terminal device sends an RRC connection request message or sends an RRC reestablishment request message or sends an RRC recovery request message to the base station according to the resource indicated by the uplink authorization information to send an RRC connection establishment request message to the base station. Either send an RRC reconstruction request message or send an RRC recovery request message.

S840: After receiving the RRC connection establishment request, the base station sends an RRC connection setup (RRC connection setup) message or an RRC reestablishment message or an RRC recovery message to the SIMB of the terminal device. The main purpose of these RRC messages is to send the wireless configuration information of the SIMB to the terminal device. For example, the RRC connection establishment message includes wireless configuration information configured by the base station for the SIMB of the terminal device, and the wireless configuration information includes protocol stack parameters of SRB1. The RRC reconstruction message and the RRC recovery message are used to indicate the wireless configuration information before the recovery (such as the protocol stack parameters of SRB1).

S850: After configuring the protocol stack parameters of SRB1 according to the wireless configuration information, the terminal device sends an RRC connection setup complete message or sends an RRC reestablishment complete message or sends an RRC recovery complete message to the base station to indicate that the RRC establishment has been completed. connection.

In method 800, the base station can send the uplink authorization information and C-RNTI of the SIMB of the terminal device through the first RRC message of the SIMA of the terminal device. This avoids the need for the SIMB of the terminal device to send a random access preamble to the base station, and also avoids The terminal device needs to obtain the SIMB uplink authorization information and the C-RNTI process from the RAR sent by the base station, which can reduce the delay of the SIMB random access of the terminal device, and can also improve the success rate of the SIMB random access, which is beneficial to improve the transmission performance.

Fig. 9 shows a method 900 for establishing an RRC connection provided by an embodiment of the present application. The method 900 corresponds to the aforementioned cases d) and e). The method 900 includes:

S910: The base station determines that the terminal device supports USIMA and USIMB, or USIMA and USIMB belong to the same terminal device.

Specifically, in S910 that the base station determines that the terminal device supports USIMA and USIMB, refer to the description of the manner in which the network device determines that the terminal device supports the first user identity and the second user identity in the aforementioned method 500, which will not be described in detail here to avoid repetition.

S920: The base station sends a first RRC message to the USIMA of the terminal device, and the USIMA of the terminal device receives the first RRC message sent by the base station. The first RRC message includes configuration information, and the configuration information may include wireless configuration information of the USIMB. The wireless configuration information includes protocol stack parameters and/or keys. Based on the current wireless configuration information of the USIMA, the terminal device can modify the wireless configuration information of the USIMB to obtain the wireless configuration corresponding to the RRC connection corresponding to the USIMB ( For example, the protocol stack parameters of SRB1).

It should be noted that the RRC connection of the USIMA of the terminal device is established by default before S920, and the base station can send any RRC message of the USIMA to the terminal device on the RRC connection of the USIMA of the terminal device, such as the first RRC message.

Optionally, in S920, the first RRC message may include a USIMB NAS message.

Optionally, the first RRC message in S920 may be an RRC connection release message of USIMA, or an RRC reconfiguration message of USIMA.

S930: The terminal device determines whether the RRC connection of the USIMA can be used by the USIMB, or the terminal device determines whether the first RRC message of the USIMA can include the RRC message of the USIMB.

Specifically, in S930, reference may be made to the determination manner in the aforementioned method 500. In order to avoid repeating the description of the embodiments of the present application, detailed descriptions are not provided here.

Optionally, if the first RRC message can include a USIMB NAS message, the terminal device needs to determine that the NAS message is USIMB. For a specific determination method, refer to the determination method in method 500. In order to avoid repeating the embodiments of the present application, it will not be described here. Detailed Description.

S940: The configuration information may include wireless configuration information of the USIMB, and the wireless configuration information includes protocol stack parameters and/or keys.

If in S930, the terminal device determines that the RRC connection of USIMA can be used by USIMB, or the terminal device determines that the first RRC message of USIMA can include the RRC message of USIMB, the terminal device can use the current wireless configuration information of USIMA according to The wireless configuration information of the USIMB is modified to obtain the protocol stack parameters corresponding to the RRC connection corresponding to the USIMB (for example, the protocol stack parameters of SRB1).

Optionally, in the method 900, the USIMA and the USIMB may have different RRC layer entities, and the different RRC layers may serve the USIMA and the USIMB at the same time. In other words, if the first RRC message is the common RRC message of USIMA and USIMB, the terminal device retains both the USIMA protocol stack parameters and the USIMB protocol stack parameters, and/or the terminal device can retain both the USIMA key and the USIMB key. Key.

Optionally, if USIMA and USIMB can have different RRC layer entities, as shown in Figure 10, for the control plane protocol, USIMA and USIMB use different RRC layer entities (PDCP layer entity/RLC layer entity/MAC layer entity may be the same , Can also be different), USIMA and USIMB use different NAS. As shown in Figure 11, for the user plane protocol, USIMA and USIMB use different SDAP layer entities/PDCP layer entities/RLC layer entities (the same or different MAC layer entities). Or, as shown in FIG. 12, USIMA and USIMB use the same SDAP/PDCP and different RLC layer entities (the same or different MAC layer entities).

Optionally, in method 900, USIMA and USIMB may have the same RRC layer entity, and the same RRC layer may serve different USIMA and USIMB at different times, and only one USIM at the same time. That is, USIMA and USIMB use the RRC layer in a time division manner. If at a certain moment, the RRC connection of USIMA can only be used by USIMB, so that the terminal device can modify the RRC connection protocol stack parameters that establish USIMA to the protocol stack parameters of USIMB. At the next moment, USIMA can continue to use the RRC connection, and the terminal device Modify the USIMB protocol stack parameters to the USIMA protocol stack parameters; or, in method 900, the RRC connection of the USIMA can only be used by the USIMB at a certain time, so that the terminal device uses the USIMB key. At the next moment, the USIMA can Continue to use the RRC connection, and the terminal device uses the USIMA key.

Optionally, if USIMA and USIMB can have the same RRC layer entity, for the control plane protocol, as shown in Figure 13, USIMA and USIMB use the same RRC layer entity/PDCP layer entity/RLC layer entity (even the MAC layer entity is also Same), USIMA and USIMB use different NAS. For user plane protocols, as shown in Figure 11, USIMA and USIMB use different SDAP layer entities/PDCP layer entities/RLC layer entities (the MAC layer entities may be the same or different); or for user plane protocols, USIMA and USIMB use the same The SDAP layer entity/PDCP layer entity adopts different RLC layer entities (the same or different MAC layer entities)

In method 900, USIMA and USIMB can use terminal equipment to establish an RRC connection with USIMA, for example, by carrying the information of two USIM cards in the same RRC message, or USIMA and USIMB can use terminal equipment in a time-division multiplexing manner RRC connection established with USIMA. In this way, the terminal device does not need to specifically establish RRC connections for the USIMB, which can reduce the number of RRC connections. At the same time, the terminal device does not need to initiate a random access procedure for the USIMB, which can avoid signaling overhead and help improve transmission performance.

The following describes the method for transmitting MDT information provided by the embodiment of the present application in conjunction with the method 1400. As shown in FIG. 14, the method 1400 includes:

S1410: The terminal device uses the SIMA RRC connection to send sixth indication information with SIMB MDT information to the base station, that is, the sixth indication information is used to indicate that the terminal device has SIMB MDT information, and the base station can learn after receiving the sixth indication information The terminal device has the MDT information of the SIMB.

Among them, the MDT information is the measurement result obtained by the terminal device using the SIMB identity to measure, and the measurement result reflects the current network coverage status. For example, the terminal device uses the SIMB identity to collect the signal quality of the current cell and neighboring cells.

For example, the sixth indication information may be carried in an RRC setup complete (RRCsetupcomplete) message, an RRC reselection complete (RRCresumecomplete) message, an RRC reconfiguration complete (RRCreconfigurationcomplete) message, or an RRC retablishmentcomplete (RRCretablishmentcomplete) message.

Optionally, the sixth indication information may also indicate indication information with SIMB radio link failure or access failure and other record information.

S1420: The base station uses the RRC connection of the SIMA to send an MDT request message to the terminal device, where the MDT request message is used to request the terminal device to send the MDT information of the SIMB.

For example, when the base station needs the terminal device to report the MDT information of the SIMB, it can send an MDT request message to the terminal device.

Optionally, the base station may also send a request to report record information such as a wireless link failure or access failure of the SIMB to the terminal device.

S1430: The terminal device sends a fourth RRC message to the base station, where the fourth RRC message includes the MDT information of the SIMB.

Optionally, the fourth RRC message may also include record information such as a radio link failure or access failure of the SIMB. As an alternative to S1420 and S1430, the base station sends an MDT request message to the terminal device. The MDT request message may carry seventh indication information. The seventh indication information is used to instruct the terminal device to report the MDT information of which SIM card. The fourth RRC message sent by the base station carries the MDT information of the SIM indicated by the seventh indication information. For example, the seventh indication information indicates that the terminal device reports the MDT information of the SIMA, and the terminal device reports the MDT information of the SIMA in the fourth RRC message. For another example, if the seventh indication information indicates that the terminal device reports the MDT information of the SIMB, the terminal device reports the MDT information of the SIMB in the fourth message.

As an alternative to S1420 and S1430, the base station sends an MDT request message to the terminal device. The MDT request message is used to request the terminal device to report the MDT information. The terminal device can report the SIMA MDT information to the base station through the fourth RRC message. And SIMB MDT information 2, and the fourth RRC message can carry eighth indication information and ninth indication information. The eighth indication information is used to indicate that MDT information 1 is SIMA, and the ninth indication information is used to indicate that MDT information 2 is SIMB. of.

If the SIMA and SIMB of the terminal device belong to different base stations, the base stations of the two SIMs may configure different measurement configurations for the two SIMs of the same terminal device, such as the measurement interval (gap) configuration, then the terminal device needs to be two SIMs Blind detection is performed separately. Due to the limited measurement capability of the terminal device, the measurement gap configured by the two base stations for the two SIMs will exceed the measurement capability of the terminal device, causing the terminal device to be unable to perform measurement. The following describes the embodiment of the application with reference to FIG. 15 A method 1500 for reporting measurement configuration is provided, and the method 1500 includes:

S1510: The terminal device sends the SIMA measurement configuration to the SIMB base station, and the SIMB base station receives the SIMA measurement configuration.

Specifically, the measurement configuration of SIMA includes the gap type of SIMA (Is it a terminal device level GAP type, or a frequency range 1 (frequency rang 1, FR1) level GAP type, or frequency range 2 (frequency rang 2, FR2) Level GAP), at least one of gap time information, measurement frequency, measurement pilot signal type, subcarrier interval corresponding to the measurement pilot signal, and the number of measurement report events.

S1520: The base station of the SIMB determines the measurement configuration of the SIMB according to the measurement configuration of the SIMA reported by the terminal device.

After the base station of USIM B receives the configuration information of USIMA, the base station determines the upper limit of the measurement configuration for USIM B according to the total capabilities of the terminal equipment and the reported configuration information of USIM A, thereby ensuring that the total measurement configuration of USIM A and USIM B is different. Will exceed the total measurement capability of the terminal device.

S1530: The base station of the SIMB sends the determined measurement configuration of the SIMB to the terminal device, and the terminal device performs measurement according to the measurement configuration of the SIMB.

It should be noted that in this embodiment of the application, the RRC connection established by the terminal device as the first user identity can be used by the first user identity and the second user identity at the same time, and the terminal device and the network device are in the RRC chain of the first user identity. The information transmitted on the road may be the identity of the first user or the identity of the second user. Therefore, the terminal device and the network device should distinguish between the information transmitted as the first user identity and the second user identity. The terminal device and the network The device can display instructions, such as direct instructions to indicate whether the transmitted information is the first user identity or the second user identity; or the terminal device and the network device can use implicit instructions, such as different logical channels corresponding to different user identities , Different BWPs correspond to different user identities, and different subcarrier intervals correspond to different user identities, and so on. Therefore, when any RRC connection established by using the first user identity transmits information of two user identities, it is within the protection scope of the embodiments of the present application to distinguish which user identity the information belongs to by a display instruction or an implicit instruction.

It should also be noted that in this embodiment of the application, the serving base stations of SIMA and SIMB may be the same or different. If the serving base stations of SIMA and SIMB are different, then the base station of SIMA can interact with the base station of SIMB, so as to achieve the establishment of SIMB. The purpose of the RRC connection, for example, the first RRC message sent by the terminal device to the base station of SIMA can carry the base station identity of SIMB, and the base station of SIMA can send information to the base station corresponding to the base station identity of SIMB, for example, send a protocol stack for requesting SIMB. Parameters and SIMB key information. In order to avoid repeating the description of the embodiments of the present application, the situation that the serving base stations of SIMA and SIMB are different will not be described in detail. Those skilled in the art can obtain different methods of serving base stations of SIMA and SIMB in combination with the methods described in the embodiments of the present application.

Further, the serving cells of SIMA and SIMB may also be the same or different, which is not limited in the embodiment of the present application.

It should also be noted that, in order to clearly describe the solution of the embodiments of the present application, in the above embodiments, the terminal device supports both SIMA and SIMB. In practical applications, SIMA and SIMB can belong to different terminal devices, for example, SIMA terminal devices. There can be mutual communication and interaction with SIMB terminal devices, for example, SIMA terminal devices and SIMB terminal devices interact through wired or wireless (such as WIFI).

It should also be noted that the configuration information in the embodiment of the present application includes wireless configuration information, that is, the configuration information includes any configuration for a terminal device to initiate random access or establish an RRC connection, and the wireless configuration information includes protocol stack parameters for establishing SRB1.

The method for establishing an RRC connection provided by an embodiment of the present application is described in detail above with reference to FIGS. 1 to 15. The following describes in detail the apparatus for establishing an RRC connection provided by an embodiment of the present application with reference to FIGS. 16 to 18.

FIG. 16 shows a schematic block diagram of an apparatus 1600 for establishing an RRC connection provided by an embodiment of the present application. The apparatus 1600 may correspond to the terminal device described in the foregoing method, or may correspond to the chip or component of the terminal device, and the apparatus 1600 Each module or unit in the above method can be used to execute each action or process performed by the terminal device in the above method. As shown in FIG. 16, the apparatus 1600 for establishing an RRC connection supports the first user identity and the second user identity. The 1600 may include a transceiving unit 1610 and a establishing unit 1620.

The transceiver unit 1610 is configured to receive a first radio resource control RRC message of the first user identity from a network device as the first user identity, where the first RRC message includes configuration information, and the configuration information is used for the The apparatus 1600 establishes an RRC connection with the identity of the second user;

The establishment unit 1620 is configured to establish an RRC connection according to the configuration information as the second user.

As an optional embodiment, the configuration information includes a random access channel RACH resource for the establishment unit 1620 to establish an RRC connection with the identity of the second user, and a establishment unit 1620 to establish an RRC connection with the identity of the second user. At least one of the uplink authorization information and the temporary radio network identifier C-RNTI of the cell used for the establishment unit 1620 to establish an RRC connection with the identity of the second user.

As an optional embodiment, the configuration information is used to instruct the apparatus 1600 to use the RRC connection established by the apparatus 1600 as the first user as the second user;

The establishing unit 1620 is specifically configured to use the apparatus 1600 to establish an RRC connection with the identity of the first user using the identity of the second user according to the configuration information.

As an optional embodiment, the establishing unit 1620 is specifically configured to use the RRC connection established by the apparatus 1600 as the first user as the second user according to the configuration information, and the apparatus 1600 can use the apparatus 1600 as the first user as the first user. An RRC connection established by a user identity.

As an optional embodiment, the first RRC message includes a second RRC message of the second user identity of the apparatus 1600, the second RRC message includes the configuration information, and the apparatus 1600 further includes:

The determining unit is configured to determine, according to the second RRC message included in the first RRC message, that the apparatus 1600 can use the RRC connection established by the apparatus 1600 in the identity of the first user as the second user.

As an optional embodiment, the first RRC message includes first indication information, and the first indication information is used to indicate that the configuration information included in the first RRC message is used by the apparatus 1600 to communicate with the second user The identity establishes an RRC connection, and the determining unit is further configured to determine, according to the first indication information, that the apparatus 1600 can use the RRC connection established by the apparatus 1600 with the identity of the first user as the second user.

As an optional embodiment, the determining unit is further configured to determine, according to the position of the cell where the configuration information is located in the first RRC message, that the apparatus 1600 can use the apparatus 1600 as the second user. For the RRC connection established by the first user identity, the cells in which the configuration information of the different user identities of the apparatus 1600 are located are in different positions in the first RRC message.

As an optional embodiment, the first RRC message includes a correspondence, and the correspondence is used to indicate that different bearers correspond to different user identities, or the correspondence is used to indicate that different logical channels of the same bearer correspond to different logical channels. Different user identities, or the correspondence relationship is used to indicate that different keys correspond to different user identities, or the correspondence relationship is used to indicate that different C-RNTIs correspond to different user identities, or the correspondence relationship It is used to indicate that different bandwidth parts BWP correspond to different user identities, or the correspondence relationship is used to indicate that different subcarrier intervals correspond to different user identities, and the correspondence relationship is used by the apparatus 1600 to determine the first user identity or The identity of the second user.

As an optional embodiment, the configuration information further includes at least one of a protocol stack parameter of the second user identity and key information of the second user identity.

As an optional embodiment, the transceiving unit 1610 is further configured to receive a third RRC message from the network device as the first user, where the third RRC message includes first paging information, and the first paging information The information carries the identifier of the second user identity of the device 1600.

As an optional embodiment, the transceiving unit 1610 is further configured to send a fourth user as the first user to the network device before establishing an RRC connection according to the configuration information as the second user. An RRC message, where the fourth RRC message includes MDT minimized drive test information of the second user identity of the apparatus 1600.

As an optional embodiment, the first RRC message is an RRC release message or an RRC reconfiguration message, and the RRC release message is used to indicate to release the RRC connection of the first user identity of the apparatus 1600 or to indicate the apparatus 1600 The RRC connection of the first user identity enters an inactive state.

It should be understood that, for the specific process of each unit in the apparatus 1600 executing the above corresponding steps, please refer to the description of the method embodiments in FIG. 5 to FIG.

FIG. 17 shows a schematic block diagram of an apparatus 1700 for establishing an RRC connection according to an embodiment of the present application. The apparatus 1700 may correspond to the network equipment or base station described in the above method, and may also correspond to the chip or component of the network equipment or base station, and Each module or unit in the apparatus 1700 may be used to execute each action or processing performed by the network equipment or base station in the above method. As shown in FIG. 17, the apparatus 1700 for establishing an RRC connection may include an acquiring unit 1710 and a transceiver. Unit 1720.

The obtaining unit 1710 is configured to obtain configuration information, where the configuration information is used by the terminal device to establish a radio resource control RRC connection as the second user;

The transceiver unit 1720 is configured to send a first RRC message to a terminal device with a first user identity, where the first RRC message includes the configuration information.

As an optional embodiment, the apparatus 1700 further includes a determining unit, configured to determine that the terminal device supports the first user identity and the first user identity before the first RRC message is sent to the first user identity terminal device. The second user identity.

As an optional embodiment, the configuration information includes a random access channel RACH resource used for the terminal device to establish an RRC connection with the second user identity, and a random access channel RACH resource used for the terminal device to establish an RRC connection with the second user identity. At least one of the uplink authorization information of the RRC connection and the temporary radio network identifier C-RNTI of the cell used for the terminal device to establish the RRC connection with the identity of the second user.

As an optional embodiment, the configuration information is used to instruct the terminal device as the second user to use the RRC connection established by the terminal device as the first user.

As an optional embodiment, the first RRC message includes a second RRC message of the second user identity of the terminal device, and the second RRC message includes the configuration information.

As an optional embodiment, the first RRC message includes first indication information, and the first indication information is used to indicate that the configuration information included in the first RRC message is used by the terminal device to communicate with the second user. The identity establishes the RRC connection.

As an optional embodiment, the first RRC message includes a correspondence, and the correspondence is used to indicate that different bearers correspond to different user identities, or the correspondence is used to indicate that different logical channels of the same bearer correspond to different logical channels. Different user identities, or the correspondence relationship is used to indicate that different keys correspond to different user identities, or the first correspondence relationship is used to indicate that different C-RNTIs correspond to different user identities, or the correspondence The relationship is used to indicate that different bandwidth parts BWP correspond to different user identities, or the corresponding relationship is used to indicate that different subcarrier intervals correspond to different user identities, and the corresponding relationship is used for the terminal device to determine the first User identity or said second user identity.

As an optional embodiment, if the configuration information includes the protocol stack parameters of the second user identity, the protocol stack parameters of the second user identity are radio link control RLC layer parameters and media access control MAC layer parameters Or at least one of the physical PHY layer parameters, the acquiring unit 1710 is further configured to send a request message to the distribution unit DU, where the request message is used to request the protocol stack parameter of the second user identity.

As an optional embodiment, the transceiving unit 1720 is further configured to send a third RRC message to the terminal device of the first user identity, where the third RRC message includes first paging information, and the first paging information The information carries the identifier of the second user identity of the terminal device.

As an optional embodiment, the transceiving unit 1720 is further configured to receive a fourth RRC message sent by the terminal device of the first user identity, where the fourth RRC message includes the second user identity of the terminal device Minimize drive test MDT information;

As an optional embodiment, the first RRC message is an RRC release message or an RRC reconfiguration message, and the RRC release message is used to instruct to release the RRC connection of the first user identity of the terminal device or to indicate The first user identity of the terminal device enters an RRC inactive state.

It should be understood that, for the specific process of each unit in the device 1700 performing the above corresponding steps, please refer to the description of the method embodiments in FIG. 5 to FIG.

The apparatus 1600 of each of the foregoing solutions has the function of implementing the corresponding steps performed by the terminal device in the foregoing method, and the apparatus 1700 of each of the foregoing solutions has the function of implementing the corresponding steps performed by the network device in the foregoing method; the functions can be implemented by hardware or software, or The corresponding software is implemented by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the sending unit can be replaced by a communication interface, the receiving unit can be replaced by a communication interface, and other units, such as the determining unit, can be replaced by a processor to execute each method separately Transceiving operations and related processing operations in the embodiment. In the embodiment of the present application, the communication interface of a device is used for the device to communicate with other devices. Exemplarily, the communication interface may be a transmitter, a receiver, a transceiver, a circuit, a bus, a module, a pin, or another type of communication interface, which is not limited in the embodiment of the present application.

In a specific implementation process, the processor can be used to perform, for example, but not limited to, baseband related processing, and the communication interface can be used to perform, for example, but not limited to, information exchange. The above-mentioned devices may be respectively arranged on separate chips, or at least part or all of them may be arranged on the same chip. For example, the processor can be further divided into an analog baseband processor and a digital baseband processor, where the analog baseband processor and the communication interface can be integrated on the same chip, and the digital baseband processor can be set on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be combined with a variety of application processors (such as but not limited to graphics processors, multimedia processors, etc.) Integrated on the same chip. Such a chip may be called a system on chip (SOC). Whether each device is arranged independently on different chips or integrated on one or more chips often depends on the specific needs of product design. The embodiment of the present application does not limit the specific implementation form of the foregoing device.

It can be understood that the processor involved in the foregoing embodiments can execute program instructions through a hardware platform with a processor and a communication interface to implement the functions involved in any design of the foregoing embodiments of the present application, based on this As shown in FIG. 18, an embodiment of the present application provides a schematic block diagram of an apparatus 1800 for establishing an RRC connection. The apparatus 1800 includes a processor 1810, a communication interface 1820, and a memory 1830. The processor 1810, the communication interface 1820, and the memory 1830 are coupled to communicate with each other. The memory 1830 is used to store instructions, and the processor 1810 is used to execute the instructions stored in the memory 1830 to control the communication interface 1820 to send signals and/or receive signal. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.

Wherein, in a possible implementation manner, if the apparatus 1800 is a terminal device, the communication interface 1820 is configured to receive the first radio resource control RRC message of the first user identity from the network device as the first user identity, The first RRC message includes configuration information, and the configuration information is used by the apparatus 1800 to establish an RRC connection as the second user; the processor 1810 is configured to establish an RRC connection as the second user according to the configuration information. RRC connection.

In a possible implementation manner, if the apparatus 1800 is a network device, the communication interface 1820 is used to obtain configuration information, and the configuration information is used by the terminal device to establish a radio resource control RRC connection as the second user; the communication interface 1820 also Used to send a first RRC message to a terminal device with a first user identity, where the first RRC message includes the configuration information.

It should be understood that the apparatus in FIG. 16 or the apparatus in FIG. 17 in the embodiment of the present application may be implemented by the apparatus 1800 in FIG. 18, and may be used to execute the respective steps and/or corresponding terminal equipment and network equipment in the foregoing method embodiments. Or process.

It is understandable that the methods, processes, operations, or steps involved in the various designs described in the embodiments of the present application can be implemented in a one-to-one correspondence manner through computer software, electronic hardware, or a combination of computer software and electronic hardware. Corresponding realization. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. For example, considering the good versatility, low cost, software and hardware decoupling, etc., they can be implemented by executing program instructions, for example , Considering system performance and reliability, etc., it can be realized by using a dedicated circuit. Ordinary technicians can use different methods to implement the described functions for each specific application, which is not limited here.

According to the method provided in the embodiments of the present application, the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code runs on a computer, the computer executes the method in the above embodiment . The various embodiments in this application can also be combined with each other.

According to the method provided in the embodiments of the present application, the present application also provides a computer-readable medium, the computer-readable interpretation stores a program code, and when the program code runs on a computer, the computer executes the method in the above-mentioned embodiment .

The embodiment of the present application also provides a system for establishing an RRC connection, including the apparatus 1600 in FIG. 16 and the apparatus 1700 in FIG. 17. Or the system includes the devices in the two possible implementation manners shown in FIG. 18.

In the embodiments of the present application, it should be noted that the foregoing method embodiments in the embodiments of the present application may be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The foregoing processor may be a general-purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or any conventional processor or the like.

It can be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. There are many different types of RAM, such as static random access memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate Synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and direct memory bus random memory Take memory (direct rambus RAM, DR RAM).

It should be understood that in the various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application. The implementation process constitutes any limitation.

The terms "first" and "second" appearing in this application are only used to distinguish different objects, and "first" and "second" themselves do not limit the actual order or function of the modified objects. Any embodiment or design solution described as "exemplary", "example", "for example", "optionally" or "in certain implementations" in this application should not be construed as better than other implementations. Examples or design schemes are more preferred or more advantageous. Rather, these words are used to present related concepts in a concrete way.

Various messages/information/equipment/network elements/systems/devices/operations that may appear in this application have been assigned names. It is understandable that these specific names do not constitute a reference to related objects. Limited, the assigned name can be changed according to factors such as the scene, context, or usage habits. The understanding of the technical meaning of the technical terms in this application should be determined mainly from the functions and technical effects embodied/implemented in the technical solution .

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product may include one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal device, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic disk), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here. In the embodiments of the present application, provided that there is no logical contradiction, the embodiments can be mutually cited. For example, the methods and/or terms between the method embodiments can be mutually cited, such as the functions and/or functions between the device embodiments. Or terms may refer to each other, for example, functions and/or terms between the device embodiment and the method embodiment may refer to each other.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

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

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method for establishing a radio resource control RRC connection, characterized in that the method is applicable to a terminal device, and the terminal device supports a first user identity and a second user identity, and includes:

The terminal device receives a first radio resource control RRC message of the first user identity from a network device as the first user identity, where the first RRC message includes configuration information, and the configuration information is used for the terminal device Establishing an RRC connection as the second user;

The terminal device uses the second user identity to establish an RRC connection according to the configuration information.
The method according to claim 1, wherein the configuration information includes a random access channel RACH resource used by the terminal device to establish an RRC connection with the identity of the second user, and a random access channel RACH resource used by the terminal device to establish an RRC connection. At least one of the uplink authorization information for establishing the RRC connection with the second user identity and the temporary radio network identifier C-RNTI of the cell used for the terminal device to establish the RRC connection with the second user identity.
The method according to claim 1, wherein the configuration information is used to instruct the terminal device to use the second user identity to use the RRC connection established by the terminal device with the first user identity;

Wherein, that the terminal device uses the second user identity to establish an RRC connection according to the configuration information includes:

The terminal device uses the RRC connection established by the terminal device in the identity of the first user with the identity of the second user according to the configuration information.
The method according to claim 1, wherein the establishment of the RRC connection by the terminal device as the second user identity according to the configuration information comprises:

The terminal device uses the RRC connection established by the terminal device with the first user identity as the second user according to the configuration information, and the terminal device can use the terminal device with the first user identity An RRC connection established as the first user.
The method according to claim 4, wherein the first RRC message includes a second RRC message of the second user identity of the terminal device, the second RRC message includes the configuration information, and The method also includes:

The terminal device determines, according to the second RRC message included in the first RRC message, that the terminal device can use the second user identity to use the RRC connection established by the terminal device with the first user identity.
The method according to claim 4, wherein the first RRC message includes first indication information, and the first indication information is used to indicate that the configuration information included in the first RRC message is used for the The terminal device establishes an RRC connection with the identity of the second user, and the method further includes:

The terminal device determines, according to the first indication information, that the terminal device can use the RRC connection established by the terminal device with the first user identity as the second user identity.
The method according to claim 4, wherein the method further comprises:

The terminal device determines, according to the position of the cell where the configuration information is located in the first RRC message, that the terminal device can use the terminal device as the second user to establish the identity of the terminal device as the first user. In the RRC connection, the information elements where the configuration information of the different user identities of the terminal device are located are in different positions of the first RRC message.
The method according to any one of claims 4 to 7, wherein the first RRC message includes a corresponding relationship, and the corresponding relationship is used to indicate that different bearers correspond to different user identities, or the corresponding The relationship is used to indicate that different logical channels of the same bearer correspond to different user identities, or the corresponding relationship is used to indicate that different keys correspond to different user identities, or the corresponding relationship is used to indicate different C-RNTIs. Corresponding to different user identities, or the corresponding relationship is used to indicate that different bandwidth parts BWP correspond to different user identities, or the corresponding relationship is used to indicate that different subcarrier intervals correspond to different user identities, the corresponding relationship Used by the terminal device to determine the first user identity or the second user identity.
The method according to any one of claims 1 to 8, wherein the configuration information further includes at least one of a protocol stack parameter of the second user identity and key information of the second user identity Kind.
The method according to any one of claims 1 to 9, wherein the method further comprises:

The terminal device receives a third RRC message from the network device as the first user, the third RRC message includes first paging information, and the first paging information carries the terminal device’s The identity of the second user.
The method according to any one of claims 1 to 10, characterized in that, before the terminal device establishes an RRC connection according to the configuration information as the second user, the method further comprises:

The terminal device sends a fourth RRC message to the network device as the first user identity, where the fourth RRC message includes the minimized drive test MDT information of the second user identity of the terminal device.
The method according to any one of claims 1 to 11, wherein the first RRC message is an RRC release message or an RRC reconfiguration message, and the RRC release message is used to instruct to release all of the terminal equipment. The RRC connection of the first user identity or the RRC connection used to indicate the first user identity of the terminal device enters an inactive state.
A method for establishing a radio resource control RRC connection, which is characterized in that it includes:

The network device obtains configuration information, where the configuration information is used by the terminal device to establish a radio resource control RRC connection as the second user;

The network device sends a first RRC message to the terminal device of the first user identity, where the first RRC message includes the configuration information.
The method according to claim 13, wherein before the network device sends the first RRC message to the terminal device with the first user identity, the method further comprises:

The network device determines that the terminal device supports the first user identity and the second user identity.
The method according to claim 13 or 14, wherein the configuration information includes a random access channel RACH resource used for the terminal device to establish an RRC connection as the second user, and used for the terminal device At least one of uplink authorization information for establishing an RRC connection with the identity of the second user and a cell radio network temporary identifier C-RNTI used for the terminal device to establish an RRC connection with the identity of the second user.
The method according to claim 13 or 14, wherein the configuration information is used to instruct the terminal device to use the second user identity to use the RRC connection established by the terminal device with the first user identity.
The method according to claim 13 or 14, wherein the first RRC message includes a second RRC message of the second user identity of the terminal device, and the second RRC message includes the configuration information .
The method according to claim 13 or 14, wherein the first RRC message includes first indication information, and the first indication information is used to indicate that the configuration information included in the first RRC message is used for the The terminal device establishes an RRC connection with the identity of the second user.
The method according to claim 17 or 18, wherein the first RRC message includes a corresponding relationship, and the corresponding relationship is used to indicate that different bearers correspond to different user identities, or the corresponding relationship is used to indicate Different logical channels of the same bearer correspond to different user identities, or the correspondence relationship is used to indicate that different keys correspond to different user identities, or the first correspondence relationship is used to indicate that different C-RNTIs correspond to different user identities. User identities, or the correspondence relationship is used to indicate that different bandwidth parts BWP correspond to different user identities, or the correspondence relationship is used to indicate that different subcarrier intervals correspond to different user identities, and the correspondence relationship is used for all The terminal device determines the first user identity or the second user identity.
The method according to any one of claims 13 to 19, wherein the configuration information further includes at least one of a protocol stack parameter of the second user identity and key information of the second user identity Kind.
The method according to claim 20, wherein if the configuration information includes the protocol stack parameters of the second user identity, the protocol stack parameters of the second user identity are radio link control RLC layer parameters, media When at least one of the access control MAC layer parameters or the physical PHY layer parameters, the network device acquiring configuration information includes:

The network device sends a request message to the distribution unit DU, where the request message is used to request the protocol stack parameters of the second user identity.
The method according to any one of claims 13 to 21, wherein the method further comprises:

The network device sends a third RRC message to the terminal device of the first user identity, where the third RRC message includes first paging information, and the first paging information carries the second paging information of the terminal device. The identity of the user.
The method according to any one of claims 13 to 22, wherein the method further comprises:

Receiving, by the network device, a fourth RRC message sent by the terminal device of the first user identity, where the fourth RRC message includes the minimized drive test MDT information of the second user identity of the terminal device;

The network device determines the MDT information of the second user identity according to the fourth RRC message.
The method according to any one of claims 13 to 23, wherein the first RRC message is an RRC release message or an RRC reconfiguration message, and the RRC release message is used to instruct to release all of the terminal device. The RRC connection of the first user identity may be used to indicate that the first user identity of the terminal device enters the RRC inactive state.
A device for establishing a radio resource control RRC connection, characterized by comprising a unit for executing the method in any one of claims 1-12.
A device for establishing a radio resource control RRC connection, which is characterized by comprising a unit for executing the method in any one of claims 13 to 24.
A system for establishing a radio resource control RRC connection, which is characterized by comprising the device according to claim 25 and claim 26.
A device for establishing a radio resource control RRC connection, including a memory, a processor, and a program stored in the memory and running on the processor, wherein the processor implements rights when the program is executed The method of any one of 1 to 12 is required.
A device for establishing a radio resource control RRC connection, including a memory, a processor, and a program stored in the memory and running on the processor, wherein the processor implements rights when the program is executed The method of any one of claims 13-24.
A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed, the method according to any one of claims 1 to 12 is realized.
A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed, the method according to any one of claims 13 to 24 is realized.
A chip comprising a processor, the processor is connected to a memory, the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the chip executes as claimed in claim 1. To the method of any one of 12.
A chip comprising a processor, the processor is connected to a memory, the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the chip executes as claimed in claim 13 To the method of any one of 24.