WO2020147837A1 - 信息传送的方法及通信设备 - Google Patents
信息传送的方法及通信设备 Download PDFInfo
- Publication number
- WO2020147837A1 WO2020147837A1 PCT/CN2020/072751 CN2020072751W WO2020147837A1 WO 2020147837 A1 WO2020147837 A1 WO 2020147837A1 CN 2020072751 W CN2020072751 W CN 2020072751W WO 2020147837 A1 WO2020147837 A1 WO 2020147837A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- card
- communication device
- following
- sending
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
- H04W68/02—Arrangements for increasing efficiency of notification or paging channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
Definitions
- the embodiments of the present disclosure relate to the field of wireless communication technologies, and in particular, to a method and communication device for information transmission.
- multi-card terminals are more and more commonly used, and the multi-card terminal may have two or more subscriber identity cards (Subscriber Identity Module, SIM).
- SIM Subscriber Identity Module
- the user experience of multi-card terminals is not optimized enough, for example, paging conflicts may occur. Therefore, how to solve the problem of the multi-card terminal and improve the user experience of the multi-card terminal is a technical problem to be solved urgently.
- the embodiments of the present disclosure provide an information transmission method and communication equipment, which are used to solve the problem of a multi-card terminal and improve the user experience of the multi-card terminal.
- some embodiments of the present disclosure provide an information transmission method applied to a first communication device, including:
- the first information of the second UE and/or the target UE information is sent to the first UE.
- some embodiments of the present disclosure provide a method of information transmission, which is applied to a second communication device, including:
- the second operation includes at least one of the following:
- some embodiments of the present disclosure provide a method of information transmission, which is applied to a third communication device, including:
- the third operation includes at least one of the following:
- some embodiments of the present disclosure provide a method of information transmission, which is applied to a fourth communication device, including:
- the third information includes at least one of the following: first capability information, the number of card slots supported by the first device, the number of cards supported by the first device, the indication information whether the first device supports multiple cards, and whether the first device Indication information for supporting multiple UEs, information about the number of UEs on the first device, information about the number of cards on the first device, relevant indication information about whether the first device is in the multi-UE state, and relevant indication information about whether the first device is in the multi-card state , Whether to request Doka optimization instructions.
- some embodiments of the present disclosure provide a method of information transmission, which is applied to a fifth communication device, including:
- the third information includes at least one of the following: first capability information, the number of card slots supported by the first device, the number of cards supported by the first device, and the indication information about whether the first device supports multiple cards , Indication information about whether the first device supports multiple UEs, information about the number of UEs on the first device, information about the number of cards on the first device, relevant indication information about whether the first device is in a multi-UE state, and whether the first device is multi-card Relevant indication information of status, indication information of whether to request multi-card optimization;
- the fifth related operation includes at least one of the following:
- some embodiments of the present disclosure provide a communication device, where the communication device is a first communication device and includes:
- the first judgment module is used to judge whether the first condition is satisfied
- the first sending module is configured to send the first information of the second UE and/or the target UE information to the first UE when the first condition is determined to be satisfied.
- some embodiments of the present disclosure provide a communication device, where the communication device is a second communication device and includes:
- the second judgment module is used to judge whether the second condition is satisfied
- the first execution module is configured to execute the second operation when it is determined that the second condition is met
- the second operation includes at least one of the following:
- some embodiments of the present disclosure provide a communication device, where the communication device is a third communication device and includes:
- the first receiving module is configured to receive the first information of the second UE and/or target UE information
- the second execution module is configured to execute a third operation according to the first information of the second UE and/or target UE information;
- the third operation includes at least one of the following:
- some embodiments of the present disclosure provide a communication device, where the communication device is a fourth communication device and includes:
- the second sending module is used to send third information
- the third information includes at least one of the following: first capability information, the number of card slots supported by the first device, the number of cards supported by the first device, the indication information whether the first device supports multiple cards, and whether the first device Indication information for supporting multiple UEs, information about the number of UEs on the first device, information about the number of cards on the first device, relevant indication information about whether the first device is in the multi-UE state, and relevant indication information about whether the first device is in the multi-card state , Whether to request Doka optimization instructions.
- some embodiments of the present disclosure provide a communication device, where the communication device is a fifth communication device and includes:
- the second receiving module is configured to receive third information; wherein the third information includes at least one of the following: first capability information, the number of card slots supported by the first device, the number of cards supported by the first device, and the first device Indication information about whether to support multiple cards, indicating information about whether the first device supports multiple UEs, information about the number of UEs on the first device, information about the number of cards on the first device, information about whether the first device is in a multi-UE state, The relevant indication information of whether the first device is in the multi-card state and the indication information of whether the multi-card optimization is requested;
- the third execution module is configured to execute a fifth related operation according to the third information
- the fifth related operation includes at least one of the following:
- some embodiments of the present disclosure provide a communication device, including a processor, a memory, and a program stored on the memory and running on the processor, and the program is used by the processor.
- the steps of the method for information transmission provided by the first aspect are realized, or the steps of the method for information transmission provided by the second aspect are realized, or the steps of the method for information transmission provided by the third aspect are realized, or the fourth aspect is realized.
- some embodiments of the present disclosure provide a computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, the information provided in the first aspect is realized
- the steps of the method of transmission, or the steps of the method of information transmission provided in the second aspect, or the steps of the method of information transmission provided in the third aspect, or the steps of the method of information transmission provided in the fourth aspect implement the steps of the information transmission method provided in the fifth aspect.
- the information about the second UE can be sent to the first UE, so that the problem of the multi-card terminal can be solved, the performance of the multi-card terminal can be improved, and the user experience of the multi-card terminal can be improved.
- FIG. 1 is a schematic diagram of the architecture of a wireless communication system provided by some embodiments of the present disclosure
- FIG. 2 is a flowchart of a method for information transmission provided by some embodiments of the present disclosure
- FIG. 3 is another flowchart of an information transmission method provided by some embodiments of the present disclosure.
- FIG. 4 is another flowchart of an information transmission method provided by some embodiments of the present disclosure.
- FIG. 5 is another flowchart of an information transmission method provided by some embodiments of the present disclosure.
- FIG. 6 is another flowchart of an information transmission method provided by some embodiments of the present disclosure.
- FIG. 7 is a flowchart of the information transmission process in scenario 1 of the specific embodiment of the disclosure.
- FIG. 8 is a flowchart of the information transmission process in scenario 2 of a specific embodiment of the disclosure.
- FIG. 9 is a flowchart of a UE registration request process in scenario 3 of a specific embodiment of the disclosure.
- FIG. 10 is a flowchart of a UE registration request process in scenario 4 of a specific embodiment of the disclosure.
- FIG. 11 is a structural diagram of a communication device provided by the present disclosure.
- FIG. 13 is another structural diagram of a communication device provided by the present disclosure.
- FIG. 14 is another structural diagram of the communication device provided by the present disclosure.
- FIG. 15 is another structural diagram of the communication device provided by the present disclosure.
- FIG. 16 is another structural diagram of the communication device provided by the present disclosure.
- words such as “exemplary” or “for example” are used as examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in some embodiments of the present disclosure should not be construed as being more preferable or advantageous than other embodiments or design solutions. Rather, the use of words such as “exemplary” or “for example” is intended to present relevant concepts in a specific manner.
- the technology described in this article is not limited to the fifth-generation mobile communication (5th-generation, 5G) system and subsequent evolution communication systems, and is not limited to the LTE/LTE evolution (LTE-Advanced, LTE-A) system, and can also be used for various A kind of wireless communication system, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (Frequency Division Multiple Access, FDMA), Orthogonal Frequency Division Multiple Access (Orthogonal Frequency Division Multiple Access, OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems.
- CDMA Code Division Multiple Access
- TDMA Time Division Multiple Access
- FDMA Frequency Division Multiple Access
- OFDMA Orthogonal Frequency Division Multiple Access
- SC-FDMA Single-carrier Frequency-Division Multiple Access
- the terms “system” and “network” are often used interchangeably.
- the CDMA system can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA).
- UTRA includes Wideband CDMA (Wideband Code Multiple Access (WCDMA) and other CDMA variants.
- the TDMA system can implement radio technologies such as Global System for Mobile (GSM).
- OFDMA system can realize such as Ultra Mobile Broadband (UMB), Evolved UTRA ((Evolution-UTRA, E-UTRA)), IEEE 802.11 ((Wi-Fi)), IEEE 802.16 ((WiMAX)), IEEE 802.20, Flash-OFDM and other radio technologies.
- UMB Ultra Mobile Broadband
- Evolved UTRA (Evolution-UTRA, E-UTRA)
- IEEE 802.11 (Wi-Fi)
- IEEE 802.16 (WiMAX)
- IEEE 802.20 Flash-OFDM and other radio technologies.
- UMB Ultra Mobile Broadband
- Evolved UTRA (E
- LTE and more advanced LTE are new UMTS versions that use E-UTRA.
- UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project (3GPP)".
- CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
- the technology described herein can be used for the systems and radio technologies mentioned above as well as other systems and radio technologies.
- a multi-card terminal is a device with two or more SIM cards.
- the SIM card is an electronic SIM card or a physical SIM card. From the perspective of the network, the same terminal device and different SIM cards constitute different UEs.
- the capability of a multi-card terminal can be single sending and double receiving, single sending and single receiving and double sending and double receiving.
- terminal devices with single sending and single receiving since multiple UEs of the terminal devices cannot work at the same time, there are the most problems.
- the main problems of single sending and single receiving include: (1) There may be a paging conflict between UE1 and UE2 on the same terminal device.
- UE1 will perform voice During the business, because the voice service data interval is 20ms, there is no gap to listen to the paging to UE2; (3) When both UE1 and UE2 are in the connected state, if the terminal equipment resides on the network on the side of UE1, the information about UE2 Data will be lost. If the data about UE2 is about voice called signaling, call drop will occur.
- the terminal device can only send data on one side.
- UE1 and UE2 can send and receive data at the same time, it is required that the band configured by the network for UE1 and UE2 belong to a band combination.
- a device is configured with a first UE and a second UE, and the second UE may be one or more UEs different from the first UE.
- the first UE is connected to the first RAN network element, resides in a cell under the first RAN network element, or the first RAN network element stores the context of the first UE.
- the second UE is connected to the second RAN network element, resides in a cell under the second RAN network element, or the second RAN network element stores the context of the second UE.
- the first UE registers with the first core network (CN).
- the second UE registers the second CN.
- the first CN and the second CN may be the same CN.
- the first UE registers with the first CN network element.
- the second UE registers the second CN network element.
- the first CN network element and the second CN may be the same CN network element.
- the first CN network element and the second CN network element may belong to the same CN or belong to different CNs respectively.
- the wireless communication networks where the first UE and the second UE are located may be the same or different.
- acquisition can be understood as acquisition from configuration, receipt, receipt after request, acquisition through self-learning, derivation acquisition based on unreceived information, or acquisition after processing based on the received information, which can be determined according to actual needs.
- Some disclosed embodiments do not limit this. For example, when a certain capability indication message sent by the device is not received, it can be deduced that the device does not support the capability.
- sending may include broadcasting, broadcasting in system messages, and returning after responding to the request.
- the channel may include at least one of the following: PDU session, Quality of Service (Quality of Service, QoS) flow, Evolved Packet System (EPS) bearer, PDP context , DRB, SRB, Internet Protocol Security (IPsec) association.
- QoS Quality of Service
- EPS Evolved Packet System
- IPsec Internet Protocol Security
- the NG interface may also be called an S1 interface or an N2 interface, and the naming is not limited.
- the wireless communication network may be at least one of the following: a public network, a non-public network; or the first network may be a non-public network.
- the non-public network is an abbreviation for non-public network.
- Non-public networks can be called one of the following: non-public communication networks.
- the non-public network may include at least one of the following deployment methods: a physical non-public network, a virtual non-public network, and a non-public network implemented on the public network.
- the non-public network is a closed access group (Closed Access Group, CAG).
- a CAG can be composed of a group of terminals.
- the non-public network may include or be referred to as a private network.
- the private network may be referred to as one of the following: private communication network, private network, local area network (LAN), private virtual network (PVN), isolated communication network, dedicated communication network, or other names. It should be noted that, in some embodiments of the present disclosure, the naming manner is not specifically limited.
- the public network is short for public network.
- the public network can be called one of the following: public communication network or other naming. It should be noted that, in some embodiments of the present disclosure, the naming manner is not specifically limited.
- the communication device may include at least one of the following: a communication network element and a terminal.
- the communication network element may include at least one of the following: a core network element and a radio access network element.
- the core network element may include but is not limited to at least one of the following: core network equipment, core network nodes, core network functions, core network elements, and mobility management entities (MobilityManagement Entity, MME), access mobility management function (Access Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), serving gateway (serving GW, SGW), PDN Gateway (PDN Gate Way, PDN gateway), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), GPRS service support node (Serving GPRS Support Node, SGSN) , Gateway GPRS Support Node (Gateway GPRS Support Node, GGSN), Application Function (Application Funcation).
- MME Mobility Management Entity
- Access Management Function Access Management Function
- SMF Session Management Function
- UPF User Plane Function
- serving gateway serving gateway
- serving gateway serving gateway
- PDN Gateway PDN Gateway
- the RAN network element may include but is not limited to at least one of the following: radio access network equipment, radio access network node, radio access network function, radio access network unit, 3GPP radio access network , Non-3GPP radio access network, Centralized Unit (CU), Distributed Unit (DU), base station, evolved Node B (eNB), 5G base station (gNB), radio network controller (Radio Network Controller, RNC), base station (NodeB), non-3GPP Inter Working Function (N3IWF), access control (Access Controller, AC) node, access point (Access Point, AP) equipment Or wireless local area network (Wireless Local Area Networks, WLAN) node, N3IWF.
- radio access network equipment radio access network node, radio access network function, radio access network unit, 3GPP radio access network , Non-3GPP radio access network, Centralized Unit (CU), Distributed Unit (DU), base station, evolved Node B (eNB), 5G base station (gNB), radio network controller (Radio Network Controller, RNC), base station (NodeB), non-3
- the base station may be a base station (BTS, Base Transceiver Station) in GSM or CDMA, or a base station (NodeB) in WCDMA, or an evolved base station (eNB or e-NodeB, evolutional Node B) in LTE and 5G base station (gNB), some embodiments of the present disclosure are not limited.
- BTS Base Transceiver Station
- NodeB base station
- eNB evolved base station
- gNB evolutional Node B
- the UE may include at least one of the following: a subscription body (subscription, or Subscriber), a SIM card, a subscription body corresponding to the SIM card, a UE associated with the SIM card, terminal equipment, and terminal equipment And the contract subject, terminal equipment and SIM card.
- the UE is the contractor.
- a terminal device can be configured with multiple contractors.
- the subject of the contract can be reflected by a SIM (Subscriber Identity Module) card.
- SIM Subscriber Identity Module
- One SIM card corresponds to one network contractor.
- the SIM card stores the identity of the subscriber, that is, the identity of the UE, such as SUPI (Subscription Permanent Identifier), or IMSI (International Mobile Subscription Identity), etc. Therefore, when multiple SIM cards are inserted into one terminal device or multiple electronic SIM card information is configured, the terminal device and different contract entities can form different UEs.
- the UE is a terminal composed of a terminal device and a contracting subject.
- the UE is the terminal device.
- the UE is the SIM card or the contract subject corresponding to the SIM card.
- the UE is the UE corresponding to the SIM card.
- the UE is a SIM card.
- the UE is a terminal composed of a terminal device and a SIM card.
- the terminal device can form multiple logical terminals with each card.
- the SIM card may be a card placed in a card slot of a terminal device, or an electronic card in a terminal device.
- the SIM card may include one of the following: a SIM card, a global subscriber identity card (Universal SIM, USIM card), and an embedded SIM card (Embeded SIM, eSIM).
- a SIM card may include one of the following: a SIM card, a global subscriber identity card (Universal SIM, USIM card), and an embedded SIM card (Embeded SIM, eSIM).
- the SIM card can also be used as another name, which is not limited in this disclosure.
- the first device may be referred to as a terminal device.
- the first device of the first UE is the terminal device where the first UE is located.
- the first device may be referred to as a terminal device.
- the device in the present disclosure may be referred to as a terminal device.
- the identification information of the UE includes at least one of the following: UE identification, and temporary identification of the UE.
- the UE identity includes at least one of the following: International Mobile Subscriber Identification Number (IMSI), Network Access Identifier (NAI), SUPI (Subscription permanent identifier), SUCI (Subscription Concealed Identifier).
- IMSI International Mobile Subscriber Identification Number
- NAI Network Access Identifier
- SUPI Subscribescription permanent identifier
- SUCI Subscribescription Concealed Identifier
- the temporary UE identity may include at least one of the following: 5G Globally Unique Temporary UE Identity, 5G GUTI, GUTI (Globally Unique Temporary UE Identity), S-TMSI, ng -S-TMSI, 5G TMSI, TMSI.
- 5G GUTI, GUTI, 5G-S-TMSI, and ng-S-TMSI may contain the identification information of the CN network element and the identification information of the UE in the CN network element.
- 5G TMSI and TMSI may be the identification information of the UE in the CN network element.
- the terminal may include a relay supporting terminal function and/or a terminal supporting relay function.
- the terminal may also be called a terminal device or a user terminal (User Equipment, UE).
- the terminal may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a personal digital assistant (Personal Digital Assistant (PDA),
- terminal-side devices such as mobile Internet devices (MID), wearable devices (Wearable Devices) or vehicle-mounted devices do not limit the specific types of terminals in some embodiments of the present disclosure.
- some embodiments of the present disclosure provide a method of information transmission, which is applied to a first communication device.
- the first communication device may be, but is not limited to, the first CN network element (such as MME or AMF). As shown in FIG. 2, the method includes:
- Step 21 Determine whether the first condition is met.
- Step 22 When it is determined that the first condition is satisfied, the first information of the second UE and/or the target UE information is sent to the first UE.
- the method may further include:
- the third information is described in the embodiment of FIG. 5, and will not be repeated here.
- the target UE may be a target terminal waiting for signaling and/or data to be sent.
- the signaling and/or data waiting to be sent indicates that the network has signaling and/or data waiting to be sent to the target UE.
- the target UE may be the first UE or the second UE.
- the target UE information may include at least one of the following: identification information of the UE and type information of the UE.
- the type information of the UE includes at least one of the following: a first UE and a second UE.
- the type information of the UE indicates that the target end of the signaling and/or data waiting to be sent is the first UE.
- the type information of the UE is the second UE, it indicates that the target end of the signaling and/or data waiting to be sent is the second UE.
- the first UE receives the type information of the UE as the second UE, it may notify the second UE to establish or resume the connection with the network. After the second UE establishes or restores the connection with the network, it can receive the signaling and/or data.
- the type information of the UE includes at least one of the following: current UE and other UEs.
- the other UEs are other UEs on the device where the current UE is located.
- the second UE may be a UE to which the network has signaling and/or data waiting to be sent, and the second UE is different from the first UE.
- the first information of the second UE may include at least one of the following:
- UE identification information of the second UE for example, the UE identification of the second UE, and/or the temporary UE identification of the second UE;
- the information container of the second UE is the information container of the second UE.
- the identification information of the UE may include at least one of the following: UE identification, and temporary identification of the UE.
- the UE identifier may include at least one of the following: International Mobile Subscriber Identification Number (IMSI), Network Access Identifier (NAI), SUPI (Subscription permanent identifier) , SUCI (Subscription Concealed Identifier).
- IMSI International Mobile Subscriber Identification Number
- NAI Network Access Identifier
- SUPI Subscribescription permanent identifier
- SUCI Subscribescription Concealed Identifier
- the temporary UE identity may include at least one of the following: 5G Globally Unique Temporary UE Identity, 5G GUTI, GUTI (Globally Unique Temporary UE Identity), S-TMSI, ng -S-TMSI, 5G TMSI, TMSI.
- 5G GUTI, GUTI, 5G-S-TMSI, and ng-S-TMSI may contain the identification information of the CN network element and the identification information of the UE in the CN network element.
- 5G TMSI and TMSI may be the identification information of the UE in the CN network element.
- the information container of the second UE is used to transmit related information of the second UE.
- the related information of the second UE may be signaling and/or data related to the second UE.
- the information container of the second UE may be visible to the second UE and transparent to the first UE. It is not difficult to understand that this can reduce the implementation complexity of the first UE.
- connection request information is used to request the second UE to establish or restore a connection with the network.
- the connection request information about the second UE may be referred to as paging request information about the second UE.
- connection request information about the second UE may include at least one of the following:
- the reason for the connection request may be called the reason for paging.
- the indication information of the connection request may be referred to as the indication information of paging.
- the reason for the connection request may be information that triggers paging of the second UE or requests the second UE to perform connection establishment or connection recovery services, and/or information about data waiting to be sent to the second UE.
- the reason for the connection request may include at least one of the following: voice services (such as IMS voice called), important services (such as mission critical services), data services, important service signaling, and voice signaling (such as IMS voice called ), NAS signaling, user plane data (such as channel data, the channel is, for example, QoS flow, bearer), etc.
- the second UE may request the second UE to resume or establish a connection by sending connection request information about the second UE.
- the service information that triggers the connection request of the second UE may include at least one of the following: voice service (such as IMS voice called), important service (such as mission critical service), and data service.
- voice service such as IMS voice called
- important service such as mission critical service
- the signaling and/or data information waiting to be sent to the second UE may include at least one of the following: important service signaling (such as mission critical service), voice signaling (such as IMS voice called) , NAS signaling, user plane data (such as channel data, the channel is, for example, QoS flow, bearer), etc.
- the association between the first UE and the second UE may be understood as the first UE and the second UE are located on the same device (for example, the first device). It is not difficult to understand that when both the first UE and the second UE are in a connected state, when the first device with single-receiving capability resides on the first UE side, the first UE can send services and/or services related to the second UE. The data request information assists the first device in deciding whether to switch to the second UE side.
- the sending the first information of the second UE to the first UE may include:
- a notification message or a paging message is sent to the first UE, and the notification message or the paging message includes the first information of the second UE and/or the information of the target UE.
- the notification message may be NAS signaling, which is sent to the first UE when the first UE is in a connected state.
- the paging message is sent to the first UE when the first UE is in an idle state or an inactive state.
- the meeting the first condition may include at least one of the following:
- the capabilities of the first UE, the second UE, and/or the first device are single receipt; in one embodiment, the capabilities of the first UE, the capabilities of the second UE, and the capabilities of the first device can be understood as the same;
- the second UE is in an idle state or an inactive state
- the first UE is in a connected state
- the first UE is associated with the second UE
- the first UE is performing a voice service
- the first UE is performing a service that prevents the first device from monitoring the paging of the second UE, and the first device is the device where the first UE and the second UE are located;
- the second information of the second UE is received from the second CN network element.
- the association between the first UE and the second UE may be understood as the first UE and the second UE are located on the same device (for example, the first device).
- the first UE and the second UE are respectively UEs corresponding to different SIM cards on the same device; in another embodiment, the first UE and the second UE are UEs corresponding to different card slots on the same device.
- the first condition is met: the first UE, the second UE and/or the first device are capable of single-receiving (single-receiving includes single-sending and single-receiving), and the first UE and the second UE The UE has a paging conflict.
- the first UE and the second UE have a paging conflict.
- the value of the UE identifier mod N of the first UE is the same as the value of the UE identifier mod N of the second UE or the UE passing the first UE
- the paging frame calculated by the identity is the same as the paging frame calculated by the UE identity of the second UE.
- N can be but not limited to 1024.
- the identity of the UE may be IMSI.
- the UE identity mod N is one of the parameters for calculating paging occasion (Paging Occassion).
- the UE identifier mod N is the same, the paging occasion is the same, and the first device is a single-receiving device, so it is impossible to monitor the paging of the first UE and the second UE at the same paging occasion.
- the first condition is met: the first UE is performing a voice service, and the second UE is in an idle state or an inactive state. Since the data packet interval of the voice service is 20ms, the first device cannot switch to monitor the paging of the second UE within 20ms. It is not difficult to understand that when the first UE performs a voice service, the paging for the second UE will be lost.
- the first CN network element simultaneously serves the first UE and the second UE.
- the first CN network element may be a CN network element serving the first UE; the second CN network element may be a CN network element serving the second UE.
- meeting the first condition is: receiving paging request information about the second UE from the second CN network element. It is not difficult to understand that when the serving CN network elements of the first UE and the second UE are different, if the second UE is to be paged through the first UE, it is necessary to negotiate between the CN network elements they serve.
- the first condition is satisfied that: the second UE is in an idle state or an inactive state (such as an RRC inactive state), and the first UE is in a connected state. It is not difficult to understand that when the second UE is in the idle or inactive state, if the second UE is to be paged, the entire RA needs to be paged, which consumes more radio resources, and the first UE is in the connected state, and its location is determined , The paging about the second UE is converted into a NAS layer data packet of the first UE and sent to the first UE, which can save radio resources.
- an inactive state such as an RRC inactive state
- information about the second UE can be sent to the first UE, so that the problem of the multi-card terminal can be solved, the performance of the multi-card terminal can be improved, and the user experience of the multi-card terminal can be improved.
- some embodiments of the present disclosure provide a method of information transmission, which is applied to a second communication device.
- the second communication device may be but not limited to a second CN network element, and the method includes:
- Step 31 Determine whether the second condition is met.
- Step 32 When it is determined that the second condition is met, perform the second operation.
- the third information is acquired.
- the third information is described in the embodiment of FIG. 5, and will not be repeated here.
- the second operation includes at least one of the following:
- the paging message may be a piece of signaling, which is sent to the second UE when it is in an idle state or an inactive state.
- the second communication device is the second CN network element
- the related information of the second UE is sent to the RAN network element.
- the RAN network element then sends a paging message to the second UE. It is not difficult to understand that the second CN network element can send a page to the second UE on the one hand or send a page through the RAN network element of the second UE, and on the other hand request the first CN network element to send a paging message to the second UE through the first UE.
- the second information can achieve the purpose of resolving conflicts and increasing the success rate.
- the second information of the second UE may include at least one of the following:
- UE identity information of the first UE associated with the second UE for example, the UE identity of the first UE, or the temporary UE identity of the first UE
- UE identification information of the second UE for example, the UE identification of the second UE, or the temporary UE identification of the second UE
- the information container of the second UE is the information container of the second UE.
- the UE identification information of the second UE and the UE identification information of the first UE may be as described in the embodiment of FIG. 2 and will not be repeated here.
- the service information that triggers the connection request of the second UE is as described in the embodiment of FIG. 2 and will not be repeated here.
- the information of the signaling and/or data waiting to be sent to the second UE is as described in the embodiment of FIG. 2 and will not be repeated here.
- the information container of the second UE may be used to transmit related information of the second UE.
- the related information of the second UE may be signaling and/or data related to the second UE.
- the information container of the second UE may be visible to the second UE and transparent to the first UE.
- the signaling of the second UE includes but is not limited to at least one of the following: NAS signaling of the second UE, and IMS signaling of the second UE.
- the UE identification information of the first UE associated with the second UE is sent to the first CN network element; the first CN network element can find the first UE according to the UE identification information of the first UE. In another implementation manner, the first CN network element may find the first UE according to the association between the first UE and the second UE and the UE identification information of the second UE.
- the second operation includes: sending a paging message to the second UE, and requesting the first CN network element to send the connection request information related to the second UE through the first UE (as shown in Figure 2 Example). It is not difficult to understand that sending the connection request information about the second UE to the second UE and through the first UE at the same time can improve the success rate.
- the second operation includes: sending related information of the second UE to the second UE, and requesting the first CN network element to send the information container of the second UE through the first UE. It is not difficult to understand that when the capabilities of the first UE, the second UE, and/or the first device are single receiving, if the first UE and the second UE are in the connected state at the same time, the network cannot confirm the network currently monitored by the first device. If the related information of the second UE is an important signaling or important data, such as a voice call, the related information of the second UE can be sent to the second UE and through the first UE at the same time to avoid loss and improve the success rate.
- the related information of the second UE is an important signaling or important data, such as a voice call
- the second operation includes: sending related information of the second UE to the second UE, and requesting the first CN network element to send paging request information about the second UE through the first UE .
- a service indication is requested to the first UE to indicate that voice has arrived.
- the first CN network element may be a CN network element serving the first UE; the second CN network element may be a CN network element serving the second UE.
- the satisfaction of the second condition may include at least one of the following:
- the capability of the first UE, the second UE and/or the first device is single receipt
- the second UE is in an idle state or an inactive state
- the first UE is associated with the second UE
- the first UE is performing a voice service
- the first UE is performing a service that prevents the first device from monitoring the paging of the second UE, and the first device is the device where the first UE and the second UE are located.
- information about the second UE can be sent to the first UE, so that the problem of the multi-card terminal can be solved, the performance of the multi-card terminal can be improved, and the user experience of the multi-card terminal can be improved.
- some embodiments of the present disclosure provide a method of information transmission, which is applied to a third communication device.
- the third communication device may be, but is not limited to, at least one of the following: a terminal, a first device, a UE (such as a first UE, and/or a second UE), as shown in FIG. 4, the method includes:
- Step 41 Receive the first information of the second UE and/or target UE information
- Step 42 Perform a third operation according to the first information of the second UE and/or target UE information.
- the third operation includes at least one of the following:
- the first information of the second UE is as described in the implementation example in FIG. 2 and will not be repeated here.
- the first UE can send information about the second UE, request to establish or restore the connection between the second UE and the network, so that the problem of multi-card terminals can be solved, and the performance of the multi-card terminals can be improved. Improve the user experience of multi-card terminals.
- some embodiments of the present disclosure provide a method for information transmission, which is applied to a fourth communication device.
- the fourth communication device may be, but is not limited to, at least one of the following: a terminal, a first device, a UE (such as a first UE, and/or a second UE), as shown in FIG. 5, the method includes:
- Step 51 Send the third information.
- the third information includes at least one of the following: first capability information, the number of card slots supported by the first device, the number of cards supported by the first device, the indication information whether the first device supports multiple cards, and whether the first device Indication information for supporting multiple UEs, information about the number of UEs on the first device, information about the number of cards on the first device, relevant indication information about whether the first device is in the multi-UE state, and relevant indication information about whether the first device is in the multi-card state , Whether to request Doka optimization instructions.
- the first capability information includes at least one of the following: single sending and single receiving, single sending and double receiving, double sending and double receiving, single receiving, single sending, double sending, double sending, multiple receiving, and multiple sending.
- the first capability information is the capability of the first UE, the second UE and/or the first device.
- the first device may be a device where the first UE is located, or the first device may be a device where the first UE and the second UE are located together. It is not difficult to understand that, for example, there are two card slots on the terminal device, the first card slot is inserted into the first SIM card, and the first SIM card corresponds to the first UE. There is no SIM card inserted in the second card slot. Then the terminal device is the device where the first UE is located. The first card slot is inserted into the first SIM card and the second card slot is inserted into the second SIM card. The first SIM card corresponds to the first UE, and the first SIM card corresponds to the second UE. The terminal device is a device where the first UE and the second UE are located together. There may be multiple second UEs.
- the UE sends the first capability information.
- the meeting the first condition may include at least one of the following:
- the network is configured with dual connectivity or carrier aggregation
- the first terminal capability is updated
- the UE quantity information on the first device may be the current UE quantity on the first device.
- the number of UEs on the first device can be understood as the number of cards on the first device.
- the card quantity information on the first device may be the current card quantity on the first device.
- the number of cards of the first device may include at least one of the following: single card, dual card, and multiple cards.
- the indication information of whether to request multi-card optimization is set to: request multi-card optimization.
- satisfying the third condition may include at least one of the following:
- the number of card slots supported by the first device or the number of cards supported by the first device is greater than or equal to 2;
- the UE quantity information on the first device or the card quantity information on the first device is greater than or equal to 2;
- the first device supports multiple cards or the first device supports multiple UEs
- the first device is in a multi-UE state
- the first device is in a multi-card state.
- the number of cards on the device is greater than or equal to 2, that is, the device is in a multi-card state.
- the number of UEs on the device is greater than or equal to 2, that is, the device is in a multi-UE state.
- the device being in the multi-UE state can be understood as a second UE associated with the first UE.
- information about the second UE can be sent to the first UE, so that the problem of the multi-card terminal can be solved, the performance of the multi-card terminal can be improved, and the user experience of the multi-card terminal can be improved.
- the fifth communication device may be, but is not limited to, at least one of the following: RAN network element, CN network element, as shown in FIG. 6, the method includes:
- Step 61 Receive the third information.
- the third information includes at least one of the following: first capability information, the number of card slots supported by the first device, the number of cards supported by the first device, the indication information whether the first device supports multiple cards, and whether the first device Indication information for supporting multiple UEs, information about the number of UEs on the first device, information about the number of cards on the first device, relevant indication information about whether the first device is in the multi-UE state, and relevant indication information about whether the first device is in the multi-card state , Whether to request Doka optimization instructions.
- the third information is as described in the embodiment of FIG. 5, and will not be repeated here.
- Step 62 Perform a fifth related operation according to the third information.
- the fifth related operation may include at least one of the following:
- the meeting the fourth condition may include at least one of the following:
- the number of card slots supported by the first device or the number of cards supported by the first device is greater than or equal to 2;
- the UE quantity information on the first device or the card quantity information on the first device is greater than or equal to 2;
- the first device supports multiple cards or the first device supports multiple UEs
- the first device is in a multi-UE state
- the first device is in a multi-card state; the indication information whether to request multi-card optimization indicates that multi-card optimization is requested.
- the fifth communication device when the fifth communication device is a CN network element, forward the received third information to the RAN network element;
- the fifth communication device when the fifth communication device is a RAN network element, forward the received third information to the CN network element;
- the operation of performing multi-card optimization may include at least one of the following:
- the device identification information may include at least one of the following: a first terminal device identification and a second terminal device identification.
- the first terminal equipment identifier may be the terminal equipment identifier of the first UE.
- the second terminal device identifier may be a terminal device identifier associated with the first UE, for example, other terminal device identifiers on the device where the first UE is located. It is not difficult to understand that each card slot on a terminal device can be configured with a terminal device identifier.
- the terminal device identifier of the UE corresponding to the SIM card is the terminal device identifier of the card slot.
- the terminal device identifiers corresponding to the other card slots of the terminal device may be the terminal device identifiers associated with the UE corresponding to the SIM card.
- the first terminal device identifier may be the terminal device identifier of the first UE.
- the second terminal device identifier may be the terminal device identifier of the second UE.
- the first UE may have an associated terminal equipment identifier but no associated second UE. It is not difficult to understand that, for example, there are two card slots on the terminal device, the first card slot is inserted into the first SIM card, and the first SIM card corresponds to the first UE. There is no SIM card inserted in the second card slot. The terminal device identification corresponding to the second card slot does not have a corresponding UE. Then the first UE has the terminal equipment identifier of the associated terminal, but there is no associated second UE.
- the device identification information is the device identification information of the first device.
- the first terminal device identifier and/or the second terminal device identifier are the first terminal device identifier and/or the second terminal device identifier of the first device.
- the first device may be a device where the first UE is located, or the first device may be a device where the first UE and the second UE are located together.
- the terminal equipment identifier may include at least one of the following: IMEI (International Mobile Equipment Identity), IMEISV (International Mobile Station Equipment Identity and Software Version number), and PEI (Permanent Equipment Identifier).
- IMEI International Mobile Equipment Identity
- IMEISV International Mobile Station Equipment Identity and Software Version number
- PEI Permanent Equipment Identifier
- the first terminal device is identified as the first IMEI
- the second terminal device is identified as the second IMEI.
- the first device may be a device where the first UE is located, or the first device may be a device where the first UE and the second UE are located together. It is not difficult to understand that, for example, there are two card slots on the terminal device, the first card slot is inserted into the first SIM card, and the first SIM card corresponds to the first UE. There is no SIM card inserted in the second card slot. Then the terminal device is the device where the first UE is located. The first card slot is inserted into the first SIM card and the second card slot is inserted into the second SIM card. The first SIM card corresponds to the first UE, and the first SIM card corresponds to the second UE. The terminal device is a device where the first UE and the second UE are located together. There may be multiple second UEs.
- the device identification information may include at least one of the following: a first terminal device identification and a second terminal device identification.
- the RAN network element may include at least one of the following: a first RAN network element and a second RAN network element.
- the first RAN network element may be a RAN network element serving the first UE; the second RAN network element may be a RAN network element serving the second UE.
- the first RAN network element and the second RAN network element may be the same or different.
- the CN network element may include at least one of the following: a first CN network element and a second CN network element.
- the first CN network element may be a CN network element serving the first UE; the second CN network element may be a CN network element serving the second UE.
- the first CN network element and the second CN network element may be the same or different.
- the first UE and the second UE are UEs on the same device.
- information about the second UE can be sent to the first UE, so that the problem of the multi-card terminal can be solved, the performance of the multi-card terminal can be improved, and the user experience of the multi-card terminal can be improved.
- Application scenario 1 of some embodiments of the present disclosure mainly describes that the serving CN network elements of the first UE and the second UE are both the first CN network element; the first CN network element sends the first information of the second UE to the first UE process.
- Step 71 The second UE is in an idle state, and the first CN network element needs to page the second UE.
- the first CN network element When the first condition is met, the first CN network element sends a notification message (notification) to the first UE, and the notification message includes the first information of the second UE.
- the first information of the second UE is as described in the embodiment in FIG. 2 and will not be repeated here.
- the first condition may include at least one of the following:
- the capability of the first UE, the second UE and/or the first device is single receipt
- the first UE is in a connected state
- the first UE is associated with the second UE.
- Step 72 The first UE sends the received first information of the second UE to the second UE
- Step 73 The second UE sends an RRC establishment request message or an RRC recovery request message to the RAN network element;
- Step 74 The RAN network element sends an RRC setup message or an RRC recovery message to the second UE;
- Step 75 The second UE sends an RRC establishment complete message or an RRC recovery complete message to the RAN network element;
- Step 76 The RAN network element sends an initial UE message or a notification response message to the first CN network element. That is, through step 73 to step 76, the second UE establishes or restores the connection.
- Application scenario 2 of some embodiments of the present disclosure mainly describes that the serving CN network elements of the first UE and the second UE are the first CN network element and the second CN network element respectively; the second CN network element sends to the first CN network element
- the second information of the second UE is a process in which the first CN network element sends the first information of the second UE to the first UE. Please refer to Figure 8, including the following steps:
- Step 81 The second UE is in an idle state, and the second CN network element needs to page the second UE.
- the second CN network element queries UDM for information about the CN network element of the first UE (that is, the first CN network element), and the first UE is a UE associated with the second UE.
- Step 82 The second CN network element sends the second information of the second UE to the first CN network element (as described in the embodiment of FIG. 3, for example, the second information of the second UE may be sent through a paging request message).
- Step 83 The first CN network element sends a notification message (notification) to the first UE, where the notification message includes the first information of the second UE.
- the first information of the second UE is as described in the embodiment of FIG. 2.
- the first CN network element when the first condition is met, sends a notification message (notification) to the first UE, where the notification message includes the first information of the second UE.
- the first condition may include at least one of the following:
- the capability of the first UE, the second UE and/or the first device is single receipt
- the first UE is in a connected state
- the first UE is associated with the second UE.
- Step 84 The first UE sends the received first information of the second UE to the second UE
- Step 85 The second UE sends an RRC establishment request message or an RRC recovery request message to the RAN network element;
- Step 86 The RAN network element sends an RRC setup message or an RRC recovery message to the second UE;
- Step 87 The second UE sends an RRC establishment complete message or an RRC recovery complete message to the RAN network element;
- Step 88 The RAN network element sends an initial UE message or a notification response message to the first CN network element. That is, through step 85 to step 88, the second UE establishes or restores the connection.
- the application scenario 3 of some embodiments of the present disclosure takes the first UE as an example, and mainly describes the process of the UE requesting registration. Refer to Figure 9 and include the following steps:
- Step 91 The first UE sends a registration request message to the first CN network element (described below by taking AMF as an example), where the registration request message includes the third information (specifically as described in the embodiment of FIG. 5).
- the AMF determines whether to perform the multi-card optimization operation and/or determines the type of the multi-card optimization operation (specifically as described in the embodiment of FIG. 6).
- Step 92 The AMF registers the terminal to the Unified Data Manager (UDM). Include the first information in the registration request.
- UDM Unified Data Manager
- AMF can also obtain and order the contract data of the terminal.
- Step 93 Establish a policy association between the AMF and the PCF regarding the UE.
- AMF can obtain the terminal strategy from the PCF.
- Step 94 The AMF sends the third information to the RAN network element (specifically, as described in the embodiment of FIG. 5).
- the RAN network element determines whether to perform the multi-card optimization operation and/or determines the type of the multi-card optimization operation (specifically, as described in the embodiment of FIG. 6).
- AMF returns a registration response message to the terminal.
- the AMF sends an initial context establishment request message to the RAN network element.
- the initial context establishment request message includes the third information.
- Step 95 The first UE returns a registration complete message to the AMF.
- the first UE during the registration process of the first UE, provides the third information to the network.
- the network may determine whether to perform the multi-card optimization operation and/or determine the type of the multi-card optimization operation according to the third information. This can support multi-card optimized operation.
- the application scenario 4 of some embodiments of the present disclosure takes the first UE as an example, and mainly describes the process in which the network obtains the terminal equipment identity of the UE from the UE after the UE initiates a registration request. Please refer to Figure 10, including the following steps:
- Step 101 The first UE sends a registration request message to the first CN network element (described below by taking AMF as an example), where the registration request message includes third information (as described in the embodiment in FIG. 5).
- the AMF determines to obtain the device identifier of the first UE (specifically as described in the embodiment of FIG. 6), and then proceeds to step 102; otherwise, proceeds to step 104.
- Step 102 The AMF sends an identification request message to the UE.
- the identification request message contains the requested identification type.
- the identification type includes at least one of the following: terminal equipment identification (such as IMEI, or IMEISV), first terminal equipment identification, second terminal equipment identification, first terminal equipment identification and second terminal equipment identification, all of the first equipment
- the ID of the terminal device is the device where the first UE is located.
- Step 103 The UE sends device identification information to the AMF.
- the device identification information includes at least one of the following: a first terminal device identification and a second terminal device identification.
- the first terminal device identifier is the terminal device identifier of the first UE.
- the UE when the received identifier type indicates "all terminal device identifiers of the first device" or "first terminal device identifier and second terminal device identifier", the UE sends the first terminal device identifier and the second terminal device identifier Equipment Identity.
- the UE when the received identifier type indicates "terminal device identifier" or "first terminal device identifier", the UE sends the first terminal device identifier.
- the UE when the received identification type indicates "second terminal equipment identification", the UE sends the second terminal equipment identification.
- the UE returns an identification response message to the AMF.
- the identification response message includes device identification information.
- Step 104 The AMF registers the terminal to the Unified Data Manager (UDM). Include the first information in the registration request.
- UDM Unified Data Manager
- AMF can also obtain and order the contract data of the terminal.
- Step 105 Establish a policy association between the AMF and the PCF regarding the UE.
- AMF can obtain the terminal strategy from the PCF.
- Step 106 The AMF sends the third information to the RAN network element (specifically, as described in the embodiment of FIG. 5).
- the RAN network element determines whether to perform the multi-card optimization operation and/or determines the type of the multi-card optimization operation (specifically, as described in the embodiment of FIG. 6).
- AMF returns a registration response message to the terminal.
- the AMF sends an initial context establishment request message to the RAN network element.
- the initial context establishment request message includes the third information.
- Step 107 The first UE returns a registration complete message to the AMF.
- the first UE during the registration process of the first UE, provides the third information to the network.
- the network may determine whether to perform the multi-card optimization operation and/or determine the type of the multi-card optimization operation according to the third information. This can support multi-card optimized operation.
- the communication device is a first communication device
- the first communication device may be but not limited to a first CN network element (such as MME or AMF), such as
- the communication device 110 includes:
- the first judgment module 111 is configured to judge whether the first condition is met
- the first sending module 112 is configured to send first information of the second UE and/or target UE information to the first UE when the first condition is determined to be satisfied.
- the first information of the second UE includes at least one of the following:
- the information container of the second UE is the information container of the second UE.
- connection request information about the second UE includes at least one of the following:
- the meeting the first condition includes at least one of the following
- the capability of the first UE, the second UE and/or the first device is single receipt
- the second UE is in an idle state or an inactive state
- the first UE is in a connected state
- the first UE is associated with the second UE
- the first UE is performing a voice service
- the first UE is performing a service that prevents the first device from monitoring the paging of the second UE, and the first device is the device where the first UE and the second UE are located;
- the second information of the second UE is received from the second CN network element.
- the communication device 110 further includes:
- the obtaining module is used to obtain third information
- the third information includes at least one of the following: first capability information, the number of card slots supported by the first device, the number of cards supported by the first device, the indication information whether the first device supports multiple cards, and whether the first device Indication information for supporting multiple UEs, information about the number of UEs on the first device, information about the number of cards on the first device, relevant indication information about whether the first device is in the multi-UE state, and relevant indication information about whether the first device is in the multi-card state , Whether to request Doka optimization instructions.
- the communication device 110 can implement the various processes implemented in the method embodiment shown in FIG. 2 of the present disclosure and achieve the same beneficial effects. To avoid repetition, details are not described herein again.
- some embodiments of the present disclosure provide a communication device, the communication device is a second communication device, the second communication device may be but not limited to a second CN network element, as shown in FIG.
- the communication device 120 includes:
- the second judgment module 121 is used to judge whether the second condition is met
- the first execution module 122 is configured to execute the second operation when it is determined that the second condition is met;
- the second operation includes at least one of the following:
- the related information of the second UE includes at least one of the following:
- the information container of the second UE is the information container of the second UE.
- the meeting the second condition includes at least one of the following:
- the capability of the first UE, the second UE and/or the first device is single receipt
- the second UE is in an idle state or an inactive state
- the first UE is associated with the second UE
- the first UE is performing a voice service
- the first UE is performing a service that prevents the first device from monitoring the paging of the second UE, and the first device is the device where the first UE and the second UE are located.
- the communication device 120 can implement the various processes implemented in the method embodiment shown in FIG. 3 of the present disclosure and achieve the same beneficial effects. To avoid repetition, details are not described herein again.
- the communication device is a third communication device.
- the third communication device may be, but is not limited to, at least one of the following: a terminal, a first device, a UE ( Such as the first UE and/or the second UE), as shown in FIG. 13, the communication device 130 includes:
- the first receiving module 131 is configured to receive first information of the second UE and/or target UE information
- the second execution module 132 is configured to execute a third operation according to the first information of the second UE and/or target UE information;
- the third operation includes at least one of the following:
- the first information of the second UE includes at least one of the following:
- the information container of the second UE is the information container of the second UE.
- the communication device 130 can implement the various processes implemented in the method embodiment shown in FIG. 4 of the present disclosure and achieve the same beneficial effects. To avoid repetition, details are not described herein again.
- the communication device is a fourth communication device.
- the fourth communication device may be, but is not limited to, at least one of the following: a terminal, a first device, a UE ( Such as the first UE and/or the second UE), as shown in FIG. 14, the communication device 140 includes:
- the second sending module 141 is configured to send third information
- the third information includes at least one of the following: first capability information, the number of card slots supported by the first device, the number of cards supported by the first device, the indication information whether the first device supports multiple cards, and whether the first device Indication information for supporting multiple UEs, information about the number of UEs on the first device, information about the number of cards on the first device, relevant indication information about whether the first device is in the multi-UE state, and relevant indication information about whether the first device is in the multi-card state , Whether to request Doka optimization instructions.
- the first capability information includes at least one of the following: single sending and single receiving, single sending and double receiving, double sending and double receiving, single receiving, single sending, double sending, double sending, multiple receiving, and multiple sending.
- the second sending module 141 is specifically configured to:
- satisfying the first condition includes at least one of the following:
- the network is configured with dual connectivity or carrier aggregation
- the first terminal capability is updated
- the communication device 140 can implement the various processes implemented in the method embodiment shown in FIG. 5 of the present disclosure and achieve the same beneficial effects. To avoid repetition, details are not described herein again.
- the communication device is a fifth communication device.
- the fifth communication device may be, but is not limited to, at least one of the following: RAN network element, CN network element, As shown in FIG. 15, the communication device 150 includes:
- the second receiving module 151 is configured to receive third information; wherein, the third information includes at least one of the following: first capability information, the number of card slots supported by the first device, the number of cards supported by the first device, the first Indication information about whether the device supports multiple cards, whether the first device supports multiple UEs, information about the number of UEs on the first device, information about the number of cards on the first device, and information about whether the first device is in a multi-UE state , The relevant indication information of whether the first device is in the multi-card state, and the indication information of whether to request multi-card optimization;
- the third execution module 152 is configured to execute a fifth related operation according to the third information
- the fifth related operation includes at least one of the following:
- the third execution module 152 is specifically configured to:
- the fourth condition includes at least one of the following:
- the number of card slots supported by the first device or the number of cards supported by the first device is greater than or equal to 2;
- the UE quantity information on the first device or the card quantity information on the first device is greater than or equal to 2;
- the first device supports multiple cards or the first device supports multiple UEs
- the first device is in a multi-UE state
- the first device is in a multi-card state
- the indication information whether to request multi-card optimization indicates that multi-card optimization is requested.
- the communication device 150 can implement the various processes implemented in the method embodiment shown in FIG. 6 of the present disclosure and achieve the same beneficial effects. To avoid repetition, details are not repeated here.
- FIG. 16 is a schematic structural diagram of another communication device provided by some embodiments of the present disclosure.
- the communication device 160 includes: a processor 161, a memory 162, and a memory 162
- a program that can be run on the processor, the components of the communication device 160 are coupled together through the bus interface 163, and when the program is executed by the processor 161, the method implemented in the method embodiment shown in FIG. 2 can be implemented
- Each of the processes, or each process implemented in the method embodiment shown in FIG. 6 is implemented, and can achieve the same technical effect. To avoid repetition, details are not described here.
- Some embodiments of the present disclosure also provide a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, each process implemented in the method embodiment shown in FIG. 2 is implemented. Or, implement each process implemented in the method embodiment shown in FIG. 3, or implement each process implemented in the method embodiment shown in FIG. 4, or implement each process implemented in the method embodiment shown in FIG. 5 , Or, implement each process implemented in the method embodiment shown in FIG. 6 above, and achieve the same technical effect. To avoid repetition, details are not repeated here.
- the computer-readable storage medium such as read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disk or optical disk, etc.
- the methods in the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware, but in many cases the former is better Implementation.
- the technical solution of the present disclosure can be embodied in the form of a software product in essence or part that contributes to the existing technology, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk,
- the CD-ROM includes several instructions to enable a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present disclosure.
- the disclosed device and method may be implemented in other ways.
- the device embodiments described above are only schematic.
- the division of the unit 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 Can be integrated into another system, or some features can be ignored, or not implemented.
- 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 purpose of the solution of this embodiment.
- each functional unit in each embodiment of the present disclosure 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 function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
- the technical solution of the present disclosure essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present disclosure.
- the foregoing storage media include various media that can store program codes, such as a U disk, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
- each component or each step can be decomposed and/or recombined.
- These decompositions and/or recombinations should be regarded as equivalent solutions of the present disclosure.
- the steps for performing the above-mentioned series of processing can naturally be executed in chronological order in the order described, but it does not necessarily need to be executed in chronological order, and some steps can be executed in parallel or independently of each other.
- Those of ordinary skill in the art can understand that all or any of the steps or components of the methods and devices of the present disclosure can be used in any computing device (including a processor, storage medium, etc.) or a network of computing devices, using hardware and firmware , Software, or a combination of them. This can be achieved by those of ordinary skill in the art using their basic programming skills after reading the description of the present disclosure.
- the embodiments described in the embodiments of the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof.
- the processing unit can be implemented in one or more application specific integrated circuits (Application Specific Integrated Circuits, ASIC), digital signal processor (Digital Signal Processing, DSP), digital signal processing device (DSP Device, DSPD), programmable Logic Device (Programmable Logic Device, PLD), Field Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processor, controller, microcontroller, microprocessor, others for performing the functions described in this disclosure Electronic unit or its combination.
- ASIC Application Specific Integrated Circuits
- DSP Digital Signal Processing
- DSP Device digital signal processing device
- DPD digital signal processing device
- PLD programmable Logic Device
- Field Programmable Gate Array Field-Programmable Gate Array
- FPGA Field-Programmable Gate Array
- the technology described in the embodiments of the present disclosure may be implemented through modules (eg, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure.
- the software codes can be stored in the memory and executed by the processor.
- the memory may be implemented in the processor or external to the processor.
- the purpose of the present disclosure can also be achieved by running a program or a group of programs on any computing device.
- the computing device may be a well-known general-purpose device. Therefore, the object of the present disclosure can also be achieved only by providing a program product containing program code for implementing the method or device. That is, such a program product also constitutes the present disclosure, and a storage medium storing such a program product also constitutes the present disclosure. Obviously, the storage medium may be any known storage medium or any storage medium developed in the future.
- each component or each step can be decomposed and/or recombined. These decompositions and/or recombinations should be regarded as equivalent solutions of the present disclosure.
- the steps for performing the above-mentioned series of processing may naturally be performed in chronological order in the order described, but it is not necessary to be performed in chronological order. Certain steps can be performed in parallel or independently of each other.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本公开实施例提供一种信息传送的方法及通信设备,应用于第一通信设备的信息传送的方法包括:判断是否满足第一条件;确定满足第一条件时,向第一UE发送第二UE的第一信息,和/或目标UE信息。
Description
相关申请的交叉引用
本申请主张在2019年1月18日在中国提交的中国专利申请号No.201910055961.5的优先权,其全部内容通过引用包含于此。
本公开实施例涉及无线通信技术领域,尤其涉及一种信息传送的方法及通信设备。
在现网中,多卡终端越来越常用,多卡终端上可具有两个或大于两个的用户识别卡(Subscriber Identity Module,SIM)。但由于缺乏网络间协商,导致多卡终端的用户适用体验不够优化,比如可能出现寻呼冲突等情况。因此,如何解决多卡终端的问题,提升多卡终端的用户体验,是亟待解决的技术问题。
发明内容
本公开实施例提供一种信息传送的方法及通信设备,用于解决多卡终端的问题,提升多卡终端的用户体验。
为了解决上述技术问题,本公开是这样实现的:
第一方面,本公开的一些实施例提供了一种信息传送的方法,应用于第一通信设备,包括:
判断是否满足第一条件;
确定满足第一条件时,向第一UE发送第二UE的第一信息,和/或目标UE信息。
第二方面,本公开的一些实施例提供了一种信息传送的方法,应用于第二通信设备,包括:
判断是否满足第二条件;
确定满足第二条件时,执行第二操作;
其中,所述第二操作包括以下至少一项:
向第一CN网元请求通过第一UE发送第二UE的第二信息;
向第二UE发送寻呼消息;
向第二UE的RAN网元发送第二UE的相关信息。
第三方面,本公开的一些实施例提供了一种信息传送的方法,应用于第三通信设备,包括:
接收第二UE的第一信息和/或目标UE信息;
根据所述第二UE的第一信息和/或目标UE信息,执行第三操作;
其中,所述第三操作包括以下至少一项:
向第二UE发送所述第二UE的第一信息;
请求建立或恢复第二UE与网络间连接。
第四方面,本公开的一些实施例提供了一种信息传送的方法,应用于第四通信设备,包括:
发送第三信息;
其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数量、第一设备是否支持多卡的指示信息、第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息。
第五方面,本公开的一些实施例提供了一种信息传送的方法,应用于第五通信设备,包括:
接收第三信息;其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数量、第一设备是否支持多卡的指示信息、第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息;
根据所述第三信息,执行第五相关操作;
其中,所述第五相关操作包括以下至少一项:
确定是否执行多卡优化的操作;
确定多卡优化操作的类型;
执行多卡优化的操作。
第六方面,本公开的一些实施例提供了一种通信设备,所述通信设备为第一通信设备,包括:
第一判断模块,用于判断是否满足第一条件;
第一发送模块,用于确定满足第一条件时,向第一UE发送第二UE的第一信息,和/或目标UE信息。
第七方面,本公开的一些实施例提供了一种通信设备,所述通信设备为第二通信设备,包括:
第二判断模块,用于判断是否满足第二条件;
第一执行模块,用于确定满足第二条件时,执行第二操作;
其中,所述第二操作包括以下至少一项:
向第一CN网元请求通过第一UE发送第二UE的第二信息;
向第二UE发送寻呼消息;
向第二UE的RAN网元发送第二UE的相关信息。
第八方面,本公开的一些实施例提供了一种通信设备,所述通信设备为第三通信设备,包括:
第一接收模块,用于接收第二UE的第一信息和/或目标UE信息;
第二执行模块,用于根据所述第二UE的第一信息和/或目标UE信息,执行第三操作;
其中,所述第三操作包括以下至少一项:
向第二UE发送所述第二UE的第一信息;
请求建立或恢复第二UE与网络间连接。
第九方面,本公开的一些实施例提供了一种通信设备,所述通信设备为第四通信设备,包括:
第二发送模块,用于发送第三信息;
其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数量、第一设备是否支持多卡的指示信息、 第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息。
第十方面,本公开的一些实施例提供了一种通信设备,所述通信设备为第五通信设备,包括:
第二接收模块,用于接收第三信息;其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数量、第一设备是否支持多卡的指示信息、第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息;
第三执行模块,用于根据所述第三信息,执行第五相关操作;
其中,所述第五相关操作包括以下至少一项:
确定是否执行多卡优化的操作;
确定多卡优化操作的类型;
执行多卡优化的操作。
第十一方面,本公开的一些实施例提供了一种通信设备,包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序,所述程序被所述处理器执行时实现第一方面提供的信息传送的方法的步骤,或者,实现第二方面提供的信息传送的方法的步骤,或者,实现第三方面提供的信息传送的方法的步骤,或者,实现第四方面提供的信息传送的方法的步骤,或者,实现第五方面提供的信息传送的方法的步骤。
第十二方面,本公开的一些实施例提供了一种计算机可读存储介质,所述计算机可读存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现第一方面提供的信息传送的方法的步骤,或者,实现第二方面提供的信息传送的方法的步骤,或者,实现第三方面提供的信息传送的方法的步骤,或者,实现第四方面提供的信息传送的方法的步骤,或者,实现第五方面提供的信息传送的方法的步骤。
在本公开的一些实施例中,可以向第一UE发送关于第二UE的信息,从 而可以解决多卡终端的问题,提升多卡终端的性能,从而提高用户对多卡终端的使用体验。
通过阅读下文优选实施方式的详细描述,各种其他的优点和益处对于本领域普通技术人员将变得清楚明了。附图仅用于示出优选实施方式的目的,而并不认为是对本公开的限制。而且在整个附图中,用相同的参考符号表示相同的部件。在附图中:
图1为本公开的一些实施例提供的无线通信系统的架构示意图;
图2为本公开的一些实施例提供的信息传送的方法的流程图;
图3为本公开的一些实施例提供的信息传送的方法的另一流程图;
图4为本公开的一些实施例提供的信息传送的方法的另一流程图;
图5为本公开的一些实施例提供的信息传送的方法的另一流程图;
图6为本公开的一些实施例提供的信息传送的方法的另一流程图;
图7为本公开具体实施例的场景1中信息传送过程的流程图;
图8为本公开具体实施例的场景2中信息传送过程的流程图;
图9为本公开具体实施例的场景3中UE请求注册过程的流程图;
图10为本公开具体实施例的场景4中UE请求注册过程的流程图;
图11为本公开提供的通信设备的结构图;
图12为本公开提供的通信设备的另一结构图;
图13为本公开提供的通信设备的另一结构图;
图14为本公开提供的通信设备的另一结构图;
图15为本公开提供的通信设备的另一结构图;以及
图16为本公开提供的通信设备的另一结构图。
下面将结合本公开实施例中的附图,对本公开实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例是本公开一部分实施例,而不是全部的实施例。基于本公开中的实施例,本领域普通技术人员在没有作出创 造性劳动前提下所获得的所有其他实施例,都属于本公开保护的范围。
本申请的说明书和权利要求书中的术语“包括”以及它的任何变形,意图在于覆盖不排他的包含,例如,包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元,而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。此外,说明书以及权利要求中使用“和/或”表示所连接对象的至少其中之一,例如A和/或B,表示包含单独A,单独B,以及A和B都存在三种情况。
在本公开的一些实施例中,“示例性的”或者“例如”等词用于表示作例子、例证或说明。本公开的一些实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言,使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本文所描述的技术不限于第五代移动通信(5th-generation,5G)系统以及后续演进通信系统,以及不限于LTE/LTE的演进(LTE-Advanced,LTE-A)系统,并且也可用于各种无线通信系统,诸如码分多址(Code Division Multiple Access,CDMA)、时分多址(Time Division Multiple Access,TDMA)、频分多址(Frequency Division Multiple Access,FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access,OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access,SC-FDMA)和其他系统。
术语“系统”和“网络”常被可互换地使用。CDMA系统可实现诸如CDMA2000、通用地面无线电接入(Universal Terrestrial Radio Access,UTRA)等无线电技术。UTRA包括宽带CDMA(Wideband Code Division Multiple Access,WCDMA)和其他CDMA变体。TDMA系统可实现诸如全球移动通信系统(Global System for Mobile Communication,GSM)之类的无线电技术。OFDMA系统可实现诸如超移动宽带(Ultra Mobile Broadband,UMB)、演进型UTRA((Evolution-UTRA,E-UTRA))、IEEE 802.11((Wi-Fi))、IEEE 802.16((WiMAX))、IEEE 802.20、Flash-OFDM等无线电技术。UTRA和E-UTRA是通用移动电信系统(Universal Mobile Telecommunications System,UMTS)的部分。LTE和更高级的LTE(如LTE-A)是使用E-UTRA的新UMTS版本。UTRA、E-UTRA、UMTS、LTE、LTE-A以及GSM在来自名为“第三代伙伴项目”(3rd Generation Partnership Project,3GPP)的组织的文献中描述。CDMA2000和UMB在来自名为“第三代伙伴项目2”(3GPP2)的组织的文献中描述。本文所描述的技术既可用于以上提及的系统和无线电技术,也可用于其他系统和无线电技术。
为了便于更好地理解本公开实施例,下面先介绍以下技术点。
多卡终端是一个设备上具有两个或大于两个的SIM卡。所述SIM卡是电子SIM卡或实体SIM卡。从网络的角度,同一终端设备与不同的SIM卡构成不同的UE。
多卡终端的能力可以是单发双收、单发单收和双发双收。对于单发单收的终端设备,由于终端设备的多UE无法同时工作,所以存在问题最多。单发单收的主要问题包括:(1)同一终端设备上UE1和UE2之间可能存在寻呼冲突,一旦发生寻呼冲突,将无法收听对其中一个UE的寻呼;(2)UE1进行语音业务时,由于语音业务数据间隔为20ms,因此没有空隙取听对UE2的寻呼;(3)UE1和UE2都处于连接态时,如果终端设备驻留在UE1一侧的网络,则关于UE2的数据会丢失,如果关于UE2的数据是关于语音被叫信令,则会发生掉话。
对于单发双收终端设备,虽然没有寻呼的问题,但同时收到关于UE1和UE2的寻呼时,无法同时响应两个寻呼。UE1和UE2都处于连接态时,终端设备只能在一侧发送数据。
对于双发双收的终端设备,虽然可以UE1和UE2同时收发数据,但是要求网络为UE1和UE2配置的频段(band)要属于一个频段组合(band combination)。
因此为了优化多卡终端的用户体验,还要解决如下问题:
问题1:同一运营商中的寻呼冲突。或者,如果一侧是连接态且进行语音时,另一侧是空闲态,UE无法监听另一侧的网络的寻呼。如何解决还不清楚。对于同一个运营商的多卡终端。
问题2:不同终端能力需要的多卡优化不同。但网络还不确认UE的能力。 不同的多个终端的能力不同,如单发单收,单发双收,双发双收等。不同能力需要解决的双卡问题不同,网络不知道多卡终端的能力类型,需要进行哪方面的优化。
问题3:即使终端设备具有多个卡槽或者具有配置多个卡的能力,但不一定配置了多个卡。网络也不知道终端是否为多卡终端,是否需要进行优化。
参考图1,为本公开的一些实施例提供的无线通信系统的架构示意图。如图1所示,一个设备上配置有第一UE和第二UE,第二UE可以是一个或多个不同于第一UE的UE。第一UE连接第一RAN网元、驻留在第一RAN网元下的小区,或者第一RAN网元保存着第一UE的上下文。第二UE连接第二RAN网元、驻留在第二RAN网元下的小区,或者第二RAN网元保存着第二UE的上下文。
第一UE注册第一核心网(CN)。第二UE注册第二CN。第一CN与第二CN可以是同一个CN。第一UE注册第一CN网元。第二UE注册第二CN网元。第一CN网元与第二CN可以是同一个CN网元。第一CN网元和第二CN网元可以属于同一个CN或分别属于不同的CN。
第一UE和第二UE所在的无线通信网络可以相同,也可以不相同。
可选的,获取可以理解为从配置获得、接收、通过请求后接收、通过自学习获取、根据未收到的信息推导获取或者是根据接收的信息处理后获得,具体可根据实际需要确定,本公开的一些实施例对此不作限定。比如当未收到设备发送的某个能力指示信息时可推导出该设备不支持该能力。
可选的,发送可以包含广播,系统消息中广播,响应请求后返回。
在本公开一种可选实施例中,所述通道可以包括以下至少一项:PDU会话、服务质量(Quality of Service,QoS)流、演进的分组系统(Evolved Packet System,EPS)承载、PDP上下文、DRB、SRB、网络安全协议(Internet Protocol Security,IPsec)关联。
本公开一种实施例中,NG接口也可以称为S1接口或N2接口,命名不受限制。
本公开一种实施例中,无线通信网络可以是以下至少一项:公网,非公网;或者第一网络可以是非公网。
在本公开一种实施例中,非公网是非公众网络的简称。非公众网络可以称为以下之一:非公众通信网络。非公网可以包括以下至少一种部署方式:物理的非公网,虚拟的非公网、实现在公网上的非公网。一种实施方式中,非公网为封闭的访问组(Closed Access Group,CAG)。一个CAG可以由一组终端组成。
在本公开一种实施例中,非公众网络可以包含或称为私有网络。私有网络可以称为以下之一:私有通信网络、私网、本地区域网络(LAN)、私有虚拟网络(PVN)、隔离的通信网络、专用的通信网络或其他命名。需要说明的是,在本公开的一些实施例中对于命名方式不做具体限定。
在本公开一种实施例中,公网是公众网络的简称。公众网络可以称为以下之一:公众通信网络或其他命名。需要说明的是,在本公开的一些实施例中对于命名方式不做具体限定。
本公开一种可选实施例中,通信设备可以包括以下至少一项:通信网元和终端。
本公开一种实施例中,通信网元可以包括以下至少一项:核心网网元和无线接入网网元。
本公开的一些实施例中,核心网网元(CN网元)可以包含但不限于如下至少一项:核心网设备、核心网节点、核心网功能、核心网网元、移动管理实体(Mobility Management Entity,MME)、接入移动管理功能(Access Management Function,AMF)、会话管理功能(Session Management Function,SMF)、用户平面功能(User Plane Function,UPF)、服务网关(serving GW,SGW)、PDN网关(PDN Gate Way,PDN网关)、策略控制功能(Policy Control Function、PCF)、策略与计费规则功能单元(Policy and Charging Rules Function,PCRF)、GPRS服务支持节点(Serving GPRS Support Node,SGSN)、网关GPRS支持节点(Gateway GPRS Support Node,GGSN)、应用功能(Application Funcation)。
本公开的一些实施例中,RAN网元可以包含但不限于至少以下之一:无线接入网设备、无线接入网节点、无线接入网功能、无线接入网单元、3GPP无线接入网、非3GPP无线接入网、集中单元(Centralized Unit,CU)、分布 式单元(Distributed Unit,DU)、基站、演进型基站(evolved Node B,eNB)、5G基站(gNB)、无线网络控制器(Radio Network Controller,RNC)、基站(NodeB)、非3GPP互操作功能(Non-3GPP Inter Working Function,N3IWF)、接入控制(Access Controller,AC)节点、接入点(Access Point,AP)设备或无线局域网(Wireless Local Area Networks,WLAN)节点、N3IWF。
基站,可以是GSM或CDMA中的基站(BTS,Base Transceiver Station),也可以是WCDMA中的基站(NodeB),还可以是LTE中的演进型基站(eNB或e-NodeB,evolutional Node B)及5G基站(gNB),本公开的一些实施例并不限定。
本公开一种可选的实施例中,UE可以包括以下至少一项:签约主体(subscription,或Subscriber)、SIM卡、SIM卡对应的签约主体、SIM卡所关联的UE、终端设备、终端设备和签约主体、终端设备和SIM卡。
一种可选实施方式中,UE即签约主体。一个终端设备上可以配置有多个签约主体。签约主体可以通过SIM(Subscriber Identity Module)卡体现。一个SIM卡对应一个网络的签约主体。SIM卡中保存着签约主体的标识,即UE的标识,比如SUPI(Subscription Permanent Identifier),或IMSI(International Mobile Subscription Identity)等。所以一个终端设备上插入多个SIM卡或配置多个电子SIM卡信息时,终端设备与不同的签约主体可以构成不同的UE。
另一种实施方式中,UE即终端设备和签约主体构成的终端。
另一种实施方式中,UE即终端设备。
另一种实施方式中,UE即SIM卡或SIM卡对应的签约主体。
另一种实施方式中,UE即SIM卡对应的UE。
另一种实施方式中,UE即SIM卡。
另一种实施方式中,UE即终端设备和SIM卡构成的终端。当一个终端设备上具有多张SIM卡时,终端设备可以与每个卡构成多个逻辑终端。所述SIM卡可以是置于终端设备卡槽中的卡,或者是终端设备中的电子卡。
本公开一种可选的实施例中,SIM卡可以包括以下之一:SIM卡、全球用户识别卡(Universal SIM,USIM卡)、嵌入式SIM卡(Embeded SIM,eSIM)。SIM卡也可以做为别的命名,本公开不做限制。
本公开一种可选的实施例中,第一设备可以称为终端设备。
本公开一种可选的实施例中,第一UE的第一设备,即第一UE所在的终端设备。
本公开一种可选实施例中,第一设备可以称为终端设备。
本公开一种可选实施例中,本公开中的设备可以称为终端设备。
本公开一种可选的实施例中,UE的标识信息包括以下至少一项:UE标识,UE的临时标识。
UE标识包括以下至少一项:国际移动用户识别码(International Mobile Subscriber Identification Number,IMSI)、网络接入标识(Network Access Identifier,NAI)、SUPI(Subscription permanent identifier)、SUCI(Subscription Concealed Identifier)。
一种实施方式中,所述临时UE标识可以包括以下至少一项:5G全球唯一临时UE标识(5G Globally Unique Temporary UE Identity,5G GUTI)、GUTI(Globally Unique Temporary UE Identity)、S-TMSI、ng-S-TMSI、5G TMSI、TMSI。5G GUTI,GUTI、5G-S-TMSI、ng-S-TMSI中可以包含CN网元的标识信息和UE在CN网元中的标识信息。5G TMSI、TMSI可以是UE在CN网元中的标识信息。
本公开一种可选的实施例中,终端可以包括支持终端功能的中继和/或支持中继功能的终端。终端也可以称作终端设备或者用户终端(User Equipment,UE),终端可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、个人数字助理(Personal Digital Assistant,PDA)、移动上网装置(Mobile Internet Device,MID)、可穿戴式设备(Wearable Device)或车载设备等终端侧设备,需要说明的是,在本公开的一些实施例中并不限定终端的具体类型。
以下对本公开的一些实施例的信息传送的方法进行说明。
请参考图2,本公开的一些实施例提供了信息传送的方法,应用于第一通信设备。第一通信设备可以是但不限于第一CN网元(如MME或AMF),如图2所示,所述方法包括:
步骤21:判断是否满足第一条件。
步骤22:确定满足第一条件时,向第一UE发送第二UE的第一信息,和/或目标UE信息。
可选地,在判断是否满足第一条件的步骤之前,所述方法还可包括:
获取第三信息。所述第三信息如图5实施例所述,此处不再赘述。
一种实施方式中,所述目标UE可以为等待被发送的信令和/或数据的目标端。等待被发送的信令和/或数据表示网络具有等待发送给目标UE的信令和/或数据。信令和/或数据。目标UE可以是第一UE或第二UE。
可选地,所述目标UE信息可以包括以下至少一项:UE的标识信息、UE的类型信息。
一种实施方式中,UE的类型信息包括以下至少一项:第一UE、第二UE。当UE的类型信息为第一UE时,表示等待被发送的信令和/或数据的目标端为第一UE。当UE的类型信息为第二UE时,表示等待被发送的信令和/或数据的目标端为第二UE。第一UE收到UE的类型信息为第二UE时,可以通知第二UE建立或恢复与网络的连接。第二UE建立或恢复与网络的连接后,则可以接收所述信令和/或数据。
另一种实施方式中,UE的类型信息包括以下至少一项:当前UE、其他UE。所述其他UE为当前UE所在设备上的其他UE。
一种实施方式中,所述第二UE可以为网络具有信令和/或数据等待发送给的UE且第二UE不同于第一UE。
可选地,所述第二UE的第一信息可以包括以下至少一项:
第二UE的UE标识信息(比如第二UE的UE标识,和/或第二UE的临时UE标识);
第二UE的信息容器;
关于第二UE的连接请求信息;
触发第二UE的连接请求的业务信息;
等待发送给第二UE的信令和/或数据的信息。
(1)进一步地,UE的标识信息可以包括以下至少一项:UE标识,UE的临时标识。
一种实施方式中,所述UE标识可以包括以下至少一项:国际移动用户 识别码(International Mobile Subscriber Identification Number,IMSI)、网络接入标识(Network Access Identifier,NAI)、SUPI(Subscription permanent identifier)、SUCI(Subscription Concealed Identifier)。
一种实施方式中,所述临时UE标识可以包括以下至少一项:5G全球唯一临时UE标识(5G Globally Unique Temporary UE Identity,5G GUTI)、GUTI(Globally Unique Temporary UE Identity)、S-TMSI、ng-S-TMSI、5G TMSI、TMSI。5G GUTI,GUTI、5G-S-TMSI、ng-S-TMSI中可以包含CN网元的标识信息和UE在CN网元中的标识信息。5G TMSI、TMSI可以是UE在CN网元中的标识信息。
(2)进一步地,所述第二UE的信息容器用于传送第二UE的相关信息。第二UE的相关信息可以为第二UE相关的信令和/或第二UE相关的数据。一种实施方式中,第二UE的信息容器可以对第二UE可见,对第一UE透明。不难理解,这样可以减少第一UE的实现复杂度。
(3)进一步地,所述连接请求信息用于请求第二UE与网络建立或恢复连接。关于第二UE的连接请求信息可以称为关于第二UE的寻呼请求信息。
进一步地,关于第二UE的连接请求信息可以包括以下至少一项:
连接请求的原因,
连接请求的指示信息。
其中,所述连接请求的原因可以称为寻呼的原因。所述连接请求的指示信息可以称为寻呼的指示信息。
其中,所述连接请求的原因可以是触发寻呼第二UE或请求第二UE进行连接建立或连接恢复的业务的信息,和/或等待发送给第二UE的数据的信息。所述连接请求的原因可以包括以下至少一项:语音业务(如IMS语音被叫)、重要业务(如mission critical业务)、数据业务、重要业务的信令、语音信令(如IMS语音被叫)、NAS信令、用户面数据(如通道的数据,所述通道比如为QoS流、承载)等。
不难理解,第二UE处于空闲态或非活跃态时,可以通过发送关于第二UE的连接请求信息请求第二UE恢复或建立连接。
(4)进一步地,触发第二UE的连接请求的业务信息可以包括以下至少 一项:语音业务(如IMS语音被叫)、重要业务(如mission critical业务)、数据业务。
(5)进一步地,等待发送给第二UE的信令和/或数据的信息可以包括以下至少一项:重要业务的信令(如mission critical业务)、语音信令(如IMS语音被叫)、NAS信令、用户面数据(如通道的数据,所述通道比如为QoS流、承载)等。
进一步地,第一UE与第二UE存在关联关系。所述第二UE与第一UE存在关联关系可以理解为第一UE和第二UE位于同一设备(比如第一设备)上。不难理解,当第一UE和第二UE都处于连接态时,当单收能力的第一设备驻留在第一UE侧时,可以通过第一UE发送关于第二UE的业务和/或数据请求信息,辅助第一设备决定是否切换到第二UE侧。
进一步地,所述向第一UE发送第二UE的第一信息可以包括:
向第一UE发送通知消息或寻呼消息,且所述通知消息或寻呼消息中包含第二UE的第一信息和/或目标UE的信息。
一种实施方式中,所述通知消息可以为NAS信令,在第一UE处于连接态时,发送给第一UE。
一种实施方式中,所述寻呼消息是第一UE处于空闲态或非活跃态时,发送给第一UE。
可选的,所述满足第一条件可以包括以下至少一项:
第一UE、第二UE和/或第一设备的能力为单收;一种实施方式中,第一UE的能力、第二UE的能力以及第一设备的能力可以理解为是一样的;
第二UE处于空闲态或非活跃态;
具有下行信令和/或用户数据等待发送给所述第二UE;
第一UE处于连接态;
第一UE与第二UE存在关联;
第一UE与第二UE存在寻呼冲突;
第一UE正在进行语音业务;
第一UE正在进行使第一设备无法监听第二UE的寻呼的业务,且所述第一设备为第一UE和第二UE所在的设备;
从第二CN网元接收到第二UE的第二信息。
一种实施方式中,第一UE与第二UE存在关联可以理解为第一UE与第二UE位于同一设备(比如第一设备)上。一种实施方式中,第一UE和第二UE分别为同一设备上不同SIM卡对应的UE;另一种实施方式中,第一UE和第二UE为同一设备上不同卡槽对应的UE。
(1)一种实施方式中,满足第一条件为:第一UE、第二UE和/或第一设备的能力为单收(单收包含单发单收),且第一UE与第二UE存在寻呼冲突。
一种实施方式中,第一UE与第二UE存在寻呼冲突为,第一UE的UE标识mod N的取值与第二UE的UE标识mod N的取值相同或者通过第一UE的UE标识计算的寻呼帧和通过第二UE的UE标识计算的寻呼帧相同。N可以但不限于1024。UE的标识可以为IMSI。UE标识mod N是计算寻呼时机(Paging Occassion)的参数之一。不难理解,当UE标识mod N相同时,寻呼时机相同,而第一设备是单收能力的设备,因此无法在相同的寻呼时机监听第一UE和第二UE的寻呼。
(2)一种实施方式中,满足第一条件为:第一UE正在进行语音业务,且第二UE处于空闲态或非活跃态。由于语音业务的数据包间隔为20ms,第一设备无法在20ms的时间内转去监听第二UE的寻呼。不难理解,当第一UE进行语音业务时,关于第二UE的寻呼会丢失。
一种实施方式中,第一CN网元同时服务第一UE和第二UE。另一种实施方式中,第一CN网元可以为服务第一UE的CN网元;第二CN网元可以为服务第二UE的CN网元。
(3)一种实施方式中,满足第一条件为:从第二CN网元接收到关于第二UE的寻呼请求信息。不难理解,当第一UE和第二UE的服务CN网元不同时,若要通过第一UE寻呼第二UE,需要通过其各自服务的CN网元间进行协商。
(4)一种实施方式中,满足第一条件为:第二UE处于空闲态或非活跃态(如RRC非活跃态),且第一UE处于连接态。不难理解,第二UE处于空闲态或非活跃态时,如果要寻呼第二UE,需要寻呼整个RA,耗费较多的无 线资源,而第一UE处于连接态,其位置是确定的,将关于第二UE的寻呼转化为一个第一UE的NAS层数据包发送给第一UE,则可以节约无线资源。
通过本公开的一些实施例,可以向第一UE发送关于第二UE的信息,从而可以解决多卡终端的问题,提升多卡终端的性能,从而提高用户对多卡终端的使用体验。
请参考图3,本公开的一些实施例提供了信息传送的方法,应用于第二通信设备。第二通信设备可以是但不限于第二CN网元,所述方法包括:
步骤31:判断是否满足第二条件。
步骤32:确定满足第二条件时,执行第二操作。
可选地,在判断是否满足第二条件步骤之前,获取第三信息。所述第三信息如图5实施例所述,此处不再赘述。
所述第二操作包括以下至少一项:
向第一CN网元请求通过第一UE发送第二UE的第二信息;
向第二UE发送寻呼消息;
向第二UE的RAN网元发送第二UE的相关信息。
一种实施方式中,所述寻呼消息可以为一条信令,当第二UE处于空闲态或非活跃态时向其发送。对RRC非活跃态的UE,当第二通信设备为第二CN网元时,将第二UE的相关信息发送给RAN网元。RAN网元再向第二UE发送寻呼消息。不难理解,第二CN网元可以一方面向第二UE发送寻呼或通过第二UE的RAN网元发送寻呼,另一方面请求第一CN网元通过第一UE发送第二UE的第二信息,可以达到解决冲突,提高成功率的目的。
可选地,所述第二UE的第二信息可以包括以下至少一项:
第二UE关联的第一UE的UE标识信息(比如第一UE的UE标识,或第一UE的临时UE标识);
第二UE的UE标识信息(比如第二UE的UE标识,或第二UE的临时UE标识);
第二UE的信息容器;
关于第二UE的连接请求信息;
触发第二UE的连接请求的业务信息;
等待发送给第二UE的信令和/或数据的信息。
进一步地,第二UE的UE标识信息,和第一UE的UE标识信息可以如图2实施例所述,此处不再赘述。
进一步地,触发第二UE的连接请求的业务信息如图2实施例所述,此处不再赘述。
进一步地,等待发送给第二UE的信令和/或数据的信息如图2实施例所述,此处不再赘述。
进一步地,所述第二UE的信息容器可以用于传送第二UE的相关信息。第二UE的相关信息可以为第二UE相关的信令和/或第二UE相关的数据。一种实施方式中,第二UE的信息容器可以对第二UE可见,对第一UE透明。
其中,所述第二UE的信令包括但不限于以下至少一项:第二UE的NAS信令、第二UE的IMS信令。第二UE的IMS信令可以表现为第二UE的数据,比如QCI或5QI=5的通道的数据。
一种实施方式中,第二UE关联的第一UE的UE标识信息发送给第一CN网元;第一CN网元可以根据第一UE的UE标识信息找到第一UE。另一种实施方式中,第一CN网元可以根据第一UE与第二UE的关联关和第二UE的UE标识信息找到第一UE。
(1)一种实施方式中,所述第二操作包括:向第二UE发送寻呼消息,且向第一CN网元请求通过第一UE发送第二UE相关的连接请求信息(如图2实施例所述)。不难理解,同时向第二UE和通过第一UE发送关于第二UE的连接请求信息,可以提高成功率。
(2)一种实施方式中,所述第二操作包括:向第二UE发送第二UE的相关信息,且向第一CN网元请求通过第一UE发送第二UE的信息容器。不难理解,当第一UE、第二UE和/或第一设备的能力是单收时,如果第一UE和第二UE同时处于连接态,网络无法确认第一设备当前监听的网络。如果第二UE的相关信息是一个重要的信令或重要的数据,比如语音被叫,则可以同时向第二UE和通过第一UE发送第二UE的相关信息,避免丢失提高成功率。
(3)一种实施方式中,所述第二操作包括:向第二UE发送第二UE的 相关信息,且向第一CN网元请求通过第一UE发送关于第二UE的寻呼请求信息。比如当收到一个语音信令相关的QoS流数据时,为了避免数据丢失,向第一UE请求发送一个业务指示,表示有语音到达。当第二UE和第一UE都处于连接态,但第一UE、第二UE和/或第一设备的能力为单收时,可以避免语音被叫信令丢失。
一种实施方式中,第一CN网元可以为服务第一UE的CN网元;第二CN网元可以为服务第二UE的CN网元。
可选的,所述满足第二条件可以包括以下至少一项:
向第二UE发送寻呼消息后,没有收到第二UE的响应;
向第二UE发送通知消息后,没有收到第二UE的响应;
第一UE、第二UE和/或第一设备的能力为单收;
第二UE处于空闲态或非活跃态;
具有信令和/或数据等待发送给所述第二UE;
第一UE与第二UE存在关联;
第一UE与第二UE存在寻呼冲突;
第一UE正在进行语音业务;
第一UE正在进行使第一设备无法监听第二UE的寻呼的业务,且所述第一设备为第一UE和第二UE所在的设备。
通过本公开的一些实施例,可以向第一UE发送关于第二UE的信息,从而可以解决多卡终端的问题,提升多卡终端的性能,从而提高用户对多卡终端的使用体验。
请参考图4,本公开的一些实施例提供了一种信息传送的方法,应用于第三通信设备。第三通信设备可以是但不限于以下至少一项:终端、第一设备、UE(如第一UE、和/或第二UE),如图4所示,所述方法包括:
步骤41:接收第二UE的第一信息和/或目标UE信息;
步骤42:根据所述第二UE的第一信息和/或目标UE信息,执行第三操作。
其中,所述第三操作包括以下至少一项:
向第二UE发送第二UE的第一信息
请求建立或恢复第二UE与网络间连接。
具体地,第二UE的第一信息如图2实施例子所述,此处不再赘述。
通过本公开的一些实施例,可以通过第一UE发送关于第二UE的信息、请求建立或恢复第二UE与网络间连接,从而可以解决多卡终端的问题,提升多卡终端的性能,从而提高用户对多卡终端的使用体验。
请参考图5,本公开的一些实施例提供了一种信息传送的方法,应用于第四通信设备。第四通信设备可以是但不限于以下至少一项:终端、第一设备、UE(如第一UE、和/或第二UE),如图5所示,所述方法包括:
步骤51:发送第三信息。
其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数量、第一设备是否支持多卡的指示信息、第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息。
(1)进一步地,所述第一能力信息包括以下至少一项:单发单收、单发双收、双发双收、单收、单发、双发、双发、多收、多发。
一种实施方式中,第一能力信息是第一UE、第二UE和/或第一设备的能力。
所述第一设备可以为第一UE所在的设备,或者所述第一设备可以为第一UE和第二UE共同所在的设备。不难理解,比如终端设备上有两个卡槽,第一卡槽插入第一SIM卡,第一SIM卡对应第一UE。第二卡槽没有插入SIM卡。则所述终端设备为第一UE所在的设备。第一卡槽插入第一SIM卡且第二卡槽插入第二SIM卡。第一SIM卡对应第一UE,第一SIM卡对应第二UE。则所述终端设备为第一UE和第二UE共同所在的设备。第二UE可以是多个。
进一步地,确定满足第一条件时,UE发送第一能力信息。
可选地,所述满足第一条件可以包括以下至少一项:
被网络配置双连接或载波聚合;
第一终端能力发生更新;
接入网络时。
不难理解,当被网络配置为双连接或载波聚合时,从双发双收回退到单发单收,此时第一终端能力更新,需要通知网络。不难理解,不同的第一能力信息需要的多卡优化不同。
(2)第一设备上的UE数量信息可以为,第一设备上当前的UE数量。第一设备上的UE数量可以理解为第一设备上的卡数量。
(3)第一设备上的卡数量信息可以为,第一设备上当前的卡数量。一种实施方式中,第一设备的卡数量可以包括以下至少一项:单卡、双卡、多卡。
(4)是否请求多卡优化的指示信息。进一步地,满足第三条件时,所述是否请求多卡优化的指示信息设置为:请求多卡优化。
可选地,满足第三条件可以包括以下至少一项:
第一设备支持的卡槽数量或第一设备支持的卡数量大于或等于2;
第一设备上的UE数量信息或第一设备上的卡数量信息大于或等于2;
第一设备支持多卡或第一设备支持多UE;
第一设备为多UE状态;
第一设备为多卡状态。
不难理解,不具有多卡能力的设备不需要进行多卡优化。对具有多卡能力的设备但设备的卡数量为单卡时,也不需要进行多卡优化的操作。
不难理解,只有具有多卡能力且具有多个卡的设备,才需要进行多卡优化。
不难理解,设备上的卡数量大于等于2即设备为多卡状态。设备上的UE数量大于等于2即设备为多UE状态。设备为多UE状态可以理解为第一UE存在关联的第二UE。
通过本公开的一些实施例,可以向第一UE发送关于第二UE的信息,从而可以解决多卡终端的问题,提升多卡终端的性能,从而提高用户对多卡终端的使用体验。
请参考图6,本公开的一些实施例提供了一种信息传送的方法,应用于第五通信设备。第五通信设备可以是但不限于以下至少一项:RAN网元、CN网元,如图6所示,所述方法包括:
步骤61:接收第三信息。
其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数量、第一设备是否支持多卡的指示信息、第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息。
具体地,所述第三信息如图5实施例所述,此处不再赘述。
步骤62:根据所述第三信息,执行第五相关操作。
其中,所述第五相关操作可以包括以下至少一项:
确定是否执行多卡优化的操作;
确定多卡优化操作的类型;
执行多卡优化的操作。
不难理解,不同的第一能力信息需要的多卡优化操作不同。
当满足第四条件时,确定执行多卡优化的操作。
可选地,所述满足第四条件可以包括以下至少一项:
第一设备支持的卡槽数量或第一设备支持的卡数量大于或等于2;
第一设备上的UE数量信息或第一设备上的卡数量信息大于或等于2;
第一设备支持多卡或第一设备支持多UE;
第一设备为多UE状态;
第一设备为多卡状态;是否请求多卡优化的指示信息指示请求多卡优化。
一种实施方式中,当第五通信设备是CN网元时,向RAN网元转发接收到的第三信息;
一种实施方式中,当第五通信设备是RAN网元时,向CN网元转发接收到的第三信息;
不难理解,对具有多卡能力的设备,但设备的卡数量为单卡时,不需要进行多卡优化的操作。
一种实施方式中,执行多卡优化的操作可以包括以下至少一项:
获取设备标识信息;
向第一UE发送第二UE的第一信息;
通过第一UE发送第二UE的连接请求信息;
判断第一UE和第二UE是否存在寻呼冲突。
可选的,设备标识信息可以包括以下至少一项:第一终端设备标识、第二终端设备标识。
(1)一种实施方式中,第一终端设备标识可以为第一UE的终端设备标识。第二终端设备标识可以为第一UE关联的终端设备标识,比如第一UE所在的设备上其他终端设备标识。不难理解,一个终端设备上每个卡槽可以配置一个终端设备标识。当卡槽插入SIM卡时,所述SIM卡对应的UE的终端设备标识是所述卡槽的终端设备标识。所述终端设备其他卡槽对应的终端设备标识可以是所述SIM卡对应的UE关联的终端设备标识。
(2)另一种实施方式中,第一终端设备标识可以为第一UE的终端设备标识。第二终端设备标识可以为第二UE的终端设备标识。第一UE可以有关联的终端设备标识但没有关联的第二UE。不难理解,比如终端设备上有两个卡槽,第一卡槽插入第一SIM卡,第一SIM卡对应第一UE。第二卡槽没有插入SIM卡。第二卡槽对应的终端设备标识就没有对应的UE。则第一UE存在关联的终端的终端设备标识,但不存在关联的第二UE。
(3)另一种实施方式中,所述设备标识信息为第一设备的设备标识信息。第一终端设备标识和/或第二终端设备标识为第一设备的第一终端设备标识和/或第二终端设备标识。所述第一设备可以为第一UE所在的设备,或者所述第一设备可以为第一UE和第二UE共同所在的设备。
进一步地,终端设备标识可以包括以下至少一项:IMEI(International Mobile Equipment Identities)、IMEISV(International Mobile station Equipment Identity and Software Version number)、PEI(Permanent Equipment Identifier)。比如,第一终端设备标识为第一IMEI;第二终端设备标识为第二IMEI。
所述第一设备可以为第一UE所在的设备,或者所述第一设备可以为第一UE和第二UE共同所在的设备。不难理解,比如终端设备上有两个卡槽,第一卡槽插入第一SIM卡,第一SIM卡对应第一UE。第二卡槽没有插入SIM卡。则所述终端设备为第一UE所在的设备。第一卡槽插入第一SIM卡且第二卡槽插入第二SIM卡。第一SIM卡对应第一UE,第一SIM卡对应第二 UE。则所述终端设备为第一UE和第二UE共同所在的设备。第二UE可以是多个。
可选的,所述设备标识信息可以包括以下至少一项:第一终端设备标识、第二终端设备标识。
可选的,RAN网元可以包括以下至少一项:第一RAN网元、第二RAN网元。第一RAN网元可以为服务第一UE的RAN网元;第二RAN网元可以为服务第二UE的RAN网元。第一RAN网元与第二RAN网元可以相同或者不同。
可选的,CN网元可以包括以下至少一项:第一CN网元、第二CN网元。第一CN网元可以为服务第一UE的CN网元;第二CN网元可以为服务第二UE的CN网元。第一CN网元与第二CN网元可以相同或者不同。
一种实施方式中,第一UE和第二UE是同一设备上的UE。
通过本公开的一些实施例,可以向第一UE发送关于第二UE的信息,从而可以解决多卡终端的问题,提升多卡终端的性能,从而提高用户对多卡终端的使用体验。
下面结合图7至图10的具体应用场景对本公开的一些实施例的信息传送的方法进行说明。
本公开的一些实施例的应用场景1:
本公开的一些实施例的应用场景1主要描述第一UE和第二UE的服务CN网元都是第一CN网元;第一CN网元向第一UE发送第二UE的第一信息的过程。请参阅图7所示,包括以下步骤:
步骤71:第二UE处于空闲态,第一CN网元需要寻呼第二UE。
当满足第一条件时,第一CN网元向第一UE发送通知消息(notification),所述通知消息包含第二UE的第一信息。第二UE的第一信息如图2实施例所述,在此不再赘述。
可选的,第一条件可以包括以下至少一项:
第一UE、第二UE和/或第一设备的能力为单收;
第一UE处于连接态;
第一UE与第二UE存在关联。
步骤72:第一UE将接收到的第二UE的第一信息发送给第二UE
步骤73:第二UE向RAN网元发送RRC建立请求消息或RRC恢复请求消息;
步骤74:RAN网元向第二UE发送RRC建立消息或RRC恢复消息;
步骤75:第二UE向RAN网元发送RRC建立完成消息或RRC恢复完成消息;
步骤76:RAN网元向第一CN网元发送初始UE消息或通知响应消息。即通过步骤73至步骤76,第二UE建立或恢复连接。
本公开的一些实施例的应用场景2:
本公开的一些实施例的应用场景2主要描述第一UE和第二UE的服务CN网元分别为第一CN网元和第二CN网元;第二CN网元向第一CN网元发送第二UE的第二信息,第一CN网元向第一UE发送第二UE的第一信息的过程。请参阅图8所示,包括以下步骤:
步骤81:第二UE处于空闲态,第二CN网元需要寻呼第二UE。
当满足第二条件时,第二CN网元向UDM查询第一UE的CN网元(即第一CN网元)的信息,第一UE是第二UE关联的UE。
步骤82:第二CN网元向第一CN网元发送第二UE的第二信息(如图3实施例所述,比如可通过寻呼请求消息发送所述第二UE的第二信息)。
步骤83:第一CN网元向第一UE发送通知消息(notification),所述通知消息包含第二UE的第一信息。第二UE的第一信息如图2实施例所述。
可选的,当满足第一条件时,第一CN网元向第一UE发送通知消息(notification),所述通知消息包含第二UE的第一信息。
可选的,第一条件可以包括以下至少一项:
第一UE、第二UE和/或第一设备的能力为单收;
第一UE处于连接态;
第一UE与第二UE存在关联。
步骤84:第一UE将接收到的第二UE的第一信息发送给第二UE
步骤85:第二UE向RAN网元发送RRC建立请求消息或RRC恢复请求消息;
步骤86:RAN网元向第二UE发送RRC建立消息或RRC恢复消息;
步骤87:第二UE向RAN网元发送RRC建立完成消息或RRC恢复完成消息;
步骤88:RAN网元向第一CN网元发送初始UE消息或通知响应消息。即通过步骤85至步骤88,第二UE建立或恢复连接。
本公开的一些实施例的应用场景3:
本公开的一些实施例的应用场景3以第一UE为例,主要描述UE请求注册的过程。请参阅图9所示,包括以下步骤:
步骤91:第一UE向第一CN网元(以下以AMF为例进行描述)发送注册请求消息,所述注册请求消息包括第三信息(具体如图5实施例所述)。
根据所述第三信息,AMF确定是否执行多卡优化的操作和/或确定多卡优化操作的类型(具体如图6实施例所述)。
步骤92:AMF注册终端到统一数据管理(Unified Data Manager,UDM)。在注册请求中包含第一信息。
AMF还可以获取、订购终端的签约数据。
步骤93:AMF与PCF关于UE的策略关联建立。AMF可以从PCF获取终端的策略。
步骤94:AMF向RAN网元发送第三信息(具体如图5实施例所述)。
根据所述第三信息,RAN网元确定是否执行多卡优化的操作和/或确定多卡优化操作的类型(具体如图6实施例所述)。
AMF向终端返回注册响应消息。
具体地,AMF向RAN网元发送初始上下文建立请求消息。所述初始上下文建立请求消息中包含所述第三信息。
步骤95:第一UE向AMF返回注册完成消息。
通过本公开的一些实施例,在第一UE注册过程中,第一UE向网络提供第三信息。网络可以根据所述第三信息,确定是否执行多卡优化的操作和/或确定多卡优化操作的类型。从而可以支持多卡优化的操作。
本公开的一些实施例的应用场景4:
本公开的一些实施例的应用场景4以第一UE为例,主要描述UE发起注 册请求后,网络向UE获取UE的终端设备标识的过程。请参阅图10所示,包括以下步骤:
步骤101:第一UE向第一CN网元(以下以AMF为例进行描述)发送注册请求消息,所述注册请求消息包括第三信息(具体如图5实施例所述)。
根据所述第三信息,AMF确定获取第一UE的设备标识(具体如图6实施例所述),则进入步骤102,否则进入步骤104。
步骤102:AMF向UE发送标识请求消息。所述标识请求消息中包含请求的标识类型。所述标识类型包括以下至少一项:终端设备标识(如IMEI,或IMEISV)、第一终端设备标识、第二终端设备标识、第一终端设备标识和第二终端设备标识、第一设备的所有的终端设备标识。第一设备为第一UE所在的设备。
步骤103:UE向AMF发送设备标识信息。设备标识信息包括以下至少一项:第一终端设备标识、第二终端设备标识。其中第一终端设备标识为第一UE的终端设备标识。
一种实施方式中,当接收的标识类型指示“第一设备的所有的终端设备标识”或“第一终端设备标识和第二终端设备标识”时,UE发送第一终端设备标识和第二终端设备标识。
另一种实施方式中,当接收的标识类型指示“终端设备标识”或“第一终端设备标识”时,UE发送第一终端设备标识。
另一种实施方式中,当接收的标识类型指示“第二终端设备标识”时,UE发送第二终端设备标识。
具体的,UE向AMF返回标识响应消息。所述标识响应消息中包含设备标识信息。
步骤104:AMF注册终端到统一数据管理(Unified Data Manager,UDM)。在注册请求中包含第一信息。
AMF还可以获取、订购终端的签约数据。
步骤105:AMF与PCF关于UE的策略关联建立。AMF可以从PCF获取终端的策略。
步骤106:AMF向RAN网元发送第三信息(具体如图5实施例所述)。
根据所述第三信息,RAN网元确定是否执行多卡优化的操作和/或确定多卡优化操作的类型(具体如图6实施例所述)。
AMF向终端返回注册响应消息。
具体地,AMF向RAN网元发送初始上下文建立请求消息。所述初始上下文建立请求消息中包含所述第三信息。
步骤107:第一UE向AMF返回注册完成消息。
通过本公开的一些实施例,在第一UE注册过程中,第一UE向网络提供第三信息。网络可以根据所述第三信息,确定是否执行多卡优化的操作和/或确定多卡优化操作的类型。从而可以支持多卡优化的操作。
请参考图11,本公开的一些实施例提供了一种通信设备,所述通信设备为第一通信设备,第一通信设备可以是但不限于第一CN网元(如MME或AMF),如图11所示,该通信设备110包括:
第一判断模块111,用于判断是否满足第一条件;
第一发送模块112,用于确定满足第一条件时,向第一UE发送第二UE的第一信息,和/或目标UE信息。
可选的,所述第二UE的第一信息包括以下至少一项:
第二UE的UE标识信息;
第二UE的信息容器;
关于第二UE的连接请求信息;
触发第二UE的连接请求的业务信息;
等待发送给第二UE的信令和/或数据的信息。
可选的,所述关于第二UE的连接请求信息包括以下至少一项:
连接请求的原因;
连接请求的指示信息。
可选的,所述满足第一条件包括以下至少一项
第一UE、第二UE和/或第一设备的能力为单收;
第二UE处于空闲态或非活跃态;
具有下行信令和/或用户数据等待发送给所述第二UE;
第一UE处于连接态;
第一UE与第二UE存在关联;
第一UE与第二UE存在寻呼冲突;
第一UE正在进行语音业务;
第一UE正在进行使第一设备无法监听第二UE的寻呼的业务,且所述第一设备为第一UE和第二UE所在的设备;
从第二CN网元接收到第二UE的第二信息。
可选的,所述通信设备110还包括:
获取模块,用于获取第三信息;
其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数量、第一设备是否支持多卡的指示信息、第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息。
本实施例中,通信设备110能够实现本公开图2所示方法实施例中实现的各个过程,以及达到相同的有益效果,为避免重复,这里不再赘述。
请参考图12,本公开的一些实施例提供了一种通信设备,所述通信设备为第二通信设备,第二通信设备可以是但不限于第二CN网元,如图12所示,该通信设备120包括:
第二判断模块121,用于判断是否满足第二条件;
第一执行模块122,用于确定满足第二条件时,执行第二操作;
其中,所述第二操作包括以下至少一项:
向第一CN网元请求通过第一UE发送第二UE的第二信息;
向第二UE发送寻呼消息;
向第二UE的RAN网元发送第二UE的相关信息。
可选的,所述第二UE的相关信息包括以下至少一项:
第二UE关联的第一UE的UE标识信息;
第二UE的UE标识信息;
第二UE的信息容器;
关于第二UE的连接请求信息;
触发第二UE的连接请求的业务信息;
等待发送给第二UE的信令和/或数据的信息。
可选的,所述满足第二条件包括以下至少一项:
向第二UE发送寻呼消息后,没有收到第二UE的响应;
向第二UE发送通知消息后,没有收到第二UE的响应;
第一UE、第二UE和/或第一设备的能力为单收;
第二UE处于空闲态或非活跃态;
具有下行信令和/或用户数据等待发送给所述第二UE;
第一UE与第二UE存在关联;
第一UE与第二UE存在寻呼冲突;
第一UE正在进行语音业务;
第一UE正在进行使第一设备无法监听第二UE的寻呼的业务,且所述第一设备为第一UE和第二UE所在的设备。
本实施例中,通信设备120能够实现本公开图3所示方法实施例中实现的各个过程,以及达到相同的有益效果,为避免重复,这里不再赘述。
请参考图13,本公开的一些实施例提供了一种通信设备,所述通信设备为第三通信设备,第三通信设备可以是但不限于以下至少一项:终端、第一设备、UE(如第一UE、和/或第二UE),如图13所示,该通信设备130包括:
第一接收模块131,用于接收第二UE的第一信息和/或目标UE信息;
第二执行模块132,用于根据所述第二UE的第一信息和/或目标UE信息,执行第三操作;
其中,所述第三操作包括以下至少一项:
向第二UE发送所述第二UE的第一信息;
请求建立或恢复第二UE与网络间连接。
可选的,所述第二UE的第一信息包括以下至少一项:
第二UE的UE标识信息;
第二UE的信息容器;
关于第二UE的连接请求信息;
触发第二UE的连接请求的业务信息;
等待发送给第二UE的信令和/或数据的信息。
本实施例中,通信设备130能够实现本公开图4所示方法实施例中实现的各个过程,以及达到相同的有益效果,为避免重复,这里不再赘述。
请参考图14,本公开的一些实施例提供了一种通信设备,所述通信设备为第四通信设备,第四通信设备可以是但不限于以下至少一项:终端、第一设备、UE(如第一UE、和/或第二UE),如图14所示,该通信设备140包括:
第二发送模块141,用于发送第三信息;
其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数量、第一设备是否支持多卡的指示信息、第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息。
可选的,所述第一能力信息包括以下至少一项:单发单收、单发双收、双发双收、单收、单发、双发、双发、多收、多发。
可选的,所述第二发送模块141具体用于:
确定满足第一条件时,发送所述第一能力信息;
其中,所述满足第一条件包括以下至少一项:
被网络配置双连接或载波聚合;
第一终端能力发生更新;
接入网络时。
本实施例中,通信设备140能够实现本公开图5所示方法实施例中实现的各个过程,以及达到相同的有益效果,为避免重复,这里不再赘述。
请参考图15,本公开的一些实施例提供了一种通信设备,所述通信设备为第五通信设备,第五通信设备可以是但不限于以下至少一项:RAN网元、CN网元,如图15所示,该通信设备150包括:
第二接收模块151,用于接收第三信息;其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数 量、第一设备是否支持多卡的指示信息、第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息;
第三执行模块152,用于根据所述第三信息,执行第五相关操作;
其中,所述第五相关操作包括以下至少一项:
确定是否执行多卡优化的操作;
确定多卡优化操作的类型;
执行多卡优化的操作。
可选的,所述第三执行模块152具体用于:
确定满足第四条件时,执行多卡优化的操作;
其中,所述第四条件包括以下至少一项:
第一设备支持的卡槽数量或第一设备支持的卡数量大于或等于2;
第一设备上的UE数量信息或第一设备上的卡数量信息大于或等于2;
第一设备支持多卡或第一设备支持多UE;
第一设备为多UE状态;
第一设备为多卡状态;
是否请求多卡优化的指示信息指示请求多卡优化。
本实施例中,通信设备150能够实现本公开图6所示方法实施例中实现的各个过程,以及达到相同的有益效果,为避免重复,这里不再赘述。
参见图16,图16是本公开的一些实施例提供的另一种通信设备的结构示意图,如图16所示,通信设备160包括:处理器161、存储器162及存储在所述存储器162上并可在所述处理器上运行的程序,通信设备160中的各个组件通过总线接口163耦合在一起,所述程序被所述处理器161执行时可实现上述图2所示方法实施例中实现的各个过程,或者,实现上述图3所示方法实施例中实现的各个过程,或者,实现上述图4所示方法实施例中实现的各个过程,或者,实现上述图5所示方法实施例中实现的各个过程,或者,实现上述图6所示方法实施例中实现的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
本公开的一些实施例还提供一种计算机可读存储介质,计算机可读存储介质上存储有计算机程序,该计算机程序被处理器执行时实现上述图2所示方法实施例中实现的各个过程,或者,实现上述图3所示方法实施例中实现的各个过程,或者,实现上述图4所示方法实施例中实现的各个过程,或者,实现上述图5所示方法实施例中实现的各个过程,或者,实现上述图6所示方法实施例中实现的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。其中,所述的计算机可读存储介质,如只读存储器(Read-Only Memory,简称ROM)、随机存取存储器(Random Access Memory,简称RAM)、磁碟或者光盘等。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端(可以是手机,计算机,服务器,空调器,或者网络设备等)执行本公开各个实施例所述的方法。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应 过程,在此不再赘述。
在本申请所提供的实施例中,应该理解到,所揭露的装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本公开各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本公开的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
此外,需要指出的是,在本公开的装置和方法中,显然,各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。并且,执行上述系列处理的步骤可以自然地按照说明的顺序按时间顺序执行,但是并不需要一定按照时间顺序执行,某些步骤可以并行或彼此独立地执行。对本领域的普通技术人员而言,能够理解本公开的方法和装置的全部或者任何步骤或者部件,可以在任何计算装置(包括处理器、存储介 质等)或者计算装置的网络中,以硬件、固件、软件或者它们的组合加以实现,这是本领域普通技术人员在阅读了本公开的说明的情况下运用他们的基本编程技能就能实现的。
可以理解的是,本公开实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现,处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits,ASIC)、数字信号处理器(Digital Signal Processing,DSP)、数字信号处理设备(DSP Device,DSPD)、可编程逻辑设备(Programmable Logic Device,PLD)、现场可编程门阵列(Field-Programmable Gate Array,FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现,可通过执行本公开实施例所述功能的模块(例如过程、函数等)来实现本公开实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
因此,本公开的目的还可以通过在任何计算装置上运行一个程序或者一组程序来实现。所述计算装置可以是公知的通用装置。因此,本公开的目的也可以仅仅通过提供包含实现所述方法或者装置的程序代码的程序产品来实现。也就是说,这样的程序产品也构成本公开,并且存储有这样的程序产品的存储介质也构成本公开。显然,所述存储介质可以是任何公知的存储介质或者将来所开发出来的任何存储介质。还需要指出的是,在本公开的装置和方法中,显然,各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。并且,执行上述系列处理的步骤可以自然地按照说明的顺序按时间顺序执行,但是并不需要一定按照时间顺序执行。某些步骤可以并行或彼此独立地执行。
上面结合附图对本公开的实施例进行了描述,但是本公开并不局限于上述的具体实施方式,上述的具体实施方式仅仅是示意性的,而不是限制性的,本领域的普通技术人员在本公开的启示下,在不脱离本公开宗旨和权利要求所保护的范围情况下,还可做出很多形式,均属于本公开的保护之内。
Claims (22)
- 一种信息传送的方法,应用于第一通信设备,包括:判断是否满足第一条件;确定满足第一条件时,向第一用户设备UE发送第二UE的第一信息,和/或目标UE信息。
- 根据权利要求1所述的方法,其中,所述第二UE的第一信息包括以下至少一项:第二UE的UE标识信息;第二UE的信息容器;关于第二UE的连接请求信息;触发第二UE的连接请求的业务信息;等待发送给第二UE的信令和/或数据的信息。
- 根据权利要求2所述的方法,其中,所述关于第二UE的连接请求信息包括以下至少一项:连接请求的原因;连接请求的指示信息。
- 根据权利要求1所述的方法,其中,所述满足第一条件包括以下至少一项第一UE、第二UE和/或第一设备的能力为单收;第二UE处于空闲态或非活跃态;具有下行信令和/或用户数据等待发送给所述第二UE;第一UE处于连接态;第一UE与第二UE存在关联;第一UE与第二UE存在寻呼冲突;第一UE正在进行语音业务;第一UE正在进行使第一设备无法监听第二UE的寻呼的业务,且所述第一设备为第一UE和第二UE所在的设备;从第二核心网CN网元接收到第二UE的第二信息。
- 根据权利要求1所述的方法,其中,所述判断是否满足第一条件之前,所述方法还包括:获取第三信息;其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数量、第一设备是否支持多卡的指示信息、第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息。
- 一种信息传送的方法,应用于第二通信设备,包括:判断是否满足第二条件;确定满足第二条件时,执行第二操作;其中,所述第二操作包括以下至少一项:向第一CN网元请求通过第一UE发送第二UE的第二信息;向第二UE发送寻呼消息;向第二UE的RAN网元发送第二UE的相关信息。
- 根据权利要求6所述的方法,其中,所述第二UE的相关信息包括以下至少一项:第二UE关联的第一UE的UE标识信息;第二UE的UE标识信息;第二UE的信息容器;关于第二UE的连接请求信息;触发第二UE的连接请求的业务信息;等待发送给第二UE的信令和/或数据的信息。
- 根据权利要求6所述的方法,其中,所述满足第二条件包括以下至少一项:向第二UE发送寻呼消息后,没有收到第二UE的响应;向第二UE发送通知消息后,没有收到第二UE的响应;第一UE、第二UE和/或第一设备的能力为单收;第二UE处于空闲态或非活跃态;具有下行信令和/或用户数据等待发送给所述第二UE;第一UE与第二UE存在关联;第一UE与第二UE存在寻呼冲突;第一UE正在进行语音业务;第一UE正在进行使第一设备无法监听第二UE的寻呼的业务,且所述第一设备为第一UE和第二UE所在的设备。
- 一种信息传送的方法,应用于第三通信设备,包括:接收第二UE的第一信息和/或目标UE信息;根据所述第二UE的第一信息和/或目标UE信息,执行第三操作;其中,所述第三操作包括以下至少一项:向第二UE发送所述第二UE的第一信息;请求建立或恢复第二UE与网络间连接。
- 根据权利要求9所述的方法,其中,所述第二UE的第一信息包括以下至少一项:第二UE的UE标识信息;第二UE的信息容器;关于第二UE的连接请求信息;触发第二UE的连接请求的业务信息;等待发送给第二UE的信令和/或数据的信息。
- 一种信息传送的方法,应用于第四通信设备,包括:发送第三信息;其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数量、第一设备是否支持多卡的指示信息、第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息。
- 根据权利要求11所述的方法,其中,所述第一能力信息包括以下至少一项:单发单收、单发双收、双发双收、单收、单发、双发、双发、多收、多发。
- 根据权利要求11所述的方法,其中,所述发送第三信息,包括:确定满足第一条件时,发送所述第一能力信息;其中,所述满足第一条件包括以下至少一项:被网络配置双连接或载波聚合;第一终端能力发生更新;接入网络时。
- 一种信息传送的方法,应用于第五通信设备,包括:接收第三信息;其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数量、第一设备是否支持多卡的指示信息、第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息;根据所述第三信息,执行第五相关操作;其中,所述第五相关操作包括以下至少一项:确定是否执行多卡优化的操作;确定多卡优化操作的类型;执行多卡优化的操作。
- 根据权利要求14所述的方法,其中,所述根据所述第三信息,执行第五相关操作,包括:确定满足第四条件时,执行多卡优化的操作;其中,所述第四条件包括以下至少一项:第一设备支持的卡槽数量或第一设备支持的卡数量大于或等于2;第一设备上的UE数量信息或第一设备上的卡数量信息大于或等于2;第一设备支持多卡或第一设备支持多UE;第一设备为多UE状态;第一设备为多卡状态;是否请求多卡优化的指示信息指示请求多卡优化。
- 一种通信设备,所述通信设备为第一通信设备,包括:第一判断模块,用于判断是否满足第一条件;第一发送模块,用于确定满足第一条件时,向第一UE发送第二UE的第 一信息,和/或目标UE信息。
- 一种通信设备,所述通信设备为第二通信设备,包括:第二判断模块,用于判断是否满足第二条件;第一执行模块,用于确定满足第二条件时,执行第二操作;其中,所述第二操作包括以下至少一项:向第一CN网元请求通过第一UE发送第二UE的第二信息;向第二UE发送寻呼消息;向第二UE的RAN网元发送第二UE的相关信息。
- 一种通信设备,所述通信设备为第三通信设备,包括:第一接收模块,用于接收第二UE的第一信息和/或目标UE信息;第二执行模块,用于根据所述第二UE的第一信息和/或目标UE信息,执行第三操作;其中,所述第三操作包括以下至少一项:向第二UE发送所述第二UE的第一信息;请求建立或恢复第二UE与网络间连接。
- 一种通信设备,所述通信设备为第四通信设备,包括:第二发送模块,用于发送第三信息;其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数量、第一设备是否支持多卡的指示信息、第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息。
- 一种通信设备,所述通信设备为第五通信设备,包括:第二接收模块,用于接收第三信息;其中,所述第三信息包括以下至少一项:第一能力信息、第一设备支持的卡槽数量,第一设备支持的卡数量、第一设备是否支持多卡的指示信息、第一设备是否支持多UE的指示信息、第一设备上的UE数量信息、第一设备上的卡数量信息、第一设备是否为多UE状态的相关指示信息、第一设备是否为多卡状态的相关指示信息、是否请求多卡优化的指示信息;第三执行模块,用于根据所述第三信息,执行第五相关操作;其中,所述第五相关操作包括以下至少一项:确定是否执行多卡优化的操作;确定多卡优化操作的类型;执行多卡优化的操作。
- 一种通信设备,包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序,所述程序被所述处理器执行时实现如权利要求1至5中任一项所述的信息传送的方法的步骤,或者,实现如权利要求6至8中任一项所述的信息传送的方法的步骤,或者,实现如权利要求9或10所述的信息传送的方法的步骤,或者,实现如权利要求11至13中任一项所述的信息传送的方法的步骤,或者,实现如权利要求14或15所述的信息传送的方法的步骤。
- 一种计算机可读存储介质,其中,所述计算机可读存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现如权利要求1至5中任一项所述的信息传送的方法的步骤,或者,实现如权利要求6至8中任一项所述的信息传送的方法的步骤,或者,实现如权利要求9或10所述的信息传送的方法的步骤,或者,实现如权利要求11至13中任一项所述的信息传送的方法的步骤,或者,实现如权利要求14或15所述的信息传送的方法的步骤。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910055961.5A CN111278107B (zh) | 2019-01-18 | 2019-01-18 | 信息传送的方法及通信设备 |
| CN201910055961.5 | 2019-01-18 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2020147837A1 true WO2020147837A1 (zh) | 2020-07-23 |
Family
ID=71000018
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2020/072751 Ceased WO2020147837A1 (zh) | 2019-01-18 | 2020-01-17 | 信息传送的方法及通信设备 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111278107B (zh) |
| WO (1) | WO2020147837A1 (zh) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114205919A (zh) * | 2020-09-18 | 2022-03-18 | 维沃移动通信有限公司 | 离开方式确定方法、装置和通信设备 |
| CN114391286A (zh) * | 2020-08-05 | 2022-04-22 | 北京小米移动软件有限公司 | 问题上报方法和装置、问题接收方法和装置 |
| WO2023015504A1 (zh) * | 2021-08-11 | 2023-02-16 | 北京小米移动软件有限公司 | 寻呼方法、装置、通信设备及存储介质 |
| CN116209034A (zh) * | 2021-11-30 | 2023-06-02 | 维沃移动通信有限公司 | 多卡终端的通信方法、装置及终端 |
| CN117135746A (zh) * | 2022-05-19 | 2023-11-28 | 上海朗帛通信技术有限公司 | 一种被用于无线通信的方法和装置 |
Families Citing this family (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114271025A (zh) | 2020-07-17 | 2022-04-01 | Oppo广东移动通信有限公司 | 信息传输方法、装置、设备及存储介质 |
| CN114071797B (zh) * | 2020-07-31 | 2025-02-25 | 维沃移动通信有限公司 | 信息传输方法、装置、多卡终端及可读存储介质 |
| CN114071445B (zh) * | 2020-07-31 | 2023-05-05 | 维沃移动通信有限公司 | 信息传输方式的配置方法、终端及网络侧设备 |
| CN118945817A (zh) | 2020-08-04 | 2024-11-12 | 北京三星通信技术研究有限公司 | 由用户终端执行的方法、由基站执行的方法、终端及基站 |
| CN114071710B (zh) * | 2020-08-04 | 2024-08-23 | 北京三星通信技术研究有限公司 | 由用户终端执行的方法、由基站执行的方法、终端及基站 |
| CN116867064A (zh) * | 2020-08-31 | 2023-10-10 | 北京小米移动软件有限公司 | 寻呼原因发送方法和装置、寻呼原因获取方法和装置 |
| CN114390650B (zh) | 2020-10-21 | 2024-09-03 | 大唐移动通信设备有限公司 | 信号传输方法、网络设备、终端和存储介质 |
| CN112514472B (zh) * | 2020-11-06 | 2023-08-22 | 北京小米移动软件有限公司 | 信息发送方法及装置、存储介质 |
| CN114641090B (zh) * | 2020-12-15 | 2025-01-10 | 华为技术有限公司 | 一种通信方法及通信装置 |
| EP4271000A4 (en) * | 2020-12-24 | 2024-01-24 | Beijing Xiaomi Mobile Software Co., Ltd. | Paging method and apparatus, and storage medium |
| CN114786243B (zh) * | 2021-01-22 | 2024-12-06 | 展讯半导体(南京)有限公司 | 参考信号传输时机有效性的指示方法和用户设备 |
| CN115314990B (zh) * | 2021-05-07 | 2025-12-05 | 维沃移动通信有限公司 | 信息处理方法、装置、通信设备及可读存储介质 |
| CN115314881B (zh) * | 2021-05-07 | 2024-11-15 | 维沃移动通信有限公司 | 信息处理方法、装置、通信设备及可读存储介质 |
| WO2022236642A1 (zh) * | 2021-05-10 | 2022-11-17 | 北京小米移动软件有限公司 | 信息处理方法、装置、通信设备及存储介质 |
| WO2022266861A1 (zh) | 2021-06-22 | 2022-12-29 | 北京小米移动软件有限公司 | 寻呼处理方法、通信装置和存储介质 |
| CN116095709A (zh) * | 2021-11-05 | 2023-05-09 | 维沃移动通信有限公司 | 信息处理方法、装置、通信设备及可读存储介质 |
| CN120786329A (zh) * | 2024-04-03 | 2025-10-14 | 华为技术有限公司 | 通信方法及装置 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120108273A1 (en) * | 2010-10-29 | 2012-05-03 | Samsung Electronics Co., Ltd. | Method and apparatus for communication in portable terminal using multiple sim cards |
| CN106535331A (zh) * | 2016-12-26 | 2017-03-22 | 惠州Tcl移动通信有限公司 | 一种双卡双待手机的通信方法及系统 |
| CN108616830A (zh) * | 2016-12-27 | 2018-10-02 | 北京信威通信技术股份有限公司 | 一种支持窄带d2d通信的寻呼方法 |
| CN108633109A (zh) * | 2018-05-11 | 2018-10-09 | 中国联合网络通信集团有限公司 | 双卡终端的主卡的识别方法和装置 |
| CN109151807A (zh) * | 2018-09-05 | 2019-01-04 | 中国联合网络通信集团有限公司 | 一种双卡双待移动终端主副卡绑定的方法和系统 |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101203005B (zh) * | 2007-12-13 | 2010-12-08 | 展讯通信(上海)有限公司 | 一种解决单芯片双卡双待手机主副卡载波冲突的方法 |
| US20130090137A1 (en) * | 2011-10-05 | 2013-04-11 | Qualcomm Incorporated | Apparatus and methods for reducing page loss in multiple subscription, multiple radio access technology devices |
| CN102984801B (zh) * | 2012-11-20 | 2016-03-30 | 华为终端有限公司 | 一种双卡用户设备的通信方法及装置 |
| CN103002516B (zh) * | 2012-12-28 | 2016-03-23 | 青岛海信移动通信技术股份有限公司 | 一种数据传输方法和装置、数据终端 |
| US9119172B2 (en) * | 2013-07-31 | 2015-08-25 | Qualcomm Incorporated | Fair instantaneous conflict resolution among N periodic contenders |
| CN104954546B (zh) * | 2015-01-23 | 2018-06-12 | 深圳市卡卓无线信息技术有限公司 | 双卡智能终端及基于双卡智能终端的sim卡智能切换方法 |
| CN107623900B (zh) * | 2016-07-13 | 2021-04-23 | 展讯通信(上海)有限公司 | 多卡多待移动终端的寻呼冲突处理方法、装置及移动终端 |
| CN107690134B (zh) * | 2016-08-05 | 2022-07-08 | 北京三星通信技术研究有限公司 | 用于双卡终端的寻呼冲突解决方法及双卡终端 |
| CN107959954B (zh) * | 2016-10-14 | 2020-10-30 | 中国移动通信有限公司研究院 | 一种无线通信方法及终端设备 |
| CN108650672A (zh) * | 2018-04-10 | 2018-10-12 | 珠海市魅族科技有限公司 | 通信控制方法、通信控制装置及终端 |
| CN109041220A (zh) * | 2018-08-30 | 2018-12-18 | 中国联合网络通信集团有限公司 | 呼叫方法及呼叫系统 |
-
2019
- 2019-01-18 CN CN201910055961.5A patent/CN111278107B/zh active Active
-
2020
- 2020-01-17 WO PCT/CN2020/072751 patent/WO2020147837A1/zh not_active Ceased
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120108273A1 (en) * | 2010-10-29 | 2012-05-03 | Samsung Electronics Co., Ltd. | Method and apparatus for communication in portable terminal using multiple sim cards |
| CN106535331A (zh) * | 2016-12-26 | 2017-03-22 | 惠州Tcl移动通信有限公司 | 一种双卡双待手机的通信方法及系统 |
| CN108616830A (zh) * | 2016-12-27 | 2018-10-02 | 北京信威通信技术股份有限公司 | 一种支持窄带d2d通信的寻呼方法 |
| CN108633109A (zh) * | 2018-05-11 | 2018-10-09 | 中国联合网络通信集团有限公司 | 双卡终端的主卡的识别方法和装置 |
| CN109151807A (zh) * | 2018-09-05 | 2019-01-04 | 中国联合网络通信集团有限公司 | 一种双卡双待移动终端主副卡绑定的方法和系统 |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114391286A (zh) * | 2020-08-05 | 2022-04-22 | 北京小米移动软件有限公司 | 问题上报方法和装置、问题接收方法和装置 |
| CN114391286B (zh) * | 2020-08-05 | 2024-01-30 | 北京小米移动软件有限公司 | 问题上报方法和装置、问题接收方法和装置 |
| CN114205919A (zh) * | 2020-09-18 | 2022-03-18 | 维沃移动通信有限公司 | 离开方式确定方法、装置和通信设备 |
| WO2023015504A1 (zh) * | 2021-08-11 | 2023-02-16 | 北京小米移动软件有限公司 | 寻呼方法、装置、通信设备及存储介质 |
| CN116209034A (zh) * | 2021-11-30 | 2023-06-02 | 维沃移动通信有限公司 | 多卡终端的通信方法、装置及终端 |
| CN117135746A (zh) * | 2022-05-19 | 2023-11-28 | 上海朗帛通信技术有限公司 | 一种被用于无线通信的方法和装置 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111278107B (zh) | 2021-10-08 |
| CN111278107A (zh) | 2020-06-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020147837A1 (zh) | 信息传送的方法及通信设备 | |
| US12082284B2 (en) | Method for registering terminal in wireless communication system and apparatus therefor | |
| WO2021027835A1 (zh) | 消息传输方法和通信设备 | |
| US11997751B2 (en) | Method for supporting UE association and communications device | |
| CN108605376A (zh) | 无线终端、无线站及其方法 | |
| CN113473564B (zh) | 网络切片切换的方法、建立pdu会话的方法及装置 | |
| US20230083832A1 (en) | Information indication method and apparatus and communication device | |
| JP2024502890A (ja) | 情報処理方法、端末、ネットワーク側機器及び可読記憶媒体 | |
| CN107105500B (zh) | 一种通信方法及装置 | |
| US12369021B2 (en) | Terminal capability identifier operation method and communications device | |
| CN113810956B (zh) | 切换多播业务的方法及设备 | |
| US12581283B2 (en) | Managing downlink data during transitions between mobile networks | |
| KR102714608B1 (ko) | 서비스 최적화 방법 및 통신 장치 | |
| US20240064702A1 (en) | Information processing method and apparatus, communication device and readable storage medium | |
| RU2791048C1 (ru) | Способ управления идентификаторами функциональных возможностей оконечного устройства и устройство связи | |
| CN113709913A (zh) | 连接控制方法、装置和通信设备 | |
| WO2023143437A1 (zh) | 信息公开方法及通信设备 | |
| HK40064700A (zh) | 终端能力标识的操作方法和通信设备 | |
| HK40064700B (zh) | 终端能力标识的操作方法和通信设备 | |
| CN114205919A (zh) | 离开方式确定方法、装置和通信设备 | |
| HK1262282B (zh) | 数据传输的方法、接入网设备、终端设备和网络实体 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20741924 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 20741924 Country of ref document: EP Kind code of ref document: A1 |